On 10/18/06, Lennon Day-Reynolds <[EMAIL PROTECTED]> wrote:
Not that it hasn't been massively oversold, but XSLT actually isn't a
bad tool within its original problem domain: basic transformation of
predictable XML content. If your apps all produced valid XHTML, you
could probably just toss an extremely simple XSLT filter on top which
extracted the body content you were interested in and wrapped it in
your standard header and footer.
Presumably, though, the backend apps aren't going to exclusively
produce well-formed content. In that case, I'd probably try
post-processing using mod_ruby and Hpricot (or your choice of HTML
parsing tools). (_why has an example of writing a mod_ruby output
filter on redhanded[1] that might be useful as a starting point.)
Good point about XSLT, but also you point out the big weakness in that
plan. As some of the apps/tools to be used still don't exist or
haven't been selected, I can't honestly say that
I can control the output too easily.
I'm honestly leaning towards something like your second suggestion. To
answer some of the other response: yes, I know that can have it's own
problems, but it's not really that much different than going the XSLT
route.
_______________________________________________
PDXRuby mailing list
[email protected]
IRC: #pdx.rb on irc.freenode.net
http://lists.pdxruby.org/mailman/listinfo/pdxruby
