Chris,
Chris Kimpton wrote:
>
> Hi,
>
> --- Paul Spencer <[EMAIL PROTECTED]> wrote:
> > I would prefer to see the CSS associated to a skin. That way a
> > portal
> > with 3 columns could have a different look, via CSS, in each
> > column. As
> > an example the first column is a navigation with the default font
> > bolded. The second column contains RSS feeds with no special
> > formatting. The third columns contains portlets in orange boxes.
> >
>
> So that I am clear on what you are saying, rather than specifying the
> class directly in the vm, as in the patch, we should get the class
> from the skin and then the skin would have the default class, but
> could be overridden via psml - or perhaps in other ways too...
>
> So the class lines would be for example:
>
> class="$!{skin.TitleStyleClass}"
>
> If so, thats fine, I'll submit a revised patch.
I believe you have the idea, although I do not believe the
implementation is a simple as patching the .vm.
Some, by no means all, items that should be addressed:
o Support for a CSS class must be added to the skin.
o The vm must only set the CSS when a CSS exists. This will allow
portlet
to inherit the CSS of their parent.
o Which elements, i.e. Portlet Box, Portlet Titles, Portlet Content...
will have a configurable CSS.
>
> Regards,
> Chris
>
Paul Spencer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
