This section describes the new features and changes that were implemented in the 10.1C release of OpenEdge Architect (renamed as Progress Developer Studio for OpenEdge in Release 11.0).
Class Browser
A new view called the Class Browser allows you to see the structure and content of the various classes that you work with in creating ABL applications. The Class Browser's contents are organized by resources, which are collections of classes (types).
Progress DB Navigator
In order to make it more independent, the OpenEdge DB Navigator plug-in has been slightly restructured and was renamed the Progress DB Navigator. You will notice a change in the location and structure of its Preferences as well as a renaming of the perspective. In addition to continuing to provide the driver for the OpenEdge database, Progress Software now provides Type IV DataDirect JDBC drivers for the following databases: ORACLE, Microsoft SQL Server, IBM DB2, Sybase, and Informix.
ABL Editor
Support for structured error handling
To support ABL enhancements in error-handling functionality, OpenEdge Architect wizards, menus, and context assistance now provide options for automatically generating:
Routine-level error-handling statements in new classes and procedures
CATCH and FINALLY blocks in new or existing source files
Performance-related options for code assistance
The Editor Assistance preferences page includes several new options that can mitigate adverse impact on system response time caused by waiting for the code to be analyzed:
You can specify the maximum amount of time that OpenEdge Architect spends updating code analysis before responding to requests for code-completion assistance. If the re-parsing of the code is not completed within the specified interval (by default 300 milliseconds), OpenEdge Architect proposes completion options based on the most recent full analysis.
You can disable highlighting of matching elements. That is, you can suppress the display of a marker at the position of the code element, such as a parenthesis or a beginning or ending statement in a code block, that is paired with the element at the current cursor position.
You can suppress field descriptions in completion proposals for database tables.
Using these options can improve performance, particularly when you work with very large source files or remote databases.
Support for static data members, methods, and properties
To support the use of the STATIC keyword where applicable, OpenEdge Architect macros, wizards, and menus now provide options for automatically defining data members, methods, and properties as static.
In the Outline view, the icons for static data members, methods, and properties appear with a red "S" overlaying the standard image.
Improved support for coding methods implemented via interface
The New Class wizard has been enhanced to automatically generate method stubs for all methods implemented via interface. In addition, the former Override Methods dialog, now called Override/Implement Methods, has been enhanced to generate stubs for interface methods on demand.
Enhanced macro functionality
OpenEdge Architect now uses standard Eclipse template functionality for creating and managing macros (also called templates). Procedures for using and managing macros are largely unchanged from previous versions, but the enhanced design offers these advantages:
You can now define and run multiple-line macros. Previously, macros were restricted to a single line.
For creating custom macros, the New Template editor includes an Insert Variable command that improves usability.
To make custom macros created in previous versions of OpenEdge Architect available for use in version 10.1C, migration is required. When you first select a workspace created in an earlier version, OpenEdge Architect offers the option of migrating the macros for that workspace. If you decline to perform the migration at that time, you can do so at your convenience by selectingOpenEdge > Migration > Migrate 10.1A or 10.1B Macros to Templates.
Formatting changes
The following changes have been made to OpenEdge Architect formatting and code-assistance options:
The Format option no longer appears on the Source menu, its functions replaced by separate commands as described in the next two entries in this list.
A new command (Source > Correct Case, Ctrl+Shift+F) causes the ABL Editor to adjust the case of keywords in the current file according to the setting on the Editor preferences page. Also, you can set a new option on the Editor preferences page to have the ABL Editor automatically adjust keyword casing as you type.
A new command ( Source > Correct Indentation, Ctrl+I) causes the ABL Editor to adjust indentation of lines in the current file.
Hot keys
Note the following changes and additions to default hot-key sequences for OpenEdge Architect:
ALT+SHIFT+T
Adds a static constructor to the current file.
ALT+SHIFT+Z, C
Surrounds the currently selected code with a CATCH block.
ALT+SHIFT+Z, F
Surrounds the currently selected code with a FINALLY block.
CTRL+SHIFT+F
Applies casing preferences to keywords in the current file. This sequence previously applied both keyword casing and indentation.
CTRL+I
(New) Adjusts indentation of lines in the current file.
CTRL+SHIFT+P
(New) Moves the cursor to the matching code element paired with the element at the current cursor position.
Accessing the Add Annotation wizard
The Add Annotation wizard is available by choosing Source > Add Annotation from the OpenEdge Architect main menu bar. The wizard is no longer available by choosing File > New > Other.
If a file is open, you can access the Add Annotationwizard by choosing Source > Add Annotation from the context menu. You can also right-click in the Resources view and choose OpenEdge > Add Annotation.
Routine-level error-handling statements in new classes and procedures