jeni - thanks for the direction.
the "stand-alone component" could be xml, htm/html, shtml file.
currently, the way i "include" a "stand-alone component" is with hardcoding.
for example:
<xsl:text disable-output-escaping="yes"><!--#include virtual=
"/public/includes/about_side_nav.htm" --></xsl:text>
OR
<xsl:value-of select="/folder name/component name" />
...
1. is there a cool way of combining the output from separate xsl files into
one browser window?
2. can you recommend an approach to a dynamic solution for "includes"?
thanks again,
Tiffany
-----Original Message-----
From: Jeni Tennison [mailto:jeni(_at_)jenitennison(_dot_)com]
Sent: Tuesday, November 23, 2004 1:50 PM
To: Tiffany Blake
Cc: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] includes
Hi Tiffany,
what is the best way to "include" stand-alone components on a page?
<xsl:import>
OR
<xsl:include href="">
Both of these elements are used to construct XSLT applications from
multiple stylesheet files.
If you want to include, say, a fixed header in the HTML page that your
XSLT is generating, I'd usually do it by putting the header in a
separate file and using <xsl:copy-of> and the document() function to
insert the content of that file into the result of the transformation:
<xsl:copy-of select="document('header.xml')" />
Note that the file must be a well-formed XML document for this to
work.
If that doesn't suit your requirement, perhaps you can give an example
of what you mean by "including stand-along components on a page".
Cheers,
Jeni
---
Jeni Tennison
http://www.jenitennison.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>
--~--