Maximizing productivity with Progress Developer Studio for OpenEdge 11

Maximizing productivity with Progress Developer Studio for OpenEdge 11
Maximizing productivity with Progress Developer Studio for OpenEdge 11.2 and Higher Anil Kumar Yogesh Devatraj

Improving OpenEdge developer productivity
Focus of the Session Brief Introduction to Progress Developer Studio For OpenEdge 11.2 Features Improving OpenEdge developer productivity Know what’s new in Progress Developer Studio for OpenEdge 11.3 Demos of all new exciting features

Introduction to Progress Developer Studio for OpenEdge
“An Eclipse based integrated development environment to increase OpenEdge developer productivity with highly customizable and easily navigable user interface.” Progress Developer Studio for OpenEdge Eclipse Plug-in Platform Appbuilder Integration REST DB Nav & Debugger Visual Designer ABL & Speed Script Editor Extending New Plug-ins

Progress Developer Studio for OpenEdge 11.2
AppBuilder Integration Seamless Appbuilder Integration with PDSOE

Appbuilder Integration to PDSOE
“New improved seamless Appbuilder Integration makes PDSOE one stop solution for developer that develops or maintain ABL GUI applications using Appbuilder” All new GUI design editor with design palette Preferences & Properties Improved ABL source editor Section editor support Support for Dynamics & ProTools All new GUI design editor with design pallet. Support for AppBuilder templates & wizards to create GUI design file. OpenEdge project aware AppBuilder applications. Appbuilder specific preferences and project properties. Improved ABL source editor. Support for Dynamics & ProTools. Much more…

Support for Dynamics & ProTools All new GUI design editor Preferences & Properties Improved ABL source editor. Section editor support Moved to Menu & Toolbar Moved to dockable Palette

All new GUI design editor Preferences & Properties Improved ABL source editor. Section editor support Support for Dynamics & ProTools Brings native Appbuilder functionality to PDSOE Dock-able widget palette Inherits look and feel of Visual Designer Hierarchical widget outline view Synchronization between design and source editor Dock-able Palette The GUI Designer has a new dock-able Design Palette that extends Eclipse’s existing GEF Palette and is populated with components from the AppBuilder customizable configuration files. New GUI Designer brings native Appbuilder functionality to PDSOE. New dock-able design palette dynamically populated from the Appbuilder customization configuration files. Inherits look and feel of Visual Designer to make all design editors consistent. Synchronized AppBuilder outline view representing widget hierarchy with editing options . Introduced Appbuilder specific context sensitive menus and toolbars. Support synchronization between design and source editor. Widget Hierarchy Outline

All new GUI design editor Preferences & Properties Improved ABL source editor. Section editor support Support for Dynamics & ProTools AppBuilder Preferences Now AppBuilder GUI applications are OpenEdge project aware. AppBuilder options are available as PDSOE preferences and project properties. The purpose of the integration is also to make the AppBuilder fully benefit from the project organization provided by OEA and all AppBuilder file operations use OEA project dialogs instead of the standard system file dialog. AppBuilder specific preferences and project properties will be available under OpenEdge preferences in PDS. ABL GUI developer will able to set integrated environment specific preferences and properties from PDS only. This set of preferences and properties are different from stand alone AppBuilder.

Improved ABL Source Editor: Read-only Code Sections
All new GUI design editor Preferences & Properties Improved ABL source editor. Section editor support Support for Dynamics & ProTools Ease of editing AppBuilder generated source file Protects AppBuilder generated code Customizable Highlighting AppBuilder Editor preference options are provided to turn on/off this feature Code folding for Appbuilder specific blocks Customized Find and Replace dialog All new Trigger Wizard. Editable code section Non-editable section for AppBuilder generated code User can turn on or off this feature as well as change background color of the read-only code section. ABL Source editor is improved for ease of editing AppBuilder generated source file. Appbuilder generated code sections are made read-only blocking all editing actions to prevent accidently corrupting the file. Read-only code sections are highlighted with customizable background color maintaining existing keyword color coding for better readability By default AppBuilder read-only code block will be close folded Editable code block

