Am Dienstag 29 Juni 2010, 10:45:43 schrieb Karsten Hilbert:
>
> > > iii) Xlib: extension "RANDR" missing on display
> > > "/tmp/launch-nf7uqn/org.x:0". ... anything to do?
> >
> > It just tells you that from your X11/video driver/BSD-subsystem RANDR is
> > missing which will prevent you from stuff like resizing or ratating your
> > screen from within X11 (you can still do that from MacOS if you want).
> > This is harmless. However your GNUmed runs on GTK on X11. There is also
> > wxpython which uses the Mac user interface like round buttons and
> > blueish tabs in GNUmed.
> >
> > It has something to do with the options in MacPort. You could check if
> > wxpyhton in MacPorts lets you select options which lead to the Macish
> > user interface instead of the X11 one.
>
> Before messing/worrying too much with/about this I should
> chip in with the fact that it will not gain much. It won't
> be possible to somehow "activate" the missing
> ResizeAndRotate code in the Mac X server. Simply setting a
> Macish theme won't make GNUmed be Macish either (it may look
> better, though). There's some special code in wxPython to
> make wxPython apps behave more Macish but we are (I am)
> quite some way from worrying about that.
I am not sure I understand what you are saying.
I was referring to this
Mac OS X
- wxPython needs a special Mac OS X-specific build of Python, called a Framework build, in order to work. Panther and Tiger include a Framework build of Python 2.3, or you can get a newer version of Python the Python Framework from the Python site.
- Note to Fink users: Versions of Python installed by Fink or other unix-like package repositories cannot run wxPython (unless you install and run X11 and use a wxGTK version of wxPython...). You need to use Apple's Framework builds, or a third-party Framework build to be able to have a native Aqua GUI.
However, MacPorts now provides a framework build of Python 2.5 and wxWidgets runs great (and with Aqua!) when using MacPorts. This is not a slight towards Fink, I'm just pointing out that it would be peachy if a note was added that everything works great in MacPorts.
Furthermore, Leopard also provides a framework build of Python 2.5 and that fact is not mentioned.
Here is more relevant info:
https://trac.macports.org/ticket/24350
I propose a new port "wxWidgets-python" to be the dependency for py*-wxpython with a version number that is in sync with that of the latest stable release of wxPython.
I also add the variant "gtk" for both wxWidgets-python and py26-wxpython. This allows these ports to be built against x11/gtk2 on 64 bit Snow Leopard, avoiding universal builds. This is an effective stop-gap until wx developers release 2.9.x with full Cocoa support.
wxWidgets_Portfile.diff 
(3.2 KB) - added by address@hidden 6 weeks ago.
added gtk variant
wxWidgets-python_Portfile.diff (0.9 KB) - added by address@hidden 3 weeks ago.
add conflict to wxWidgets and flags for i386 carbon
http://wiki.wxpython.org/TentativeRoadmap
OS X Cocoa build: (soonish) 2.9.1 may also include a build of wxPython based on Cocoa instead of Carbon. If it's not ready by the time of the 2.9.1 release then I expect it soon after.
OS X 64-bit build: (soonish) Once the Cocoa port of wxWidgets and wxPython is in a usable state then I'll look at adding a 64-bit personality to the fat binaries as well.
Summary
I am confused. WTF. Aqua, Carbon, Cocoa ? What is next ? Banana ? I assume that snow leopard has a framework build. There is a gtk2 build and another (aqua/carbon/cocoa) build. I would thing that Jim has a GTK2 build right now which is fine. It might look a little different and it may integrate into the Apple menu strucuture. In the Macish build all the GNUmed menu options are integrated into the Mac menu at the top. On Tiger I assume the *other* build is enabled.
Just try if you get the carbon option set or leave it if this is no problem for you.
Sebastian