As I mentioned in the first post, the separation of content and the rest via css is a good thing. The portlet spec defines a set of css classes and ids , taken from the wsrp 1.0 spec, that fit nicely with this approach. WSRP 2.0 is completing this set of classes and ids. So I'd like to propose to follow this approach, and define a set of classes and ids , by taking what is in wsrp 2.0 , and completing it if necessary. The portal will render a set of div and span tags with these class and id attributes. The css from the theme can then handle the rest (position, color, font, etc.)
If you can't go with this approach for whatever reason, you can still create your own layouts, render set and themes and just use the infrastructure in the portal. But wouldn't it be nice if it just worked ? ....and putting it all on the foundation of an emerging and strong standard like wsrp is a good thing, I beliefe ...... what do you think ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872971#3872971 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872971 ------------------------------------------------------- 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
