Hi! The portlet creation guidelines is available online, the latest version is in cvs too.
http://www.medic.chalmers.se/~jmo/CPS/portlet-creation-guidelines.html I've had some hard times explaining to Olivier why it is important to not fiddle around too much with the HTML markup of portlet, and the reason for it is explained in detailed in the document. Basically, the reason is that CPSSkins makes a triple separation between: - portlet content (HTML markup) - box layout / presentation - box style Hence making assumptions about how portlets will be displayed destroys the content / layout separation. This is for *generic* portlets only, not for all portlets. So there is still the possibility to create custom layout, custom styles, etc. This is meant to overcome two major limitations of the original CPSBoxes implementation: - when users are adding a box, they also have to think about the layout / position on the page. In the end adding new boxes is a bit like putting together the pieces of a puzzle. With the HTML/layout separation portlets can be moved from one slot to another while preserving the theme's design (see: http://www.medic.chalmers.se/~jmo/CPS/cpsdefault-cpsskins.html). - software updates change the appearance of existing sites because there is no explicit contract with the user. best /JM _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
