From: Jonathan B. <jbr...@ea...> - 2006-05-31 23:14:08
|
On Wed, 2006-05-31 at 15:58 -0700, Dethe Elza wrote: > On 5/31/06, Jonathan Brandmeyer <jbr...@ea...> wrote: > > On Wed, 2006-05-31 at 06:41 -0700, Jeremy Sachs wrote: > > > Just to be clear on the matter, what are the major hurdles that must > > > be jumped to implement VPython in Mac OS X's Aqua interface? > > > > A developer that knew something about Aqua, for starters. Said > > developer would need to write an implementation of src/gtk2/display.cpp > > and/or src/gtk2/render_surface.cpp (in the vpython-core2 module). > > > > > And has anyone been making any recent progress that deserves mention? > > > > Not that I'm aware. Someone mentioned that they would give it effort a > > while back, but I haven't heard from them since. > > That was probably me. I struggled with just getting it to compile, > without having to pull in all the dependencies from Fink, but failed. > My autoconf-foo was not good enough, and I had to switch back to > projects that are tractable for me. I know Cocoa and OpenGL, and can > find my way around Aqua, but the VPython build system defeated me. How much Cocoa code did you get done for VPython before you threw in the towel? I can manage to beat on the autotools if you can supply the Cocoa code. > Personally, I'd like to see a VPython built on top of PyOpenGL, so it > would play well with others (PyOpenGL works with PyGame, Cocoa, > Windows, Linux, etc.) Since PyOpenGL is getting some speedups these > days (and machines are about 100x faster than when VPython was > created) it ought to be feasible. Plus the code would be accessible > to more pythonistas. I did some PyOpenGL stuff quite recently. Unfortunately, it is _much_ too slow for VPython. > I'm still willing to try again sometime, when I have time to futz with > it, but that won't be soon. -Jonathan |