The benefit of the LCHH architecture is that its execution path is identical to the life cycle of an HTTP request. The Server-side scripts then perform updating, insertion or deletion functions before piggybacking the updated View back to the original Loader via AJAX callback and DOM update. These JavaScript handlers then sends XmlHTTPRequestObject or AJAX requests to Server-side Handlers. Visual affordances, also known as "triggers" that are included in the Content invoke client-side handlers. In the LCHH architecture, a Loader, or a "DIV" container with a unique identifier is populated with default Content.
Gyroscope uses the Loader-Content-Handler-Handler LCHH architecture instead of explicit Model-View-Controller MVC. Gyroscopes tab system ensures that no duplicate tabs can open for the same record. They are logically tabs within the web application. Clicking on an actor would pivot the view, by displaying in a separate tab, the basic information of the actor, putting his/her related films on the side. For example, in a Film-Actor database where a film may have multiple actors, and an actor can be in multiple films, the Film details view lists the actors on its "Related Records" section. Many-to-many N-N relations are displayed as two 1-N views mirroring each other. Click on a contact item will open the contact details in a separate tab. The "Related Contacts" are listed on the side.
In the tabbed company record view, the basic information such as company name and address are displayed in the main section of the details view. In the "Companies" list view, each item points to a Company record. For example, in a Company Directory application a company may have multiple contact persons.
One-to-many 1-N relations are shown in the form of "Related Records". Each item in the list view opens the record in a Tab where the rest of the columns are displayed in a key-value format. The most significant columns in a data table are used to display the records in a "List View". For example, tables are typically shown as "Entry Points". The Gyroscope UI represents typical data relations such as one-to-many, many-to-many and foreign-key-reference with application-level visual concepts.
0 kommentar(er)
