On Thu, Feb 05, 2009 at 08:53:28AM -0500, Tod Harter wrote:
> In days gone past any number of people, myself included, did webapp work
> using AxKit. It was a great tool, but I cannot recall being exceedingly
> pleased with XPathScript. In fact I always found it to end up being a really
> awkward module to use in practice. There were various 'phasing' problems
> with it IIRC. Certain things turned out to be inordinately difficult to do
> or had to be done in non-obvious ways.
>
> Towards the end of my AxKit days things seemed to have settled down to a
> situation where basically you generated XML from a 'provider' and just hit
> it with XSLT and XPathScript seemed to kind of fall by the wayside. Of
> course other people maybe were more fond of it than I was.
Well, I know at least of a person who was fond enough of it to
adopt and maintain it for the last few years. :-)
I'll not argue that XPS is a wee bit of an acquired taste and
not everybody's cup of tea (I'm biased, not deluded). But since the
AxKit days there have been lots of improvements that -- or so I hope --
polished some of XPS's rough edges.
Not to say there's not still a lot of corners sharp enough to
cut unsuspecting fingers, mind you. One of the things that is still
hard to do is to manage large stylesheets. But I'm working on
that, and a decent system should appear with XPS2.
Which in turn means that, in order not to repeat mistakes
of the past, I'm quite interested to know what you considered to
be awkward when you were using XPS, and what where the phasing problems.
So, if you feel so inclined, I'd love to hear you expand on those points.
And the invitation holds for everybody. If you ever used XPS and shook
your fist the heavens, now is the time to rant about it. :-)
Joy,
`/anick
_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.