I agree with Chris. In every language you can create a mess. Two rules of advice for Kasper on programming: 1) Be a lazy coder. Think first how you can write as few lines of code as possible. Not only will you have effecient code, you'll have code that you can maintain. 2) Stop using copy & paste. If things are similar to each other, create a function. In XSL that's a template. If you copy&paste a line of code 100 times and it shows a bug afterwards, be sure that you will change it 95 times, leaving 5 bugs.
Bad coding habits are no reason to break down a product. Cocoon is a great XML publishing framework. It's even not about XSL at all. It uses XSL but it's not an XSL editor or whatever you want to call it. Use the tools for what they're intented. > >For a short synopsis at school I'm looking for points to areas where > > cocoon and stacking an endlessly number of XSL transformers on top of > > each other falls short. You know stuff like how difficult it is adding a > > new attribute to an XML element, and make sure it's copied along in all > > your 200 stylesheets, compared to how easy it is in languages like java. > > I think it is easier to edit a couple of stylesheets than coding Java. > Plus, the use of stylesheets helps with the separation of > style/content/logic. If you have a new bit of style to add, a designer > responsible for the look of the output could edit the stylesheet. > > I appreciate your reason for use of hyperbole but it is not fair - no-one > has an endless number of XSL transformers stacked up and no-one has 200 > stylesheets to edit. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
