Rapha�l Luta wrote:
>
> "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.
Sorry about the dated reply :(
I see your point. But this overriding behavior can be potentially bad.
IMO we should have a static set of values that are allowed to be
overrided. This way if someone defines something like "put" we don't
have namespace issues.
I don't have a problem with giving you this behavior but we should limit
it to a certain set of parameters.
We should also build a better "blend" mechanism. I don't like how we
are doing the blend in multiple places. This can lead to problems.
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
The house of the unbelievers shall be razed and they shall be
scorched to the earth. Their code will be open until the end of days.
--
--------------------------------------------------------------
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]
