Thanx Kurt,
Um.. Do u (or others) have any small samples showing this. I like the
concept, but I am not too clear on how to go about it... Sorry
Salud
John
John,
In general, I find with XSLT that you reach a certain point where it is
easier to create generalized XHTML templates with alternate namespace
tags
that can then be expanded from within XSLT. This way, the XSLT can be
used
to create generalized tables, layouts, navigational elements, forms,
etc.,
and the XHTML can be custom mapped to fit (this strategy works
especially
well with CSS in the mix too). This actually cuts down on the amount of
"custom" XSLT that you need to write, you can consolidate a lot of this
code
in libraries, and anything that you don't already have done you can
build as
needed for future code reuse.
-- Kurt
----- Original Message -----
From: "John Reid" <John(_dot_)Reid(_at_)optusnet(_dot_)com(_dot_)au>
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Thursday, September 18, 2003 12:06 AM
Subject: [xsl] My XSLT project is getting larger, maybe too large
My project started of with a text XML database for one unit of people
(about 80). It uses MSXML to generate HTML from a transformation. It
stands a good chance of growing to 20 units and maybe 100 units. Each
unit could have their own text XML database. But I can see where
somebody is going to want stats across them all. So I am asking for
advice. While I would guess that the app could be migrated to say
Tamino, the current database standard used is SQL Server. Could I
continue with mutiple XML text files, I kinda like them for they are
fast and easy to manipulate (ie if there is corruption then they can
simply be edited - with care!) any hints, guidelines suggestions would
help.
Salud
John Reid
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list