Hi,
My friend and workmate Chris keeps telling me about AxKit, and I've
had quite a long look at the website but there's a couple of things
which I cannot figure out.
Currently the way I handle separation of content from presentation is
using templates. There is no XML here, I just fetch the objects I need
to fetch and stick them into my in-house templating system which is
able to process them, invoke their methods, etc.
From what I read from the website, an obvious way to be quickly using
AxKit would be to pipe the output of my scripts using
Apache::RegistryFilter and the Filter provider (the application output
being valid XHTML...). But then Axkit would be no more than merely an
XSLT processor for XHTML content...
I have the feeling that it's a lot more than that though. So my
question is: which kind of jazzy / fancy stuff could AxKit provide to
an application which already uses a templating system and outputs
valid XHTML? Is AxKit capable of processing objects rather than purely
XML?
I'm confused. Help! :-)
Cheers,
--
IT'S TIME FOR A DIFFERENT KIND OF WEB
================================================================
Jean-Michel Hiver - Software Director
[EMAIL PROTECTED]
+44 (0)114 255 8097
================================================================
VISIT HTTP://WWW.MKDOC.COM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
