"Kevin A. Burton" wrote:
>
> Rapha�l Luta wrote:
> <snip>
> > -1
> >
> > For most parameters I can think of, the controllers just want the current value for
> > a given parameter, they don't want to know if it's a locally overridden property
> > or if it's inherited from the current set. Why would they need to care ?
> > Do you have an explicit need for querying local only parameters ?
>
> Why would we ever need to override a local property. I think the
> distinction is important. Can you give an example where this
> functionality is needed?
>
Well, in the PanedPortletControlelr I need 2 informations to layout
the portlets: column number and position for each of the portlets. If I want to
specify a default behavior for all portlets, I set in the portletSet (or one of
the panes, default values for these parameters, and only explicit values in the
portlets entries when I need non standard behavior.
This could also apply for XSL stylesheets used in CocoonPortlets, where a default
value can be set for a portletSet and then overridden by some specific ones.
You can argue that this behavior can be achieved by specifying the portletSet value
as default. True but the structure is already 3 levels deep (PortletSet,Pane,Portlet)
and may grow arbitrarily deep in future revisions. PortletSets are just a way to
group portlets and affect them a coherent behavior (and layout). These groups may
themselves be nested and I don't want to force the programmer to explore the
object hierarchy to find where a property has been defined.
--
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]
