OpenEdge Architect renamed as Progress Developer Studio for OpenEdge
Beginning with the 11.0 Release of OpenEdge, Progress Developer Studio for OpenEdge replaces OpenEdge Architect as a product name. Progress Developer Studio for OpenEdge is not a new product. References in documentation to Progress Developer Studio for OpenEdge, or OpenEdge Architect refer to the same product.
Also be aware that you no longer choose Start > OpenEdge > OpenEdge Architect to launch the product from the Windows Start menu. In the 11.0 release you can start Progress Developer Studio for OpenEdge by selecting one of the following default locations:
Start > Progress > OpenEdge 11 > Progress Developer Studio 3.6 for OpenEdge
Start > Progress > OpenEdge 11 > Progress Developer Studio 3.6 for OpenEdge Clean
Start > Progress > Developer Studio 3.6 > Progress Developer Studio 3.6
Start > Progress > Developer Studio 3.6 > Progress Developer Studio 3.6 Clean
Note: Clean is a startup option that removes cached data before starting Eclipse.
Upgrade to Eclipse 3.6.0
The 11.0 Release of Progress Developer Studio for OpenEdge includes Eclipse 3.6.0 (The 10.2B release was shipped with Eclipse 3.4.2.)
Debugging
The following are the new debug launch configuration features provided in the 11.0 Release of Progress Developer Studio for OpenEdge:
AppServer and WebSpeed debugging - Remote and local debugging of both AppServer and WebSpeed applications.
Attachable Debugger - A new debug launch configuration type that allows you to attach the debugger to an external AVM.
AppServer pass-through - Debugging a remote procedure from within Architect, during pass-through, without having to set breakpoints in the remote procedure code.
Standalone Debugger functionality - The debugging features provided by the standalone debugger are now available within Progress Developer Studio for OpenEdge.
With the enhanced debugging functionality, you can:
Debug code running on a local or remote AVM from within Progress Developer Studio.
Set breakpoints in ABL files located outside the workspace, and also in include files.
Debug multiple AppServer or WebSpeed agents in a single Progress Developer Studio session.
Attach the Debugger to an AppServer or WebSpeed broker in debug mode.
View the ABL stack for multiple AVMs in the Debug view.
Debug SpeedScript applications running on a WebSpeed agent.
Launch WebSpeed brokers with the new run and debug launch configurations.
WebSpeed
The 11.0 Release of Progress Developer Studio for OpenEdge includes improved support for creating and managing WebSpeed applications. WebSpeed support includes:
The addition of a WebSpeed project type to the OpenEdge project wizard.
Templates and wizards for creating SpeedScript and CGI Wrapper files.
Full-featured editors for editing HTML, Embedded SpeedScript, and CGI Wrapper files.
Content assist for super procedures.
WebSpeed server support for running, debugging, and testing WebSpeed applications.
Support for the configuring of, and publishing to local and remote servers. (You can optionally compile to the AVM of a remote broker when you publish.)
AppServer
Enhancements to AppServer support in the 11.0 Release of Progress Developer Studio for OpenEdge allow you to:
Create and publish an application to a local or remote AppServer, so you can test the application in an environment outside of the Progress Developer Studio workspace.
Use OpenEdge Explorer, which provides an HTTPS connection for secure communication, to create and manage AppServer brokers.
You can also use OpenEdge Explorer to publish to a remote machine (minimum version OpenEdge 11.0 required). You can access OpenEdge Explorer from within OpenEdge Developer Studio.
Use OpenEdge Explorer to publish to a remote machine (minimum version OpenEdge 11.0 required). You can access OpenEdge Explorer from within Progress Developer Studio for OpenEdge.
Optionally compile as you publish, when publishing remotely.
Create custom project types.
Monitor all brokers from a single view.
Associate a project with both AppServer and WebSpeed if the project contains the required facet.
Visual Designer
Visual Designer, in the 11.0 Release of Progress Developer Studio for OpenEdge, is updated to provide support for ABL SIGNATURE-ONLY events and is enhanced with an improved ProBindingSource Designer.
Support for ABL SIGNATURE-ONLY events
In earlier releases of OpenEdge, the Visual Designer Properties view displayed the public .NET events including events defined in ABL using the DELEGATE clause. In OpenEdge 11.0, the Visual Designer Properties view displays the ABL events that are defined in an ABL-derived .NET class using the DELEGATE or the SIGNATURE clause. The events using the SIGNATURE clause appear in the Events tab only if their signatures follow the .NET convention for event handler signatures.
Enhancements to ProBindingSource Designer
In earlier releases of OpenEdge, the ProBindingSource Designer opened multiple modal dialogs to define a schema. The Available Schema panel is now available on the ProBindingSource Designer window. It enables you to define schema more easily and reduces the number of steps for importing schema.
In addition, support for defining recursive relationships between tables is added to the interface. A combo box labeled Recursive table lists the name of the selected table and all the parent tables where a recursive relationship can be defined.
ABL Editor
The ABL Editor, in the 11.0 Release of Progress Developer Studio for OpenEdge, is enhanced to enable or disable processing preprocessors from a toggle button on the toolbar. The following features are supported when preprocessing is enabled:
The ABL Editor displays the inactive preprocessor regions in gray.
Code assistance displays proposals for the built-in or defined preprocessors. Preprocessor references are expanded when evaluating completion proposals.
Hovering over the preprocessor reference displays the current value of the preprocessor in a pop-up dialog.
The elements inside the inactive preprocessor regions appear in gray in the Outline view.
The Quick Outline view displays a list of preprocessors and their values.
In addition, the ABL Editor supports the following ABL language changes:
Color-coding recognizes the DYNAMIC-PROPERTY keyword, and the SetPropertyValue() and GetPropertyValue() methods. The ABL Editor displays these syntax elements in different colors to make them easy to recognize.
Content assistance displays a list of syntax elements that are valid for the DYNAMIC-PROPERTY keyword, and the SetPropertyValue() and GetPropertyValue() methods. You can select a syntax completion proposal from the list to complete the code in the ABL Editor.
Hovering over the DYNAMIC-PROPERTY keyword displays additional information in a pop-up dialog.
A new ABL Interface now inherits interfaces from other interfaces.
DB Navigator
DB Navigator was enhanced to support the multi-tenant features in OpenEdge databases. DB Navigator now enables:
Serving multiple users with a single OpenEdge database instance.
Creating, editing, and identifying multi-tenant tables and sequences.
Categorizing and filtering DB tables.
Launching OpenEdge Explorer from the DB navigator perspective for configuring the database.
Sharing data definition files (schema changes) among developers.
Custom project types
OpenEdge projects and the Customization Editor were enhanced in OpenEdge Release 11.0 to support custom project types.
The following enhancements are now available for OpenEdge projects:
Progress Developer Studio for OpenEdge creates all new OpenEdge projects as faceted projects and converts the old OpenEdge projects into faceted projects by default.
Progress Developer Studio for OpenEdge provides a predefined set of OpenEdge facets and project types.
Progress Developer Studio for OpenEdge allows you to create a specialized project type for the current project with the enhanced New OpenEdge Project wizard.
Progress Developer Studio for OpenEdge provides a set of commonly used project types for OpenEdge application development and a framework to configure custom project types as required.
The enhancements made to the Customization Editor now allow you to:
Create custom project types with the desired folder layouts and PROPATH settings.
Generate new Editor templates.
Configure code-generation templates and use them in custom projects.
Share custom project types with other developers.
Use custom project types as templates for new projects.
Excluding files and folders from compilation
In earlier releases of Progress Developer Studio for OpenEdge, there was no option to exclude a file or folder from a build. The build and compile environment in Progress Developer Studio for OpenEdge is enhanced as follows:
You can exclude project resources from your build from the context menu (Progress OpenEdge > Exclude from Build) or from the Source tab of the Build properties page. Excluded entries are added to the Excluded node in the Source tab of the Build properties page.
You can include the resources that were previously excluded from the build from the context menu (Progress OpenEdge > Include in Build) or from the Source tab of the Build properties page.
You can create working sets to compile a set of resources instead of building the entire project.
You can control the build order using the Source tab of the Build properties page.
AppServer and WebSpeed debugging - Remote and local debugging of both AppServer and WebSpeed applications.