yes, this is intended to be used and altered by developers. I just haven't gotten around to provide proper documentation. We also kept it a bit in the closet since we still try to figure out the correct connection to themes. My 'perfect world' would look like this: the render set generates a set of xhtml tags with well known class and id attributes. the theme would match on those classes and attributes . This would give us a portable theming / skinning model where skins (themes) can be freely exchanged and swapped on the fly. For that to work, we need to define the correct set of classes and ids that every theme has to follow. Since I'm not a web designer, I'm depending on input from others for this. Unfortunately, my designer friends here have lots of ideas, but still no time. .... long story, sorry ;) ...
back to reality: you can change the existing render set in the core, or provide your own. render sets can be deployed independent of other portal artifacts, so you could wrap one in a war and deploy it, the portal will pick it up (as long as you provide the /WEB-INF/theme/rendetSet.xml descriptor) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886375#3886375 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886375 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
