shannon 2002/06/02 18:20:14
Modified: src/documentation/xdocs/faq faq-xslt.xml
Log:
Added Ken's helpful reply on
cocoon-users on deciding
appropriate use of XSLT
in C2.
Revision Changes Path
1.2 +21 -1 xml-cocoon2/src/documentation/xdocs/faq/faq-xslt.xml
Index: faq-xslt.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/faq/faq-xslt.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq-xslt.xml 13 May 2002 17:55:25 -0000 1.1
+++ faq-xslt.xml 3 Jun 2002 01:20:14 -0000 1.2
@@ -49,6 +49,26 @@
</answer>
</faq>
-
+<faq>
+ <question>
+ Is (your description here) kind of functionality appropriate for a stylesheet?
+ </question>
+ <answer>
+ <p>When this kind of question arises, ask yourself:</p>
+ <ul>
+ <li>Am I using my stylesheet to address style concerns, or am I programming
with it?</li>
+ <li>Could I solve this problem once and for all during Generation?</li>
+ <li>Isn't my problem better solved with a Transformer, since it requires
coding?</li>
+ </ul>
+ <p>
+There is not one, nor only one, answer. In Cocoon, you can accomplish the same
thing in a number of different ways. Nonetheless, if your transformation depends on
something specific happening during generation, it will be more difficult to reuse
your code.
+</p>
+ <p>
+Here's a hint. Do all that you possibly can in a Generator. Add only what is
absolutely
+necessary with Transformers. Use stylesheets to change format or style,
+not to code. This approach will make your system more manageable and reusable
because it removes dependencies between components.
+ </p>
+ </answer>
+</faq>
</faqs>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
