Re: what to use instead of Axkit?

Well, I don't know...

Over the years I've just ginned up a somewhat ad-hoc framework using XSLT
and callbacks mostly. It works pretty well for me and the code isn't
astronomically complex. If you like XSLT the approach works reasonably well.
There are any number of more complex perl webapp frameworks out there that
support a wide variety of templating, like HTML::Mason. Most of them seem to
be primarily built around Text::Template and its friends, but I am pretty
sure you can set them up to let you generate stuff with XSLT, Sax, or no
doubt XPS too!

On Sun, Feb 8, 2009 at 2:55 PM, Harry Wozniak <[email protected]> wrote:

> Hi List,
> On another thread, some members wrote of Axkit as a tool who's usefulness
> has subsided.
> (see  Re: spot/remove repeated elements in XML documet )
>
> I am getting ready to do some work that I thought I would use Axkit2 for.
>  What are the other ways of doing things that people prefer to Axkit2, these
> days?  I am looking for a way to handle inserting my content into other
> peoples web site templates, product of which to be served by me.
>
> Thanks,
> Harry
>
> _______________________________________________
> Perl-XML mailing list
> [email protected]
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
>


-- 
The Wise adapts himself to the world. The Fool adapts the world to himself.
Therefore, all progress depends on the Fool.

_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs