I was giving this some thought today. I was thinking of a scheme of breaking a theme into two separate pieces, a page-renderer and a css-based skin.
Skins could be packaged in an uploadable archive (.skar maybe?? :) ) consisting of one or more .css files and images/other resources. The portal or renderer would be responsible for serving up this content in a skin-specific context (to avoid browser caching of images from other skins). This would make on-the fly skin changes extremely easy. The page-renderer would be responsible for the creating the basic structure of the page. New page renderers would only be needed for themes that couldn't accomplish their look with the default structure, adding support for new portal window states, and so on. This wouldn't have as much need to be changeable on-the-fly. I can try to throw together some html mock-ups this weekend to illustrate the concept, if that would help. What do we think? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865276#3865276 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865276 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
