Re: nested templates?

> 
>> I actually did say, quite explicitly:
>> 
>> Is it possible to nest templates, i.e. to create templates for elements, and
>> nest them within on another, so I can effectively build a complete page,
> 
> that's not explicit at all. You can't nest templates, you posted an
> example that had nested templates and somehow we are supposed to guess
> what you want this construction to do!

uh, ok.

>> so I can effectively build a complete page,
>> with some xsl sprinkled in to take care of value-of selection.
> 
> look at the literal-result as stylesheet mechanism, just write an html
> page and put <xsl:value-of .../> at places you want to pull in data.
> 
> But you'll find as you learn more about XSL that using the templates
> mechanism about which you are very critical is in fact more general and
> more powerful than the "whole page as template" mechanism with which you
> might be familiar from asp etc.

Given the avalanche of posts I have caused, I think this is not the case.

I'm not approaching this problem from "used to"

I'm approaching it as "how would I have done, this how should this work" and
seeing what fits, and what doesn't.

A lot fits, otherwise I would not be using XSLT and not spending the time
necessary to master it, and Xpath.

But I don't just have "hello world" to deal with, if I'm going to use xslt,
I'm going to use the s*it out of it, pardon the expression - and that means
I need to deal with the same issues that "other" template system handle,
however ineffectively (and inelegantly)

_alex




--
alex black, ceo
enigma@xxxxxxxxxxxxxxxx

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list