Difference between revisions of "Common Presentation"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 8: Line 8:
As to solution specific needs resources will be stored in two places with the following structure.
As to solution specific needs resources will be stored in two places with the following structure.


==SVN==
== Solution Specific GUI Resources ==


e.g. FACES
Each svn project keeps a part of it's presentation (JS won't be separated to avoid cross side scripting)
 
/$solution$_presentation/src/main/webapp/resources
 
 
The foldes should look like that (pls. merge additional image/script locations to what is documented here):
 
- resources
-- commonJavaScript (should be kept in synch with other solutions)
--- componentJavaScript (contains JS used in common components)
--- externalJavaScript (3rd party JS resoures)
--- jquery (The jQuery framework)
--- eSciDoc_javascript.js: Installs component scripts and holds general JS
--- main.js: Loads main functions
 
-- $solution$Images (contains overrides for images used by solutions only: static Startpage Images, Logos, ...)
--- ...
--- ...
 
-- $solution$JavaScript (contains solution specific JS plus plugins, if only used here)
--- ...
--- ...
 
 
The common part of the presentation will be stored here: https://zim02.gwdg.de/repos/common/trunk/common_services/common_presentation/


<pre>
- 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)
</pre>


== New Common GUI Resources ==


The common part of the presentation will be stored here: https://zim02.gwdg.de/repos/common/trunk/common_services/common_presentation/src/main/resources/


<pre>
<pre>
-- cssFramework (contains the css for all solutions)
-- cssFramework (contains the css for all solutions)
--- componentCSS
--- componentCSS
--- globalImages
--- globalCSS
--- globalCSS
--- themes (themes and standard skins are all stored here, and will be deployed as needed)
--- themes (themes and standard skins are all stored here, and will be deployed as needed)

Revision as of 08:29, 12 October 2010

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 Specific GUI Resources[edit]

Each svn project keeps a part of it's presentation (JS won't be separated to avoid cross side scripting)

/$solution$_presentation/src/main/webapp/resources


The foldes should look like that (pls. merge additional image/script locations to what is documented here):

- resources -- commonJavaScript (should be kept in synch with other solutions) --- componentJavaScript (contains JS used in common components) --- externalJavaScript (3rd party JS resoures) --- jquery (The jQuery framework) --- eSciDoc_javascript.js: Installs component scripts and holds general JS --- main.js: Loads main functions

-- $solution$Images (contains overrides for images used by solutions only: static Startpage Images, Logos, ...) --- ... --- ...

-- $solution$JavaScript (contains solution specific JS plus plugins, if only used here) --- ... --- ...


The common part of the presentation will be stored here: https://zim02.gwdg.de/repos/common/trunk/common_services/common_presentation/


New Common GUI Resources[edit]

-- cssFramework (contains the css for all solutions)
--- componentCSS
--- globalImages
--- globalCSS
--- 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

As the logo needs to be separated from the common graphics it will be included in the standard includes JSP of the solution.

The following folders could be moved:

  1. eSciDoc_CSS_v2/
  2. favicon.ico
  3. images/ (??)
  4. skins/

Builds[edit]

Common presentation will be defined as dependency.

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.