From: Bruce S. <Bru...@nc...> - 2011-01-25 00:03:12
|
Ah. Of course. I made the corresponding mistake of forgetting that in the Fink environment the demise of Carbon isn't a problem. In fact, Fink may in the future again be the basis for VPython if no one figures out how to make a Cocoa-based VPython. The problem with that is that many Mac users very much want the standard Mac look and feel, as was made clear when the only Mac version was based on X11. Bruce Sherwood On Mon, Jan 24, 2011 at 3:41 PM, Martin Costabel <cos...@wa...> wrote: > Bruce, > > you are right; I keep forgetting that Fink's vpython uses X11 graphics. For > aqua graphics, the non-existence of some parts of Carbon for 64bit is indeed > a serious obstacle. > > Martin > > On 24/01/11 17:21 , Bruce Sherwood wrote: >> >> Martin, that's very good news, but puzzling. I thought that there was >> no support for Carbon within Mac 64-bit programs? The demise of Carbon >> has had me very worried, as no one seems to know how to make VPython >> work within a Cocoa environment. >> >> Bruce Sherwood >> >> On Mon, Jan 24, 2011 at 5:11 AM, Martin Costabel<cos...@wa...> >> wrote: >>> >>> On 24/01/11 11:17 , Daniel Farrell wrote: >>> [] >>>> >>>> * Is there a fundamentally reason for sticking to 32-bit (e.g. >>>> dependency difficulties?) >>> >>> I can't answer your other questions, but this one I can: There is no >>> such reason. Fink (an older "community driven package manager for >>> MacOS") has vpython version 5.40 (package visual-py27) that builds OK in >>> the 64bit tree. >>> > |