Matt Sergeant wrote:
It's one way to do it. I personally haven't used the provider method (seeGiven that a Provider has access to everything that is available for the Language modules *and* gets to control both the content and the styles that are applied, how does it lack flexibilty, exactly?
the Wiki for how I did it), because I feel it lacks flexibility.
It wasOh? My experience is quite different...
originally meant as a publishing layer, and I'm not entirely sure it's
powerful enough for building web apps
Consider the following:
Application Framework (builds XML document) -> Custom Provider -> AxKit
Again, as I mentioned in my other reply to this thread, deciding whether a custom Provider is appropriate all about *defining* what the XML source is. For many Web applications, that source is best seen as the application code that creates the dynamic content.
In practice, this allows Perl developers to do what they want, how they want to do it as long as the proper XML content is returned from their application, while still taking advantage of the seperation of concerns and other more obviously practical benefits that AxKit offers.
Try it sometime, you'll *really* like it :-)
-kip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
