and

for conditions. > Your cart is empty >

> > > forEach() > ------------------- > > example: > > > or for iterators. > > > > >

${index}

${description}

${price}

> > > for(var=,begin=,end=,step=) > --------------------------------------------------- Is it necessary? Current jxtg does not have it (IIRC). > context= > -------------- > > Set the current evaluation context for expressions. > > example: > >

or t:context, or some such. ... and the rest is similar. I also feel that expressions like "if();context();let();for();etc;etc;etc" are too complicated for what is necessary in Cocoon Templates. Vadim > ... >

> > > let(=,...,=) > ------------------------------------ > > Define a number of variables for the current context. Observe that this > not is a set operation it just defines the content of the variable > $ in the current context, it doesn't intoduce any possibilities to > have side effects. > > example: > >

> > ${item} > > > > We also need an evalBody as in JXTG. And maybe we should have a > possibilty to give a name space to the macro name. > > > eval(,context=,=,...,=) > ----------------------------------------------------------------------- > > Evaluates the named macro in either the curent context or the > excplictliy chosen, with a number of forma parameters. The containing > element is replaced by the result of the evaluation. And the content of > the the containing element is available in the macro through "evalBody". > > example: > > > > We could maybe even have the synatax: > >
> > for user defined macros. > > > replace() > --------------- > > Replaces the containing element with the result of the expression, > useful for inserting DOM etc from the flow layer. > > example: > >
> > > content() > --------------- > > Like replace but replaces only the content. > > > attributes(=,...,=) > ------------------------------------------- > > Inserts an attribute. > > > Several directives > ------------------ > > So, how do we handle multiple directives for one element? We could > handle the TAL example above like: > >
do="let(x=/a/long/path/from/the/root;if(x);content(x/txt);attributes(class=x/class)"> > > Ex Text >
> > The idea is that when the leftmost directive is executed it has the > ability to access the result of executing the directive sequence right > of it in its current context. It will be the rightmost directive that > has direct access to the containing element with evaluated attributes > and body. > > The corresponding tag based template expression would be (in pseudo jx): > > > > > >
Ex Text
> > > > > > The jx:attribute and jx:content returns the patched variant of its > respectively body. Not particulary natural constructions in a tag based > template language, but hopefully it explains the direcive combination > construction.