Difference between revisions of "Common Presentation"
m (→First Step) |
|||
Line 5: | Line 5: | ||
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. | 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= | ||
As to solution specific needs resources will be stored in two places with the following structure. | |||
==Solution Project SVN== | |||
e.g. FACES | |||
<pre> | |||
- solutionResources | |||
-- facesJavaScript | |||
-- facesImages | |||
</pre> | |||
commonResources | |||
* How/where can these resources be stored during development? | * How/where can these resources be stored during development? |
Revision as of 10:33, 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.
Solution Project SVN[edit]
e.g. FACES
- solutionResources -- facesJavaScript -- facesImages
commonResources
- How/where can these resources be stored during development?
Could be stored here: https://zim02.gwdg.de/repos/common/trunk/common_services/common_presentation/
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]
- RichFaces proved to be a nice way for dynamic stuff DARIAH/imeji
- RF components can be styled flexible
It doesn't make sense anymore to grab more jQuery stuff for future development while more and more RichFaces components are used.
- how and when to phase out jQuery?
- where to store additional css classes for jQuery?
- how to plug in additional jQuery stuff into JSF/RichFaces (if possible/necessary)?
Doesn't make sense time. JS can't be unified on short term base.
A separate css file should be created to overwrite richfaces scc: rich_overwrite_js.css.