[CPS-devel] redundant styles ?

Jean-Marc Orliaguet jmo at ita.chalmers.se
Thu Mar 16 11:54:38 CET 2006


Joachim Schmitz wrote:

> when going to the set style of a templet, I see 7 styles I can set. 
> For my treeview I tried to set the style so that it looked the way I 
> wanted, and found that all styles influence each other in an non 
> obvious way.
>
> while the first three styles : "Font color", "Font shape", "Area Color",
> make sense. The last four "Portal box shape", "Portal box color", "Box 
> corners" and "Tab style", seam redundant to me, and setting them to any
> non blank value leads to hard predictable results.
>
> Are these relicts of Portal Boxes ?
>

only  portlets that implement the expected HTML markup can use this 
information. Some of the portlets / display modes implement there own 
HTML markup, hence the styles inherited from CPSSkins have no effect.

see:
http://svn.nuxeo.org/trac/pub/file/CPSPortlets/trunk/doc/portlet-styling.txt

also there is some information about the distinction between custom and 
generic portlets in:
http://www.cps-project.org/sections/documentation/developers/guidelines_for_creation/downloadFile/file/portlet-creation-guidelines.sxw

the zope2 version of CPSSkins/CPSPortlets has no clear notion of widgets 
(widgets are described in HTML by portlet creators).

in the zope3 version which is being worked on, the issue of matching the 
HTML markup to some CSS styles is tackled differently since the style 
information applies to *widgets* and not to portlets directly. So we have:

portlet | widget | style

instead of:

portlet | style

/JM


More information about the cps-devel mailing list
More information about CPS: CPS project - CVS - API

Hosting: Nuxeo: Zope service provider


This list archive provided by Nuxeo, the leaders of open source ECM. Check out the Nuxeo 5 open source, standards-based ECM project.