RE: [cgiapp] CGI::Application::XML

["Jesse Erlbaum" <suppressed>]

Hi Jason --


> Of course, you could override the cgiapp_postrun(), in 
> CGI-App-XML; and
> then add the serialize() function.  But, then the user of the module
> can't use the cgiapp_postrun() hook without destroying the XML
> serialization.

I don't think this is a real problem.  That's what the hook is for!  If
you're concerned, and want the user to still be able to use a hook like
postrun(), just add one!  In your cgiapp_postrun(), add a call to
"cgiappxml_postrun()", and document it in the POD.


> HTML::Template is nice but XSLT is nicer :).  XSLT strength comes from
> it's abliity to tranform structured XML data into another form of
> structered XML data.  Not simply replacing text with text.

I don't agree with you there, but that doesn't mean you shouldn't
release your module!

XSLT is fine if you have to transform XML into XML.  HTML, however, is
all about creative design.  Designers don't know XPATH, and never will.
Their tools are HTML and CSS.  The purpose of HTML::Template is to give
the designer power to change design WITHOUT a programmer.

If your templating interface is XPATH, then your designer needs to work
with an XPATH programmer.  If you're going to have your designer work
with a programmer, then you're right back to the awful state of things
in the world before templating systems were designed.


IMHO,

-Jesse-


--

  Jesse Erlbaum
  The Erlbaum Group
  suppressed
  Phone: 212-684-6161
  Fax: 212-684-6226




---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed