Re: Perl, C, Interface Builder, and Aqua?
on 6/11/01 10:28 PM, Daniel Lord at [EMAIL PROTECTED] wrote: > But there seems to be no quick & dirty scripting solution to a GUI for > OSX Perl. That is (at least it is my impression) what we are trying to > come together and find here. Yep, that'd be ideal. I really don't want to learn C if I can avoid it, but I do want to create some apps that use the Aqua GUI. >>On Monday, June 11, 2001, at 02:19 PM, Anita Holmgren wrote: >> You certainly can do this. >> We do this sort of thing to build an Aqua GUI on our Tenon iTools. That's so cool! You've gotten some great reviews on that too! I haven't used it yet, but I did get "XTools" installed yesterday and had a few mooments to play with it. I still haven't gotten "GIMP" to run, but I hope to see it before my two weeks are up ;) I guess I'll get O'Reilly's "Cocoa" book and see if I can't make a simple front end to a "Hello World" perl script. Maybe it's not as difficult as I imagine ;) -- Bill Stephenson
Re: Perl, C, Interface Builder, and Aqua?
On Monday, June 11, 2001, at 02:19 PM, Anita Holmgren wrote: > You certainly can do this. You would need to create a project using > Project Builder and an interface using Interface Builder. You could > then make an Objective C object that 'interacts' with your Perl script > using NSTaks and a few NSPipes and sends the data to your interface. > > We do this sort of thing to build an Aqua GUI on our Tenon iTools. The approach certainly has merit for focused applications such as iTools where the GUI is established and the UI design known. It seems one could use that spot approach on a per application basis but unless one is a commercial developer creating a specific product, doing that for every instance where one needs a Perl GUI would be tedious and complex without higher-level aids. After all, RAD is one of the advantages scripting languages offer over larger compiled languages. We have have Carbon and Cocoa on the Mac using Project Builder accessible from C, java, and ObjC already if we want a full, long development cycle. But the reasons I (cannot speak for the rest of you here) use Perl for some tasks on the Mac are: 1) to leverage existing code, 2) simplicity and 3) speed to solution. One could theoretically (and with a lot of work) create make the graphics calls using a C-Perl framework like SWIG and avoid ObjC if one wanted a Quartz GUI or if X was okay, there is Perl GTK which needs work: doesn't compile out of the box unfortunately. At least my modest skills have been unable to get ti to work. But there seems to be no quick & dirty scripting solution to a GUI for OSX Perl. That is (at least it is my impression) what we are trying to come together and find here. There's Jython for Python which works very well with Swing/Java 2, but that doesn't run the multitude of Perl modules out there. We simply have to press on.
Re: Perl, C, Interface Builder, and Aqua?
On 2001-06-11, [EMAIL PROTECTED] (Anita Holmgren) wrote: > At 2:28 PM -0500 6/11/01, Bill Stephenson wrote: > >In theory, could you use "Interface Builder" to create a front end > >GUI that uses perl to interact with user input? > > You would need to create a project using Project Builder and an > interface using Interface Builder. You could then make an Objective C > object that 'interacts' with your Perl script using NSTaks and a few > NSPipes and sends the data to your interface. Hmm. That's viable, but seems like a somewhat limited approach. What I *really* want is to tie Interface Builder widgets directly to Perl code; there was an Objective-Perl package that claimed to do this for MacOS X Server, but it seems to be dead, with no web site updates in the last two years: http://www.tiptop.com/Objective/ -Simon
Re: Perl, C, Interface Builder, and Aqua?
At 2:28 PM -0500 6/11/01, Bill Stephenson wrote: >I wonder if anyone can shed some light on this for me. I've read a little >about calling perl from "C" apps and vice/versa. In theory, could you use >"Interface Builder" to create a front end GUI that uses perl to interact >with user input? > >Could this be an alternative to using "TK". It seems like a cool approach if >it could. You certainly can do this. You would need to create a project using Project Builder and an interface using Interface Builder. You could then make an Objective C object that 'interacts' with your Perl script using NSTaks and a few NSPipes and sends the data to your interface. We do this sort of thing to build an Aqua GUI on our Tenon iTools. -Anita -- Tenon Intersystems 805-963-6983 1123 Chapala Street [EMAIL PROTECTED] Santa Barbara, CA 93101 http://www.tenon.com
