Difference between revisions of "Common Presentation"
m |
|||
| Line 57: | Line 57: | ||
=JavaScript Strategy= | =JavaScript Strategy= | ||
If dynamic patterns are needed UIE checks http://livedemo.exadel.com/richfaces-demo/richfaces/actionparam.jsf?s=darkX to suggest one. If feasability is given overwrite style can be written to extend css. | |||
jQuery can't phase out at this point in time. Manual JS scripting is also still necessary. | |||
A separate css file should be created to overwrite richfaces scc: rich_overwrite_js.css. | A separate css file should be created to overwrite richfaces scc: rich_overwrite_js.css. | ||
Revision as of 12:14, 6 October 2010
| APPLICATION AREAS |
|---|
|
|
| PROJECTS |
|
Research- and Metadata Handling Corporate & Interface Design (under Rework) |
| edit |
Precondition[edit]
CSS/JS resources in the presentation layer are maintained redundantly across solutions. As GUI 2.0 is common for all solutions it can be maintained and deployed in a more common manner to prevent diverging sources.
Places[edit]
As to solution specific needs resources will be stored in two places with the following structure.
SVN[edit]
e.g. FACES
- solutionResources (contains all solution specific GUI stuff)
-- facesJavaScript (contains solution specific JS plus plugins, if only used here)
-- javaScript (contains common JS and the jquery core)
--- jquery
-- componentJavaScript (contains JS used in common components)
-- facesImages (contains favicon, startpage images and the like)
The common part of the presentation will be stored here: https://zim02.gwdg.de/repos/common/trunk/common_services/common_presentation/src/main/resources/
-- css (contains the css for all solutions) --- componentCSS --- themes (themes and standard skins are all stored here, and will be deployed as needed) ---- skin_skin1 (contains logo, icons as well) ---- skin_skin2 ---- skin_skin3
Problem: jQuery vs. RichFaces ($)
The following folders could be moved:
- eSciDoc_CSS_v2/
- favicon.ico
- images/ (??)
- skins/
Problem: Logo is solution specific and needs a different folder: move to PNG.
- How should resources be fetched when deployment happens?
Common presentation will be defined as dependency.
- How/Where are stored for productive solutions?
Should stay like it is now. Will be done like PubMan if an installer is made.
Flexibility[edit]
- Is there a need to address solution specific parts of the presentation separately?
JavaScript Strategy[edit]
If dynamic patterns are needed UIE checks http://livedemo.exadel.com/richfaces-demo/richfaces/actionparam.jsf?s=darkX to suggest one. If feasability is given overwrite style can be written to extend css.
jQuery can't phase out at this point in time. Manual JS scripting is also still necessary.
A separate css file should be created to overwrite richfaces scc: rich_overwrite_js.css.