Subject: Re: [xsl] Help moving away from named templates From: Abel Braaksma <abel.online@xxxxxxxxx> Date: Wed, 02 May 2007 18:11:58 +0200 |
On 5/2/07, David Carlisle <davidc@xxxxxxxxx> wrote:
In particular in what way do you avoid this conflict using named templates, you still need to decide on which nodes to call the named template which should be an exactly equivalent problem, shouldn't it?
A few ways which seem clunky/limited:
1) Generally, I just have the script call emergencyContacts.xsl, which contains one template--the emergency contacts template. But doesn't this circumvent the magical property of XSL to pick its own darn templates according to the data? Also, there's something seemingly naive to me about having a bunch of xsl files with one template.
2) If I need to display BOTH the consumer's info and their emergency contacts on the same page, I include (INCLUDE HELL) the emergencyContact XSL and then use <xsl:call-template name="eContacts" />
Cheers, -- Abel Braaksma
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Help moving away from nam, David Carlisle | Thread | Re: [xsl] Help moving away from nam, David Carlisle |
Re: [xsl] Help moving away from nam, David Carlisle | Date | [xsl] How to show context of term i, Antony Quinn |
Month |