Re: [MacPerl] What list to use?

[Arved Sandstrom <Arved_37@chebucto.ns.ca>]

On Tue, 23 Feb 1999, Rich Morin wrote:

> I am quite interested in XML, but I'm a bit lost as to the support
> it now has and has coming.  If there is a recent precis, I'd like
> a pointer.  Otherwise, if Arved would be interested in writing a
> precis, we could put it online and/or publish it in print (e.g.,
> Perl journal if really Perly; MacTech or NetProfessional otherwise).

[ Also taking into account answers from Vicki and Chris ]

OK, I'll start thread(s) along this line on the main list, and as Vicki
said, maybe it'll migrate to macperl-anyperl. Certainly chunks of the
discussion also have a rightful place on macperl-modules, but that wasn't
the part I was getting at.

The kind of stuff Rich brought up is _exactly_ what I'd like to see
discussion about. The heavy duty support for XML is gravitating towards
Perl and Java, although specific tools (apps and libraries) are of course
also available in C/C++, and Python is doing its thing also. :-)

Thee is a lot of stuff that can be done with MacPerl, somewhat more that
can be done with Perl if one then assumes any OS is up for grabs, quite a
bit more if one allows for other tools to be in the discussion, and so
forth. And, of course, at this stage of the game, what is just as
important, there is a fair bit that can't yet be done or can be done only
with difficulty.

There are of course specific lists for XML development. I'm on three of
them myself - the perl-XML list, the xml-dev list, and the Edinburgh WG
XML list. The key phrase being "XML _development_". If you want to talk
about memory leaks in a Perl SAX implementation, or argue about how a
particular element is handled in the DOM spec, these lists are where you
go. But I wanted to talk about the more general stuff, like what Rich
mentioned.

Case in point - I'm writing a MacPerl app (series of scripts and droplets)
that simplifies life for me big time, as I have a time-constrained PPP
connection. I am on a whole bunch of mailing lists, most of which generate
digests. I don't have time to read more than a fraction.

So what I'm doing is, one script processes a daily batch of digests,
converting line-endings and putting in XML markup. A utility script 
generates indexes. Another script uses XML::Parser and XML::XQL to perform
reasonably fast queries on my mailing-list DB, in conjunction with the
indices.

And since the output can be XML (although it can also be text), it can
also be converted to something styled, although my current project in that
regard (and this is just proof of concept) is pod2xml, with a person then
saying, well, I'd like HTML (and XML->HTML is very doable), or maybe I'd
like PDF (also doable, but not simple), and so on.

As far as getting something in print, well, we're the MacPerl people. If
anyone is doing something significant on MacOS with XML, they can't ignore
MacPerl. No ifs and buts. So after we've had good discussion over the
course of a few months, maybe we'll have some decent material to synopsize
and print in one of the mags Rich mentions.

Thanks for the responses, Arved



===== Want to unsubscribe from this list?
===== Send mail with body "unsubscribe" to macperl-request@macperl.org