i just wanted to check before i start coding, if there are best practices or
design patterns concerning that issue.
matthias
----- Ursprüngliche Mail ----
Von: Michael Kay <mike(_at_)saxonica(_dot_)com>
An: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Gesendet: Dienstag, den 21. Juli 2009, 10:49:23 Uhr
Betreff: RE: [xsl] Design Question: XSLT Configurable
From your description it seems like a reasonable design approach. I'm not
sure why you are asking the question.
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
-----Original Message-----
From: Matthias Müller [mailto:pymote(_at_)yahoo(_dot_)de]
Sent: 21 July 2009 09:33
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] Design Question: XSLT Configurable
Hi there,
i work on a application that let the users configure it to
their needs using a certain file (a user-settings.xml) during
the years this file has changed, so there exist different
versions now. my idea is to transform all of them to the
newest version.
the configuration file is a very simple xml file (max 2
levels), the changes are also moderate (create node, delete
node, rename node and merge content of nodes).
the thing is, i want to keep the transformation expandable by
only configuring what have changed from version to version.
e.g. like that
-------------------------------------
<Versions>
<Version nr="0.3">
<Actions>
<RenameAction fromElement="elementA"
toElement="elementD"/>
</Actions>
</Version>
<Version nr="0.2">
<Actions>
<MergeContentAction toElement="elementA" separator=" ">
<MergeFromElement name="elementB"/>
<MergeFromElement name="elementC"/>
</MergeContentAction>
</Actions>
</Version>
<Version nr="0.1">
</Versions>
-------------------------------------
so, i only will have one transformation file instead of a
file for each version.
what about this approach? i think that this is supposed to be
a common issue, isn't it?
Thanks for your ideas,
Matthias
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--