At 21:23 +0100 2000.12.08, apeiros wrote: >Hi, > >>> I wanted to programm something with a GUI (graphical user interface), >>>AFAIK, >>> MacPerl hasn't got any routines for GUI's expected AppleScript and HTML >>> outputs, what I don't want. >> I cannot parse this sentence. What does it mean? > >I meant Perl hadn't got any routines for GUI MacPerl has lots of routines for GUI. There's info on the MacPerl site that you have, there's the MacPerl book, there's the online Help in the MacPerl app, there's the example files in ext:t: in the MacPerl folder. >> Regardless, MacPerl has >> lots of routines for creating GUIs, direct hooks into the Mac OS API. >> Mac::Windows, Mac::Events, Mac::Dialogs, etc. As I understand it, though, >> those routines are not as easy to use, nor as stable, as those of >> RealBasic. > >That, I didn't know. What do you mean with "not stable"? That it will cause >system errors or stuff like this? There are some bugs here and there. As mentioned, there are memory leaks. It's also prone to crash in some situations, though I can't say what those are offhand. >> You can also drive any OSAX or scriptable application with >> MacPerl. > >How? And which one was useful? Lots of ways. There's the built in MacPerl::DoAppleScript() function. There's the Mac::Glue module on CPAN and SourceForge, which I wrote, which lets you control scriptable Mac apps and OSAXs with a Perl syntax, but AppleScript vocabulary. There's raw Apple events. >> I'd ask the RealBasic people. > >Do you know a good forum or mailinglist? Nope. -- Chris Nandor pudge@pobox.com http://pudge.net/ Open Source Development Network pudge@osdn.com http://osdn.com/ # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org