The usage interface section of entity files is subject
to the same straightforward rule previously discussed
for sections DB and LOGIC: it may only contain
any number of field collections. Typical collections
for section UI include graphical user interfaces
for human users,
complete with grid layout directives - as shown below -,
and packetized contents descriptors for automatic
interapplication communication and for data or service
The sample mold for section UI produces an HTML file
containing a GUI form to edit or view data fields of the entity
processed by the Sisendel translator. The next illustration shows
the HTML form for
employee, derived from collection
employee.UI.full_view. An overlay grid shows the layout
correspondence between the textual description contained
in the entity file and the generated HTML form.
Figure 3 - From employee.UI.full_view to "employee.html"
It should be noted that fields a and b of entity
employee are embedded entities of type person and
person_info respectively, and thus employee.UI.full_view
appropriately embeds person.UI.full_view (marked by "a" in the
grid) and person_info.UI.full_view (marked by "b" in the grid).
The result of processing collection employee.UI.compact_view
is illustrated below, within the full_view of entity
project. The latter entity uses a list of employees in its
full_view and therefore - by sample project convention -
embeds three instances of employee.UI.compact_view at the
bottom of its HTML form.
Figure 4 - employee.UI.compact_view within "project.html"
[Back to top]