Speaking of "best practices", isn'r this a *bad* practice?
I have several imports, like this
<!-- Global Vars -->
<xsl:include href="xglobalvars.xsl" />
<!-- Page Body -->
<xsl:template match="/">
<XPage class="Tester" name="Tester">
<xsl:call-template name="StandardComponents"/>
<xsl:call-template name="StandardEvents"/>
</XPage>
</xsl:template>
<!-- All Templates -->
<xsl:include href="StandardComponents.xsl" />
<xsl:include href="StandardEvents.xsl" />
and then, in StandardComponents and StandardEvents i'm using variables defined
in xglobalvars.
That means that if i use Standard* on their one, or in another context, i will
have troubles for not having the vars...
But is the alternative to import the xglobalvars in all the Standard* xlsl's?
Isn't that a bad practice also?
What other alternatives are there?
Thanks.
Quoting xptm(_at_)sapo(_dot_)pt:
Are there any naming conventions in XSL/XSLT?
In Java we have thos conventions, like class names begin with a capital
letter,
methods and properties with lower letters, etc...
Is there any "best practices " for XSL, for naming vars, global vars,
functions,
etc.?
Thanks.
O SAPO já está livre de vírus com a Panda Software, fique você também!
Clique em: http://antivirus.sapo.pt
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--
O SAPO já está livre de vírus com a Panda Software, fique você também!
Clique em: http://antivirus.sapo.pt