cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [Proposal]: Advanced Value Substitution
Date Tue, 08 Oct 2002 10:18:53 GMT
Please don't answer on this one...it's only a joke, really :)

Carsten

> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> Sent: Tuesday, October 08, 2002 11:53 AM
> To: cocoon-dev@xml.apache.org
> Subject: RE: [Proposal]: Advanced Value Substitution
> 
> 
> Ok, what do you guys think about this?
> 
> A configurable variable substitution component! I can configure
> in the cocoon.xconf if I want to use the old substitution algorithm
> or my suggestion (or a custom implementation).
> 
> Carsten
> 
> > -----Original Message-----
> > From: www-data [mailto:www-data@dff.st]On Behalf Of tcurdt@dff.st
> > Sent: Tuesday, October 08, 2002 11:39 AM
> > To: cocoon-dev@xml.apache.org
> > Subject: Re: [Proposal]: Advanced Value Substitution
> > 
> > 
> > > >here is a simple proposal for an easier value substitution algorithm
> > > >in the sitemap.
> > > >
> > > >Currently, if you nest actions and matchers you have to aware of
> > > >the paths to get your information:
> > > ><match pattern="**">
> > > >  <act type="anything">
> > > >      <read src="{directory}/{../1}"/>
> > > >  </act>
> > > ></match>
> > > >
> > > >This can get very complicated. When I first got contact with value
> > > >substitution more than two years ago, I thought I could write:
> > > ><read src="{directory}/{1}"/>
> > > >
> > > >The two components use different keys, so there is no conflict and
> > > >the values can be resolved.
> > > >This is in accordence to usual programming languages where a
> > > >variable is not only searched in the current scope but also
> > > >in the parent scope:
> > 
> > ...
> > 
> > > >What do you think?
> > > >
> > > 
> > > Sorry Carsten, this is a day where we don't agree :-/
> > 
> > Although I am also sometimes confused about substitution values like
> > {../../../../../../../1} just to get the result of the first match..
> > But I fear you might find yourself searching for clashes... don't know
> > if this will make things really easier...
> > 
> > BTW: Do we support absolute paths already? like {/1} being on the 
> > first level?
> > --
> > Torsten
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message