Difference between revisions of "Common Presentation"
Jump to navigation
Jump to search
m (→First Step) |
|||
| Line 30: | Line 30: | ||
# where to store additional css classes for jQuery? | # where to store additional css classes for jQuery? | ||
# how to plug in additional jQuery stuff into JSF/RichFaces (if possible/necessary)? | # 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. | |||
</div> | </div> | ||
Revision as of 13:26, 29 September 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.
First Step[edit]
One starting point should be to clarify:
- 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 ($)
- How should resources be fetched when deployment happens?
- How/Where are stored for productive solutions?
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.