on 3/11/02 3:55 PM, [EMAIL PROTECTED] purportedly said:

> WEB ACCESS
> - is there any way to have a script in any form from HTML call AppleScript??

Not exactly, but I think you can create mac-based CGI's which can be used
with the personal web sharing on Mac. The archives should have loads of info
on this, and I think the MacPerl book also addresses this.

Alternatively, the CGI module is Mac-friendly and has a feature where you
can manually enter form data to a script and the script will treat it as if
it was posted through a form.

> XML Libraries
> - what libraries are working on the Macintosh OS Classic??

There is a ported version of XML::Parser (with ported expat lib) for both
versions of MacPerl (5.2.0 and 5.6.1).

> - is there an XSLT engine on the Mac in Perl?

Not that I have heard of, at least not one specifically ported to mac. Of
course, that doesn't mean there isn't one. Any module which is pure Perl and
uses XML::Parser should work, although installation may be tricky in some
cases.

> DBI
> - is this even feasible on the Mac OS Classic??

Yes and no. DBI is ported, but if you want to use a database system, I don't
know of any DBD's that are ported to Mac (even though some could be). There
is a proxy module that allows you to use "proxy" to a host that has the
proper DBD's, which I think is included in the DBI bundle.

> Perl/Tk
> - Does this work on the Macintosh?

Not sure. There is a TCL/Tk port, but I have never used it.

> - Is there support for some sort of Aqua/Tk?

if you are running OS X, then you don't have to be concerned about any of
the mac compatibility issues. That is your bet bet if it is available and
you are developing for *nix/web.

> Other Modules
> - Do NET::SMTP, Mail::Internet, LDAP, IMAP::Admin, Mail::IMAPClient,
> Net::LDAP, Net::LDAP::LDIF
> work on the Mac?!?

I know some of these do (like Net::SMTP). The general rule is that if the
module is pure Perl (i.e. no xs code to compile) and doesn't use IPC,
fork(), or exec-related calls (exec(), system(), backticks, etc.), it will
work under MacPerl. There are a few other things that don't work as a module
might expect like command line options, $$ (current process id number), and
other *nix specific stuff, but there are workarounds for some of these.

Keary Suska
Esoteritech, Inc.
"Leveraging Open Source for a better Internet"

Reply via email to