The OAK-Frontend Environment offers a Graphical User Interface (GUI) editor to allow vApp developers the implementation of end-user interfaces for their solutions. The editor will be accessible from within the OAK Studio as a plain browser consuming external microservices. These services provide large ranges of visual templates implemented in HTML5 + CSS3. Developers can combine them within the GUI editor to achieve enclosed vApp visualisations at the end. The templates can stand for themselves (eg customised GUI elements) or contain/bind to additional behaviour and JavaScript logic (eg registration forms or error representation). vApp developers thus will have a high degree of flexibility and power as there are barely any restrictions in merging templates. The OAK Frontend Environment will still develop an abstraction layer concept, subordinating the entities into abstraction levels. This strategy will produce additional guidance for the developer and speed up the process of rapid prototyping. The editor also allows the inheritance of external configuration like translations for internationalisation, as well as internal, individual configurations / attributes for each template itself.
This vf-OS module is subdivided in lower-level modules:
- The Client- Module consists out of nothing more than one single HTML file, processing user inputs and forwarding them to the mirco services module, where necessary calculations for representing vApps take place.
- The Server- Module consists out of multiple Mircoservices working together, which listen to user inputs and transform them into clickable prototypes of a vApp.
This page includes the Code developed to implement this module.
Additionally, this page includes a Tickets entry to handle specific issues regarding this module as a whole (which may include management, integration, new features, etc.).
Module Development:
Development Status: OAK Frontend
Responsible: Gerrit Klasen (ASC), Bastian von Halem (ASC)
Other Participants: (none)
Requires: (none)
Dependents: