On 3 May '08, at 4:35 PM, Bruce Sherwood wrote:
Visual, which is written in multithreaded C++, can be imported dynamically at any time in a Python program. Visual then has to start up an event loop to make a window and process events.
Oh boy, this is a flashback. You've got the exact same issues we had when we brought up Java on OS X back in 2000. The process starts out GUI-less (just an invocation of /usr/bin/python, in your case) and has to acquire a windowserver connection, event loop, menus, all that stuff.
This is pretty tricky stuff, or it was back then, and we had the advantage of being able to use or create private APIs. But more of that stuff might be public now. (Wasn't there some discussion on this list recently of upgrading a command-line process to a GUI?)
IIRC, you don't have to start the event loop on the process's main thread, but whatever thread you create the WindowServer connection on becomes the de facto GUI thread, on which the main event loop will run.
I don't see any problem with loading nibs. You just have to find them — presumably you'd put them next to wherever you put your code.
—Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
