I've been helping out with an initiative to port wxPython
(http://www.wxpython.org) to the Mac OS X platform. For those who aren't
familiar with it, wxPython is a wrapper to make wxWindows, a
cross-platform (Win/Mac/Linux) GUI API, accessible in Python. wxWindows
itself has already been ported to Mac and is Carbonized, so it is very
close to being a working product. However, a couple of interesting
issues have arisen regarding the Python interpreter on Mac. I hope that
Apple is listening to this, because these are some tough ones! =)
1) Multiple Instances: The Python Interpreter has an app bundle version
available ("Python.app"), but this has the side effect of not allowing
multiple instances of the Interpreter to run. I know that on Macs, it is
standard behavior for only one instance of an application to run, but
since Python is a script interpreter, we'd like it to behave more like
the Mac's Java JAR launcher utility, considering each script as a
separate application. Is there anyway to get Python.app to launch a
separate instance for each script the user runs?
2) Sharing Menus: Another interesting problem is that wxPython does not
get its "own" menubar, that is, all wxPython windows and menus are
considered part of Python.app's resources. As a result, trying to create
a new menubar fails, and the only alternative we've found for OS X is to
have wxPython overwrite Python.app's menubar for its script. (At the
moment, Python.app doesn't use its menubar so this isn't a problem, but
we'd like to avoid having its contents overwritten if possible.) Is
there any way for wxPython to create its own menubar, so it won't use
Python.app's?
If anyone is so inclined, steps for building wxPython on Mac are
available at:
Kevin
_______________________________________________
unix-porting mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/unix-porting
Do not post admin requests to the list. They will be ignored.
