[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Hi Eric,
At 07:46 AM 6/23/2003, you wrote:
Well if you want frames in your output, the requirement is implicit that you'll need several output files, contents.htm etc. (Whether you break up your main copy into several files then becomes an HTML design issue.) So this does boil down to mapping the output of your transform to several output files.
Most XSL processors now contain extension functions to create several output files from a single transformation; even if you can't do that there are workarounds to the same effect. It generally can't be done client-side (in case that's what you mean by "on the fly"), but it can be done dynamically by a server-side engine in, say, Apache Cocoon or a similar environment, if necessary.
So the answer, I think, is that the latter is perfectly standard procedure.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] Documentation output
Subject: Re: [xsl] Documentation output From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Mon, 23 Jun 2003 13:51:21 -0400 |
Hi Eric,
At 07:46 AM 6/23/2003, you wrote:
<documentation> <topic> <title>First Topic</title> <content>content here</content> </topic> <topic> <title>Second Topic</title> <content>content here</content> </topic> <topic>... </documentation>
I'm wanting to display this content in IE6.0 in relatively standard help format--with the left frame containing the contents (i.e. a list of all of the titles as hyperlinks, a TopRight frame with the Title of the currently selected topic, and a BottomRight frame with the content of the currently selected topic.
I'm wondering if there is a good way to do this on the fly, or if I should transform this one file into multiple XML or html files (e.g. contents.htm, First Topic.htm, First Topic header.htm, etc.)...at which point getting the right material into the right windows is a standard html issue.
Well if you want frames in your output, the requirement is implicit that you'll need several output files, contents.htm etc. (Whether you break up your main copy into several files then becomes an HTML design issue.) So this does boil down to mapping the output of your transform to several output files.
Most XSL processors now contain extension functions to create several output files from a single transformation; even if you can't do that there are workarounds to the same effect. It generally can't be done client-side (in case that's what you mean by "on the fly"), but it can be done dynamically by a server-side engine in, say, Apache Cocoon or a similar environment, if necessary.
So the answer, I think, is that the latter is perfectly standard procedure.
Cheers, Wendell
Thanks in advance
Eric : )
p.s. It's been a year and a half since I last had a project that let me use XSLT with any depth, and even then, I was somewhat stumbling, so answers at the XSLT for Imbeciles level would be great.
________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Documentation output, Eric K Taylor | Thread | [xsl] identity transform exclude pi, I-Lin Kuo |
[xsl] xslt component, Ai, Larry | Date | RE: [xsl] evaluate, Michael Kay |
Month |