Edo6 was a private commercial project developed as the definition and implementation platform for the Ecensity EPS product. 

Edo6 is an interpreted server side programming language designed for extreme flexibility in the use, construction and personalization of its applications.  Business analysts manage an application system on behalf of groups of users in a production environment.  Application construction, management and reconfiguration features.

A commercial report from radell.es describes Edo6.

EDO: Ecensity Scripting Language

Ecensity’s XML-based scripting language is a revolutionary way to describe both presentation and interaction of user views.  Similar to Business Process Execution Language (BPEL), where business processes are described in an XML-based language, the EDO language allows the presentation layer to be created descriptively.

Such an approach has many advantages, not least is the speed at which the presentation layer can be created.  In a recent “blind” test conducted by Ecensity, in conjunction with a customer, EDO was found to take approximately 20% of the development time, as compared to a traditional development language.

Since EDO is by its very nature descriptive, it can be easily picked-up by non-development personnel, either in its XML form or in conjunction with any number of widely available design environments, including FrontPage, Dreamweaver or the Altova product suite.

To make development of SOA Presentation Services a highly productive experience, Ecensity provides its own visual toolset for rapid creation of Displets (Designer) and for simple construction of configurable applications (Composer). [Ed. All implemented in EDO and delivered in source].

The EDO language has been developed on top of [Ed. rather, As] an object-based model and this model is also inherent in EDO. Re-usable objects, Displets and Functions, form the basis of the presentation layer.  Many of these objects will be re-used multiple times within an application.  Development times are thus significantly reduced.  Re-composing applications to meet individualized requirements is a dramatically simple process.

Portlets and Displets

Displets are developed with EDO and do not require any interface as their basic containers are also EDO programs.  The granularity of what a Displet symbolizes can vary.  From simple visual components to sophisticated Presentation Services, a Displet can represent any presentation object such as a Form, a tabular view, a tree, a Report, a summary of information, a command bar buttons, a graph, a master/detail …

This core difference makes it straightforward for Displets to deliver productivity and cost-effective, interoperable re-use in meeting the challenges raised by evolving business requirements.  In essence, Displets represent the fastest and easiest way to construct and compose portlets that need to integrate composite views, for use in multiple portal environments, by multiple users.