Thanks for all answers.
At 11:03 Uhr -0700 26.8.2001, Ed Silva wrote:
> I can say it has been hard to get it
>working (and it is only partially functional as is) due to object
>allocation issues, etc. I'm almost ready to rewrite the thing in C.
Thanks for the hint. I just thought Cocoa must be easier than this
old mac style carbon api since it's already OO, but so this might
already be a difficulty in itself...
At 9:36 Uhr -0500 26.8.2001, Jeff Lowrey wrote:
>There's also a rumor of an Apple internal Cocoa to Perl bridge.
One that they won't release? Would be silly if they don't.
Well considering all this, I think I'll probably give up the idea
writing cocoa interfaces and instead look into porting the essential
(for me anyway :-/) Mac::* Modules to carbon (I suspect that should
be quite trivial, just strip some Toolbox calls, am I wrong?).
One thing that I'm not really clear about is the event handling:
since I write a networked app, this includes both events from the
network as well as from the gui. Now usually one calls WaitNextEvent
(or what it's called anyway) and gets events for both (am I right?,
never wrote a networked MacOS C app). Now that perl uses POSIX
networking (and MacPerl emulates it through Matthias' GUSI) it has to
'select' socket filehandles for event capture. Is the only thing to
solve this to timeout (0.25 secs or so) on both WaitNextEvent and
select and call them alternately? Or call WaitNextEvent and if it's a
network event go call select?
(It will take a week or two until I find time to actually work on the topic.)
Christian.
--
Christian Jaeger
Technik ETHLife - die tägliche Webzeitung der ETH
G: 01/430 45 26
P: 01/273 65 46
