"mholzner" wrote : here are some more ideas (way out there, I know ;):
|
|
| * an incoming request contains the page name (or it defaults to a name)
| * the request/session contains the user information
| * the request contains information about the client device and the
supported mime types
| * based on the page name, user name, and mime type a pageLayout is
determined (from a page-layout registry ?)
| * the layout is a JSP with mime type specific markup, and optional custom
tags
| * based on the page name, user name, and mime type a skin is determined
(skin registry ?)
| * the skin is a separate WAR containing a skin descriptor file, one or more
css and/or js files, and optional media files (images)
| * the information about the skin (skin name) is set into the request
| * the request is dispatched to the determined layout jsp
| * the custom tags on the jsp can be one or more of the following:
| - <jbp:title exp="#{someBean.someMethod}">
| - <jbp:skin/> to use the determined skin, or <jbp:skin
name="myVerySpacialSkin"/> to overwrite the determined skin
| - <jbp:region name=""/> as already described by Patrick
|
| * the skin tag reads the skin Name from the request, gets the WAR context
information of that skin from the skin registry, and injects the appropriate
link and script tags with url's pointing to the skin resources
| * a skin descriptor could look something like:
|
|
|
|
|
|
|
| * it would make sense to define a set of well-known css classes that need
to be defined by all skins, and are used by the markup produced by the custom
tags
| * by having the custom tags only emmit div tags, we would have ultimate
flexibility (see http://www.csszengarden.com/)
|
|
| some things to consider, clarify:
| * if the layout.jsp is xhtml compliant, it would be much easier to write a
portlet that can allow a user to dynamically assign portlets to a region via
drag and drop
| * this approach would limit the skin API to custom tags that talk to the
page registry
| * layouts and themes are the domain of web designers. The tools they know
are design tools and WebDAV. How could jbp allow designers to define skins and
layouts and make them available to the portal via webDAV
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866271#3866271
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866271
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
