burtonator wrote:
>
> Neeme Praks wrote:
> >
> > I would like to add one more point: the current markup of user PSML
> > files is really confusing: we have three different ways of passing
> > information to the portlet:
> >
> > skins:
> > <skin>
> > <property name="selected-color" value="#BEBEFF"/>
> > <property name="background-color" value="FFFFFF"/>
> > </skin>
> >
> > parameters:
> > <parameter name="name" value="mmail"/>
> >
> > and metadata/metainfo:
> > <metainfo>
> > <title>M.Mail</title>
> > </metainfo>
>
> In this situation... skins could probably be easier done with properties
>
> jetspeed.skin.selected-color.
>
> Is there any reason we need a <skin> section other than this?
>
Yes, certainly. The <skin> is defined for a given *element* not a global property
Children a elements inherit these settings and may override them.
Using a property based system in this case require defining a CSS-like element
selector and process it server-side...
> > Could someone more knowledgeable explain the main differences between
> > these? And how are they used by portlets, controls anbd controllers?
> <snip>
>
> I see your point on the <metainfo><title> stuff. Although I think this
> is cleaner than:
>
> jetspeed.title
>
Actually I don't like the <metainfo><title> stuff, I think this should really be
handled by the Dublin Core schema, as in:
<portlets xmlns="http://java.apache.org/jetspeed/xsd/psml/1.0/"
xmlns:dc="http://purl.org/dc/elements/1.0/">
<dc:title>myTitle</dc:title>
<dc:description>myDescription</dc:description>
<dc:language>EN</dc:language>
<!-- ... -->
</portlets>
This would allow PSML to focus on its core task: describing portlet sets layout while
still keeping readability, schema validation, etc...
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
