Jasen, That is similiar to how we are handling the styling for a portal. I say similiar because we use a directory for the images and a directory for the .css. That could very easily be a chage for the better though, if we were to include all aspects of a style in a single folder. I think that we may have overlooked a few of the minor design details in that issue because we were more focused on creating common .css class references.
John On Tuesday 01 April 2003 06:14, [EMAIL PROTECTED] wrote: > I've found the skinning methodology in Jetspeed to be awkward, at best. > Take a look at how uPortal ( http://mis105.mis.udel.edu/ja-sig/uportal/ > <http://mis105.mis.udel.edu/ja-sig/uportal/> and > http://mis105.mis.udel.edu/ja-sig/uportal/developers/looknfeel.pdf > <http://mis105.mis.udel.edu/ja-sig/uportal/developers/looknfeel.pdf> ) does > its skinning. Each skin is a directory, each directory contains all the > .css and image files necessary for the theme, skins are swapped by changing > a single variable which then makes all the appropriate relative directory > references. Much cleaner than the embedded style declarations in Jetspeed, > IMHO. > > - Jasen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
