PSC has created AutoEdge as an example application example to illustrate the OpenEdge Reference Architecture. The idea and purpose of AutoEdge is to provide practical definition and examples of OERA and illustrates many aspects of modern ABL and Sonic code and technique. AutoEdge is what an application, with certain ‘business requirements’, might look like if architected and designed following the OERA guidelines.
The complete AutoEdge kit is available here
Using all features of the complete kit requires OpenEdge 10.1A including Sonic, WebSpeed, AppServer, and IIS. The more recent version of the installer is supposed to allow you to install without all of these in place, but there are certainly aspects of the application which you can't try without all of this.
If you want to just look at the code, you can download it here
This project on OE Hive is intended to supplement what is available from the PSDN downloads and forums with additional materials and commentary.
Issue tracker for Progress Software's AutoEdge reference implementation of OERA.
One of the remarkable aspects of the AutoEdge application is that it is provided with an unusual amount of documentation. One of the categories of this documentation is the "Project" documentation, which covers programming and naming standards, UI guidelines, and an overall documentation of the structure. It is unlikely that everyone will agree with the choices made in this documentation, indeed, it seems apparent that the team that did the work learned from the experience and would do some things differently if they had to do the whole thing all over again. This node has been created in order to provide a place to exchange different points of view about these design documents.
From the introduction:
"This document outlines a set of Programming standards and naming conventions to be used on the OpenEdge Application Example application. These standards are a culmination of many other works including guidelines from education, John Sadd’s whitepapers and the Developers Guide."
The document is provided both in its original form and with a series of comments by Thomas Mercer-Hursh. The commented copy is complete in all respects so you do not need both copies, but if someone wishes to do a similar annotation, then they might want to start with a clean copy.
Simpler or shorter comments can be attached directly to this page.