Improved ABL Source Editor: Section Editor
All new GUI design editor Preferences & Properties Improved ABL source editor. Section editor support Support for Dynamics & ProTools Simulates Standalone AppBuilder section editor functionality Easy navigation through ABL outline nodes Hides AppBuilder generated code to better readability Quick toggle option to enable/disable section view. Toggle action to enable/disable section view Hides AppBuilder generated code to better readability. Quick toggle option to enable/disable section view. Introduced two new virtual node to ABL outline view to navigate main & definition code blocks. Displays code section related to selection

AppBuilder ProTools & Dynamics
All new GUI design editor Preferences & Properties Improved ABL source editor. Section editor support Support for Dynamics & ProTools AppBuilder ProTools options are available under workbench toolbar as well as Menu, divided in three sub groups General ProTools Appbuilder ProTools ADM2 ProTools All Progress Dynamics features are fully integrated in PDSOE like Open dynamic object. Register to repository. Save dynamics object as static. Save static object as dynamics. Open associate procedure. ADM2 ProTools General ProTools ApppBuilder ProTools

AppBuilder Integration Seamless Appbuilder Integration with PDSOE ABL Scratchpad Running ABL code snippet on the fly

Editing Experience Running Options Data Persistence ABL Scratchpad
“ABL Scratchpad is an editable multi-tabbed view that allow user to write and test ABL code snippet on the fly.” Editing Experience Running Options Data Persistence Editing Experience Running Options Data Persistence

Standard editor options
Editing Experience Editing Experience Running Options Data Persistence Content Assistance and Data Awareness on demand Color Coding Syntax Check in view itself Standard editor operations like cut, copy, paste options Undo redo actions Clear entire code in view. Content Assist Color Coding Standard editor options

