At 11:24 Uhr -0500 4.10.2001, Bill Stephenson wrote: > > on 9/29/01 10:30 AM, Christian Jaeger at [EMAIL PROTECTED] wrote: >> >>> I've been thinking about porting some MacPerl Toolbox modules (see > >> thread `cocoa interfaces'). However in the meantime I've discovered >>> wxPerl (wxPerl.sourceforge.net), > >This sounds exactly like what I think I need. But I have no idea if your >work on PerlObjCBridge is what is needed to make wxPerl work on OS X.
The PerlObjCBridge should not be required for wxPerl to work. Both are different ways to create guis on MacOSX (another one would be to use Carbon and port the Mac Toolbox modules to MacOSX). I see the following differences (I still haven't got the time to install wxWindows): - wxPerl needs wxWindows to be installed. So you will probably either need a smart installer (and include wxWindows into the distribution of your app) or require the user to install wxWindows+wxPerl. The PerlObjCBridge will have the advantage to operate directly with the base system, so only the PerlObjCBridge itself will have to be installed. - a perl app written with wxPerl will not only run on MacOSX, MacOS8/9 (when it ever will be done), but also on MS Windows, Linux, ... - PerlObjCBridge might offer some advantages re fully exploitation of the aqua api (however as it seems it has ways to go for that) - wxPerl/MacOSX might be ready sooner (It's currently just a problem of lack of time for me to work on wxPerl/MacOSX. Still waiting for some sign from the two programmers I wanted to hire.) Christian.
