Difference between revisions of "User Interface Components"
Line 8: | Line 8: | ||
https://zim01.gwdg.de/repos/smc/trunk/04_Design/03_GUI_Design/03_interface_development/eSciDoc_Component_Library/ | https://zim01.gwdg.de/repos/smc/trunk/04_Design/03_GUI_Design/03_interface_development/eSciDoc_Component_Library/ | ||
==CSS== | |||
All CSS is invoked by the main CSS. It calles at first the core CSS framework: | |||
Revision as of 09:21, 1 March 2010
APPLICATION AREAS |
---|
|
PROJECTS |
Research- and Metadata Handling Corporate & Interface Design (under Rework) |
edit |
Development of Reference HTML[edit]
All eSciDoc interfaces should derive from a defined set of HTML reference components. The html-components are hosted here. As implementation is always a bit ahead they may not be in sync to the JSPs. This is also the place where an online pattern library will be forthcoming to offer access to third party development as well:
CSS[edit]
All CSS is invoked by the main CSS. It calles at first the core CSS framework:
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.