Hi Sajeesh,
IMHO, writing well designed code comes with experiance. I prefer
writing code with nice indentation and with well-established coding
practices, so that it is understood and maintained easily by another
person.
As far your second question, if it is required to document the XSLT
program design, I would write the design in a plain vanilla word file.
I believe there is no standard for XSLT program design.
Regards,
Mukul
On 8/18/05, Sajeesh N Kakkat <ksajeesh(_at_)in(_dot_)ibm(_dot_)com> wrote:
This should be for single transformation using a XML file with XSLT 1 or 2
to produce a PDF file.
Design Patterns :
Are there specific design patterns or ideas on how to structure XSLT code
such as to make them more readable and maintainable. This can be a problem
since both the formatting code and logic code can get intertwined in the
file and can get messy if somebody is continuously making changes on top of
it.
Design documents :
Are there any standard templates for writiing External design document and
internal design document for XSLT. The idea is to write whatever is being
read from the XML such as its understandable to a layman.
Any suggestions or tips are welcome.
Sajeesh
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--