Jeff Turner wrote:
>
> On Tue, Oct 08, 2002 at 01:17:28PM +0400, Piroumian Konstantin wrote:
> ...
> > > So the user would say {default:skin}, and get the 'skin'
> > > request parameter, or if not present, 'defaultSkin'.
> > >
> > > IMO this is backwards. The user should use {request:skin},
> > > not {defaults:skin}.
> > >
> > > What do people think? Chris?
> >
> > I imagine this a little different, e.g.:
> >
> > <component-instance
> > class="org.apache.cocoon.components.modules.input.SkinModule"
> > logger="core.modules.input" name="skin">
> > <input-module name="request-param"/>
> > <input-module name="skin-defaults"/>
> > </component-instance>
>
> Oo.. that's a good idea. Say we've got all these modules floating about
> loose, and then we have a 'glue' module that can stick together a bunch
> of them.
>
> <component-instance class="...GlueModule" name="forwards">
> <input-module name="A"/>
> <input-module name="B"/>
> <input-module name="C"/>
> </component-instance>
>
> <component-instance class="...GlueModule" name="backwards">
> <input-module name="C"/>
> <input-module name="B"/>
> <input-module name="A"/>
> </component-instance>
>
> > The user uses {skin:name} and the SkinModule checks request
> parameters first
> > and then skin-defaults input module to obtain the value of
> 'name' attribute.
>
> Nice :)
>
Just a silly question: are you joking or do you consider this seriously?
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
