[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: When to use conditional constructions?

Subject: Re: When to use conditional constructions?
From: John Lumley <john@xxxxxxxxxxxx>
Date: Sun, 30 Mar 2014 19:49:05 +0100
Re:  When to use conditional constructions?
On 30 Mar 2014, at 18:28, Michael Kay <mike@xxxxxxxxxxxx> wrote:

> I do have a strong preferance for multiple template rules over xsl:choose. I
think this is mainly because it makes it easier to evolve the code as it
develops over time. Though a strong downside is that it can be very hard for
the reader of the code to work out which templates are going to fire under
which circumstances.

I've found that one of the benefits of using xsl:choose is that it keeps all
the 'cases' together in one coherent collection. It also has a well-defined
'priority order'. If you use multiple template rules they can end up scattered
and difficult to view as a complete set and priority can be somewhat awkward.

For example one of my 'pagination' called templates contains an xsl:choose
with perhaps 15 cases (bpage-break?', 'content-fits?', 'can-be-broken?'....)
that would be much more tricky to prioritise as templates.

Of course use of a unique mode with templates can help, but it would still be
nice to collect them all together into preferably a single XML node - perhaps
a package?

John

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.