Running Options and Persistence
Editing Experience Running Options Data Persistence Run against any of the available projects runtime By default, uses shared AVM Can also be executed against new AVM to avoid overwriting session or global variables. Preserves the content of all opened tabs Remembrance of associated AVM for individual tabs Save-as option for saving any code snippets into file system. `1

AppBuilder Integration Seamless Appbuilder Integration with PDSOE ABL Scratchpad Running ABL code snippet on the fly REST Introducing ABL to REST world

REST Support in PDSOE “REST (REpresentational State Transfer) is an architectural style for distributed computing that was defined in conjunction with the HTTP protocol”. PDSOE provides Application development tools for the same. REST Projects creation in PDSOE REST Annotations to ABL Files REST Expose Editor for Mappings Publishing and Packaging OE REST Applications OE Web Server and REST Services - It is becoming apparent that even as it becomes popular, REST (Representational State Transfer) is not yet as well understood. This might seem a surprising statement, but a lot of us use REST thanks to many frameworks supporting REST like interfaces. Roy Fielding, who proposed his dissertation (and is treated as reference document for REST) with REST concepts might not thought of its evolution. OpenEdge users can make use of the fruits of REST (technology) starting from OpenEdge 11.2 release. OpenEdge provides lots of Application development tools for the same. Steps involved in REST Completion REST Project Creation Annotating new or existing ABL File Creating REST Service Perform mappings using REST Expose Editor Publish specific service to OE Webserver Invoke service through REST Client

New REST Project New project types: REST project type
REST Projects in PDSOE REST Annotations to ABL Files REST Expose Editor Publishing and Packaging OE REST Appl OE Web Server and REST Services New project types: REST project type Mobile project type REST and Mobile projects are associated with the OpenEdge Server perspective To make development easier - based on the type of project that you’re developing, Progress Developer Studio for OpenEdge offers a number of different project types. In OpenEdge 11.2, there are two new project types, one for REST and one for Mobile. The new options can be seen under the Project type configuration drop-down list, with the REST project type is selected For the rest of the wizard we’ll only be looking at the areas that have changed, or that are pertinent when selecting options for an OpenEdge REST project. A new REST facet is been added in the PDSOE which brings up all of the REST capabilities like having an Appserver nature for the same.

REST Annotations to ABL Files
REST Projects in PDSOE REST Annotations to ABL Files REST Expose Editor Publishing and Packaging OE REST Appl OE Web Server and REST Services Identify ABL code that is to be exposed as REST service Programs can also be: ABL classes REST annotations are added to identify functionality that will be exposed to the REST service Use Define Service Interface Wizard for adding Mobile Annotations Annotations can be added to: Methods in a class Once the REST Project is created the next immediate step is to identify the ABL Code/snippet that is to be exhibited as REST Service. New entries are been added to Service Interface wizard (through which one can add BPM and ESB annotations) namely REST and Mobile and one can add annotations to the ABL file using the SI wizard. Starting from 11.2 annotations addition to ABL Classes is also provided from PDSOE apart from procedures. REST Specific Option

Creating a REST Service
REST Projects in PDSOE REST Annotations to ABL Files REST Expose Editor Publishing and Packaging OE REST Appl OE Web Server and REST Services REST Service URI should start with ‘/’ Service can be associated to respective OE Web Servers during the creation One REST Project can have multiple REST Services Once an ABL resource is decorated with the REST annotations one can associate set of resources by creating a REST service directly from PDSOE. There is also one section to associate the created REST service to OE Webservice. So what is this OE Webserver. Once an service/application is developed that should be hosted in a webserver for further accessibility. PDSOE provided an in the box tomcat server. Ie., starting from 11.2 release when you install PDSOE (Progress Developer Studio for OpenEdge) we also install Tomcat server. I will show more while I am demoing things. The respective REST application is zipped as a WAR file and is placed in the ‘Webapps’ directory. The ‘Webapps’ directly is available under $DLC location for a default tomcat that gets shipped with PDSOE. OE Webserver is listed by default

REST Expose Editor REST Expose Editor is used to
REST Projects in PDSOE REST Annotations to ABL Files REST Expose Editor Publishing and Packaging OE REST Appl OE Web Server and REST Services REST Expose Editor is used to Create resources Define a mapping between exposed ABL routines and Verbs From the REST Expose Editor you can: Manage the REST resources defined for the REST service Associate REST verbs, HTTP methods, with the exposed ABL procedures Map the input and output parameters REST Expose Editor is the place where one can create set of resources and also perform mappings directly to ABL resources and HTTP verbs. PDSOE provided an extensible editor such that one can perform easy way of mapping through Drag and Drop functionality. Where in user can perform Input and Output mappings directly from this Editor. Resource URI is also calculated from the same REST Expose Editor.

Servers in PDSOE OpenEdge REST applications need two types of servers
REST Projects in PDSOE REST Annotations to ABL Files REST Expose Editor Publishing and Packaging OE REST Appl OE Web Server and REST Services OpenEdge REST applications need two types of servers OpenEdge AppServer (restbroker1) OE Web Server (restmgr1) Servers can be stopped and started from Servers view in PDSOE Other Approaches Proenv command line OpenEdge Explorer / OpenEdge Management Server operations (Start/Stop) can be done from the server’s view Publishing/Clean operations can also be done from the server’s view. Once the Application/Service is published to OE Webserver appropriate status of the servers moves to Synchronized. Also respective status of the server is shown in the server view. By default the servers are listed in the Server’s view. Server view which is same as 10.2B and We have added couple of servers/brokers to support REST and Mobile things in 11.2 ie., a default OE Webserver and restbroker are available by default in the Server’s view. One can easily perform Start/Stop operations directly from the server’s view. Also make sure that respective states are available for the application and server in the Server view.

Publishing Resources to OE Webserver
REST Projects in PDSOE REST Annotations to ABL Files REST Expose Editor Publishing and Packaging OE REST Appl OE Web Server and REST Services OE Web Server resources Defined Service required Configured to publish on server Published to application directory Here you can observe the summarized information of the REST applicatio. Once service is created in PDSOE that is available under ‘Defined Services’ node in the Project Explorer, which is then associated to respective Server through Server’s view. This is how folder/directory hierarchy in the disk once the services are published using server’s view from PDSOE. All the WAR files are exploded and are placed in webapps directory.

Status of OE Web Server [Stopped] - Initial State after PDSOE Launch
REST Projects in PDSOE REST Annotations to ABL Files REST Expose Editor Publishing and Packaging OE REST Appl OE Web Server and REST Services [Stopped] - Initial State after PDSOE Launch [Starting] During the process of starting OE Web Server [Started] Successful start of OE Web Server. [Started, Synchronized] Application is published properly [Stopped, Synchronized] - Web Server stopped and app available [Started, Republish] When Application is changed in PDSOE [Synchronized][Published] Application is in sync or up-to date [OE Web server not started] - Webserver not started yet This slide speaks about different states of server and the application/service that is associated to REST manager (or OE Webserver). Most of the status(es) are self-explanatory. However, following are few of key status (Started, Synchronized) which says the application is upto date in the OE Webserver and the server is started. The other one is (Started, Republish) resembling the OE Webserver was started and there are few changes in the deployed/published application which needs a republish. By default the changes are republished automatically without any manual intervention by the user.

AppBuilder Integration Seamless Appbuilder Integration with PDSOE ABL Scratchpad Running ABL code snippet on the fly REST Introducing ABL to REST world The next outstanding feature is the support for Mobile. I think most of you have attended the mobile session which Shelley Chase has given where all the architectural details of the mobile are provided. I will give a brief touch up on PDSOE related things in OE-Mobile. Mobile Build Apps faster and get to market quickly

OpenEdge Mobile Complete Mobile application development and deployment can be done directly from PDSOE and all Mobile specific artifacts for iOS and Android can be generated with minimal steps. Mobile App Creation Business Entity and Mobile Service Mobile AppBuilder Options Running Mobile Application OpenEdge Mobile is one stop solution for developing mobile applications from PDSOE. Build your apps quickly and deploy to devices directly from PDSOE.

Mobile App creation as part of Mobile Project
Business Entity and Mobile Service Mobile AppBuilder Running Mobile Application from PDSOE Creates project (or a mobile application) in cloud Requires user credentials (PSDN) for Mobile App Builder Choice of App types Device (Phone or Tablet) Predefined Templates Twitter App Weather App From backup Existing Mobile App Optionally user can associate to OE Web Server - A new Mobile App wizard is provided such that user can create a new mobile application directly from PDSOE. Everyone also uses tablets in our day to day life along with phones. So we also provided couple of options like Phone, Tablet in the same page such that user can select specific application during the application creation. - Inorder to have a complete End to End working application, we have provided couple of templates namely Weather and Twitter such that he/she can create complete application directly instead of a blank application

Mobile Project Folder Hierarchy
Mobile App Creation in PDSOE Business Entity and Mobile Service Mobile AppBuilder in PDSOE Running Mobile Application from PDSOE Mobile Apps Contains the mobile apps that are creates in the Mobile project AppServer Contains the files (business logic) to be publish to the server RESTContent Contains the files that will be used for generating a Mobile service (WAR) file WebContent Contains the Progress JavaScript Data Object (JSDO) files: progress.js, progress.session.js, and the .json files Defined Services Contains a list of defined/created Mobile and REST services. This is how the Project hierarchy is shown for a mobile project in the Project Explorer. Mobile Apps: This node contains all of the mobile applications that are created as part of the Mobile project Appserver: It is the placeholder for the ABL Business logic. What ever the ABL Code that is part of this module (Appserver) is published to respective publishing directory (in the file system) RESTContent: It contains REST metadata. Basing on these files, WAR file is generated WebContent: Which contains files like progress.js and progress.session.js as a combination we term it as JSDO. These two files are created along with new OpenEdge Mobile Project Defined Services: This contains list of all REST and Mobile services that are part of the project.

Business Entity Resembles same as that of ABL Class wizard
Mobile App Creation in PDSOE Business Entity and Mobile Service Mobile AppBuilder in PDSOE Running Mobile Application from PDSOE Resembles same as that of ABL Class wizard Contains ABL Business Logic Default CRUD operations/methods are generated with stubs Schema file selection is allowed such that CRUD operations are generated on top of selected schema Decorated with Mobile annotations such that they can be exposed as mobile services Method types Business Entity is the new term that was introduced in 11.2 PDSOE. Which will give default CRUD (Create, Read, Update and Delete) operations by defining a schema in the same ABL file. BE is same as an ABL Class file and few options are provided in the second page One can expose the methods that are created as part of Business Entity to Mobile compatible. A skeleton code for all CRUD operations is provided as part of Business Entity class file.

Mobile Service Mobile App Creation in PDSOE Business Entity and Mobile Service Mobile AppBuilder in PDSOE Running Mobile Application from PDSOE Mobile Service is a combination of REST and some specifics of Mobile Mobile service can be created for a Business Entity A mobile service results in REST (resourceModel.xml, mapping.xml) and Mobile artifacts (.json) in PDSOE <service name>.json file is one of the outputs of mobile service JSON file contains complete information (schema, operations) of the mobile resources A mobile service is which enables mobile resources to be available globally as a prerequisite one need to have an ABL file (in our case a Business Entity) which has mobile annotations Contains all of the REST artifacts and mobile one’s (JSON file) Generated JSON file will be integration point between PDSOE and the Mobile App Builder JSON file enables us to create set of JSDO services in Mobile Appbuilder A JSDO service is created for each routine available as part of the Business Entity

Mobile App Builder Options in PDSOE
Mobile App Creation in PDSOE Business Entity and Mobile Service Mobile AppBuilder Options Running Mobile Application PDSOE allows user to perform following options on a mobile application Open Run Backup Local Copy Source Local Export Local Delete Rename Android (.apk) and iOS (.ipa) files are generated based on the Project Properties settings Deleting an application in PDSOE removes from Cloud as well. - As you all know that creating a mobile application/project creates one application with the same name in the Mobile Appbuilder. Users can operate on the same application directly from PDSOE with these context menu options. Ie., couple of context menu options are provided for a given mobile application in PDSOE. Users can easily all respective mobile artifacts like Android and iOS directly from PDSOE by setting appropriate value in the Project Properties page. Be cautious enough when deleting a project or application from PDSOE as it will also delete appropriate application in the Mobile Appbuilder.

Publishing Mobile App and Mobile Service
Mobile App Creation in PDSOE Business Entity and Mobile Service Mobile AppBuilder in PDSOE Running Mobile Application from PDSOE Complete Mobile Project constitutes both Mobile Application and Mobile Service Same OE Web Server is used for publishing both Mobile Application and Mobile Service Two different .WAR files are published to OE Web Server Publishing a mobile application does: Get sources from Mobile App Builder Package it as WAR file Publish to Tomcat directory. This is same as that REST Application publishing to OE Webserver as we have seen in the REST demo. However, make sure there are two WAR files that are used for a complete mobile application. Ie., one for the Mobile Service and other is for the Mobile Application. Both of them are packaged as individual WAR files and are published to OE Webserver. Publishing an application performs couple of operations like fetching the latest files from Mobile Appbuilder, Package as WAR file and then publish the same to the OE Webserver or the tomcat directory. Observe that same OE Webserver is used for both Mobile and REST App developments.

Run Options for Mobile Application
Mobile App Creation in PDSOE Business Entity and Mobile Service Mobile AppBuilder in PDSOE Running Mobile Application from PDSOE Run Local Sources will be copied to local file system if not done already Run on Server Application should be published properly to OE Web Server Either of options opens specific application in the emulator Machine name is populated by default in the Run Configuration dialog for ‘Run on Server’ Once mobile application is published or deployed to OE Webserver, one can run the specific mobile application using ‘Run Configurations’ section. A new configuration namely ‘Progress OpenEdge Mobile Configuration’ is added to existing Run Configuration dialog Couple of options like ‘Run locally’ and ‘Run on Server’ options are provided for the same such that user can execute specific mobile application.

D I S C L A I M E R Further part of presentation includes information about future products and/or product enhancements. What we are going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here. This is a standard Disclaimer slide as we are about talk on upcoming features of 11.3 release. D I S C L A I M E R

Express Mobile Application Complete Mobile Application in single click OE-Corticon Integration Create Business Rules to any OpenEdge application with no-coding efforts and with minimal Corticon knowledge PDSOE support for Win 64 Bits ABL Developers can use Win 64 platform for their application development starting from 11.3 Infragistics and JRE Upgrade .NET Ultra controls upgradation to latest version of Infragistics Seamless Integration to OEBPM Unified installer for both PDSOE and OEBPM Here goes the set of new features that are (planned for) about arrive in PDSOE 11.3 release of OpenEdge . Lets go through each of them in detail.

Express Mobile Project
Express Mobile Application OE-Corticon Integration Support for Win64 Bits JRE and Infragistics Upgrade Other Enhancements New option introduced in the Mobile Project Creation wizard Complete Mobile application is achieved with single click Predefined template is added for the Mobile Project Set of prerequisites that are to be satisfied prior proceeding One Click Project completion Finishing Project opens mobile screen in the Emulator You have seen all the steps that are involved in the complete End to End working mobile application. To make this very much simpler we have given a new project called Express Mobile Project, which will allow users to create a complete working End to End application from a single wizard given a database table. However, user has to satisfy couple of prerequisites for achieving this (Like starting OE Webserver, RESTBroker and setting credentials in the Preferences page…) What all will happen behind the scenes… New Mobile Application Creation with selected template Business Entity with DB table as Schema and proper CRUD operations for the specific schema. Mobile Service for the same Business Entity Publish both Mobile Application and Mobile Service to OE Webserver (Tomcat directory) Run and launch specific application in Emulator.

OpenEdge / Corticon Integration
Express Mobile Application OE-Corticon Integration Support for Win64 Bits JRE and Infragistics Upgrade Other Enhancements Progress Developer Studio for OpenEdge Export ProDataset/Temp-Table schema from PDSOE ABL is master (i.e. no round-tripping, sync) Proprietary interchange format (.brvd) “Corticon Runtime for Development” provides testing capabilities for ABL developers Corticon Studio Import PDS/TT schema Create entities, attributes, associations Mark imported schema as read-only Re-import without redefining rules or custom additions ABL API For invoking the decision services through ABL OE-Corticon Integration, one of the key features of Which enables ABL developers to make use of the rules that are developed in the Corticon Studio. With this integration, an ABL developer can export ABL Schema (proDataset or temp-table) file as an intermediately file to Corticon studio ie., we call it as .brvd (Business Rules Vocabulary Definition). This file inturn is used in the Corticon Studio for the development of rules (Rulesheets and Rule Flows). Once the rules are created they can be directly deployed to Corticon Server or the OE Webserver as decision services. The deployed services can be directly invoked/called in your ABL Application using couple of ABL API’s provided as part of 11.3 installation. Deployment Cases Rules and ABL deployed as one package Rules are modified after deployment of ABL, and changed regularly

Win64 support for PDSOE ABL Client in Win64 (prowin.exe)
Express Mobile Application OE-Corticon Integration Support for Win64 Bits JRE and Infragistics Upgrade Other Enhancements ABL Client in Win64 (prowin.exe) Support for all features of PDSOE PDSOE supports and ships for JRE/JDK 1.7 PDSOE 11.3 ships with latest version of Infragistics (13.1) inclusive of .NET 4.0 support New Controls: Ultra ganttview print document Ultra touch provider Ultra Control’s help in generic browser. - New installer for 64 bit is available for PDSOE starting from 11.3 ie., Users can start working with GUI clients in nt64 platforms as well starting from 11.3 release. All of PDSOE features are available as part of Win64 changes (inclusive of new Appbuilder Integration) We have also upgraded our JRE/JDK to 1.7 versions. Also, we have upgraded the Infragistics (.Net) controls to latest 2013 vol 1 version which brings us couple of new controls to Visual Designer development namely ‘Ultra ganttview print document‘ and ‘Ultra touch provider’

Install Changes Unified installer for PDSOE and OEBPM
Express Mobile Application OE-Corticon Integration Support for Win64 Bits JRE and Infragistics Upgrade Other Enhancements Unified installer for PDSOE and OEBPM Removal of multiple instances/installations of PDSOE support Removal of .NET 2.0 Disk Layout changes of the PDSOE installation. Further installation to existing instances of PDSOE is no more allowed from 11.3 PDSOE. Installing only PDSOE component brings us all the PDSOE and BPM Studio plug-ins for effective development of OE and BPM things. Now the $DLC points to ‘oeide’ location in the installation. No ‘DeveloperStudio’ directory structure will be available from 11.3 version of PDSOE. Also starting from 11.3 PDSOE Ultra Control’s help is opened up in the generic browser instead of new window that gets opened prior 11.3 releases.

www.progress.com/exchange-pug October 6–9, 2013 • Boston #PRGS13
Special low rate of $495 for PUG Challenge attendees with the code PUGAM And visit the Progress booth to learn more about the Progress App Dev Challenge! We have Progress Exchange happening in the month of October Please do attend the same to know most happenings at Progress Software. Please stop by near Progress stall/booth available near stalls area for complete details.

With this I open up floor for any questions.
Thank you Very much.

Maximizing productivity with Progress Developer Studio for OpenEdge 11

Similar presentations

Presentation on theme: "Maximizing productivity with Progress Developer Studio for OpenEdge 11"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Maximizing productivity with Progress Developer Studio for OpenEdge 11

Similar presentations

Presentation on theme: "Maximizing productivity with Progress Developer Studio for OpenEdge 11"— Presentation transcript:

Similar presentations

About project

Feedback