There are several must-to-know concepts implied in the cloud toolkit, which have to be understood before getting started. Some of them are closely related to the dynamic applications nature and behavior, others just follow the best practices from the service architecture reflected also in the cloud applications.
First comes the concept of a Repository. It is the place where the applications content is stored - such as a database for the Dirigible's instance.
Next is the concept of a Workspace, which is very similar to the well known workspace from desktop IDEs e.g. Eclipse. The workspace can hold one or more projects. One user can have multiple workspaces, but can work in one only at a given moment of time.
Registry and the related publishing processes are taken from the SOA (UDDI) and recent API Management to bring some of the strengths, such as discoverability, reusability, loose coupling, relevance, etc.
To boost the development productivity at the very initial phase, we introduced template-based generation of application artifacts via wizards.
The new Web 2.0 paradigm and the leveraged REST architectural style changed the way of how services should behave as well as how to be described. Although there is push for bilateral contracts only and free description of the services, we decided to introduce a bit more sophisticated kind of services for special purposes - Entity Services.
There are several editors currently available that provide visual definition of application artifacts such as Database Schema Models, Entity Data Models and BPMN Processes.
Along with the low level HTTP request, response and session handling, Dirigible provides a higher level framework for building REST services. More information on how to use this framework can be found here.
The client-side application code transported via the container web channel. Mode information can be found here
Mobile application support in Eclipse Dirigible is achieved via Tabris.js.