Difference between revisions of "User Interface Components"
Jump to navigation
Jump to search
m (New page: =Development of Reference HTML= All eSciDoc interfaces should derive from a defined set of HTML Reference components. [https://zim01.gwdg.de/repos/smc/trunk/04_Design/03_GUI_Design/03_in...) |
m |
||
| Line 30: | Line 30: | ||
#View Item | #View Item | ||
=Implementation of JSPF Structure= | |||
A JSPF is built upon one or more blocks of the Reference HTML. To prepare the JSPF structure a HTML component is separated in reusable snippets and | A JSPF is built upon one or more blocks of the Reference HTML. To prepare the JSPF structure a HTML component is separated in reusable snippets and | ||
Revision as of 09:05, 7 November 2008
Development of Reference HTML[edit]
All eSciDoc interfaces should derive from a defined set of HTML Reference components.
Header Section Components[edit]
- Meta Menu
- Logo
- Search Menu
- Main Menu
Common Content Components[edit]
- Content Menu (Options, Actions)
- Breadcrumb
- Title
- Status
- Message (Optionally)
Content Components[edit]
- Paginator
- Grid List (Not R4.0)
- Bibliographic list (short and medium)
- Bibliographic list (simple)
- Wizard
- Edit Item
- View Item
Implementation of JSPF Structure[edit]
A JSPF is built upon one or more blocks of the Reference HTML. To prepare the JSPF structure a HTML component is separated in reusable snippets and nested into the JSPF.
JSPFs[edit]
- Application layout
- List Items
- View Item
- Edit Item
- ...
After a JSPF is prepared, UIE hands it over to Dev/Presentation for debug and implementation into the presentation layer. If implementation leads to a change of the intended appearance the JSPF needs to be fine tuned by UIE again.