[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: stylesheet organisation
My 2cts
I break down my stylesheets in multiple smaller parts by definition - by differentiating include and import smartly, I have good hooks for customization - it helps me when I am unit testing parts of the code. I develop a test harnas first, for developing and testing tricky functions, most of the time, and build the function in separate files for include. So I only migrate tested code in production branches, and I am not bothered by existing code - all my code is in subversion repositories at least somewhere. Smaller files help collaboration, allowing me to work on one part whilst someone else is working on another part I definitely don't agree that include/import is only useful for reuse of code in different projects Since I am often not alone when working on a larger project, maintainability is an important requirement And having multiple smaller files helps collaboration I try to have my includes of common function libraries top level only (but having multiple includes of the same library usually doesn't hurt since there are enough imports in between) I do have stubs that do nothing but including other stylesheets And Oxygen's features are important for maintaining all this cheers Geert At 13:11 2/09/2011, you wrote: Hi all,
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|