Hi,
I don't know of any standards, but my suggestion is to organize them in
seperate files and directories. This resembles the OO approach. One class is
normalley defined in one Java-file and packages are grouped in directories.
To improve the maintainability you can also document you're code like Java,
see www.kielen.com
Regards,
Agnes
----- Original Message -----
From: "Brian Chrisman" <incubus(_at_)shell(_dot_)izap(_dot_)com>
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Saturday, September 04, 2004 10:15 PM
Subject: [xsl] organization for large numbers of templates
I'm wondering if the issue of organizing relatively large numbers of
templates. Currently I have a reasonably maintainable XSLt code base,
but as I add templates, I tend to lump them into libraries by
functionality.
Are there any standards, specs, or ideas on formalizing groupings of
templates
much like Object Oriented Programming has grouped functions/methods into
classes
etc?
I know I can kind of do this on my own, and have been doing so.. I'm just
wondering if there's a directive or recommendation out there for such.
thanks,
Brian Chrisman
--+------------------------------------------------------------------
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>
--+--