Re: XML in, HTML out design patterns

Using XSLT seems to be the XML-ish way to convert XML to HTML. I don't think that has changed in 4 years. Other options probably include using XML::Twig or XML::Simple to read in the XML, and then use some templating system (such as Text Template or HTML::Template or ...) to produce HTML output. It kind of depends on what framework, if any, you have, or, if you don't have a framework yet, what framework you are going to use.

For example, if you are doing all the rest of your website in HTML::Template, I would probably suggest that you use the perl to read in the XML file, and place it in a hash with which HTML::Template can use to populate its template. However, if all your pages are coming from an XML source, learning XSLT may be a good thing as it is a differently cross-problem tool that you can put in your mental toolbox.

As for your fun in installing XML::Parser on OS X, I'd suggest Meditations or Tutorials.

Comment on Re: XML in, HTML out design patterns

Replies are listed 'Best First'.
Re^2: XML in, HTML out design patterns by nmerriweather (Friar) on Feb 05, 2006 at 05:17 UTC
you could use Petal - its the perl implementation of TAL. template docs are/must be valid xml and way easier to use than xslt	[reply]
Re^2: XML in, HTML out design patterns by alienhuman (Pilgrim) on Feb 05, 2006 at 21:42 UTC
Thank you both for your replies and suggestions to what I realize is a pretty open-ended question. I decided to try XSLT first, but I'm having difficulty installing XML::LibXSLT properly (it keeps failing tests during 'make test'). I'm just about at my wits end, so I may end up looking at Petal sooner than I thought. ---------- `Using perl 5.8.1-RC3 unless otherwise noted. Apache/1.3.33 (Darwin) unless otherwise noted. Mac OS X 10.3.9 unless otherwise noted.` [download]	[reply] [d/l]