Let me be clear that I fully understand how to have rich dynamic content in
PageKit -- it makes it quite easy. What I can't have is rich XML content,
to connect software that generates its content in XML with presentation
tools that expect its input in XML.
The real strength of PageKit is that it very nicely integrates a number of
very useful tools: HTML::Template, Data::FormValidator, etc. Allowing it
to be used with XML producers and consumers would make it attractive to
another class of developer. Right now you can do all these things with
AxKit, but the learning curve for AxKit is a bit steep, compared to
On Mon, Mar 17, 2003 at 04:32:36PM -0500, Shimon Rura wrote:
> It looks like what you want is a way to represent---from the Model---data
> that can be as richly structured as is the Content's XML representation. It
> seems to me that it would be fairly easy to get a tree-type structure passed
> in from the Model, and from that you could do various LOOP queries and such
> from your template. Of course, you couldn't do XPath queries. Although I am
> not well versed on how XSLT templates have access to model data; perhaps
> there is a way that for XSLT templates the model input can be automatically
> treated as an XML document.
> On Mon, Mar 17, 2003 at 05:56:32PM +0100, Boris Zentner wrote:
> > Hi Paul,
> > Am Montag, 17. März 2003 17:04 schrieb Paul Weiss:
> > > I don't know if this has been addressed in this forum, but can PageKit
> > > handle dynamic content? So far, everything I've read in the docs implies
> > PageKit handles Ddynamic content very well, but you mean the *.xml files in
> > the Content dir.
> > > that the content file must be fixed, i.e. a static xml file in the Content
> > > directory.
> > And yes, this file must be static, or at least written back to disk. Otherwise
> > PageKit did not read it again. And note that the file is only parsed once and
> > the output is then cached. A change in the file is only noticed if the file
> > is changed and reload is on in Config.xml. Or at server startup.
> > >
> > > However, it would be useful at times, to have the content generated
> > > dynamically, by a Perl script that produces either an XML file (or even
> > > better, a DOM tree, so that we don't incur the expense of building an XML
> > > file only to parse it).
> > But we do not parse it, the data in the content files are parsed inserted into
> > the page and then CACHED and never parsed again. So on every request to the
> > page the cached data is served and enriched with the real dynamic content.
> > > This would let the developer use the content
> > > itself to pass data to the template rather than the one-dimensional $model-
> > >
> > > >output, and it would allow the use of existing XSLT templates that know
> > you can use <MODEL_LOOP> to create something like namespaces in the output.
> > >
> > > nothing of PageKit. It would also allow us to use tools that generate XML
> > > directly from the database.
> > Maybe we can generate another pass that allows us to feed a dom tree or xml to
> > a stylesheet before the final data is filled in, with the model tags.
> > Let us build a whishlist for that future eg. a list with desired functions.
> > Then some version of pagekit has this option.
> > >
> > > This seems a pretty powerful capability. Can PageKit do this?
> > >
> > at this point it can not, for speed reason mostly.
> > > -Paul Weiss
> > >
> > --
> > Boris
> > -------------------------------------------------------
> > This SF.net email is sponsored by:Crypto Challenge is now open!
> > Get cracking and register here for some mind boggling fun and
> > the chance of winning an Apple iPod:
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> > _______________________________________________
> > Pagekit-users mailing list
> > Pagekit-users@...
> > https://lists.sourceforge.net/lists/listinfo/pagekit-users