Maybe a Mac expert will step forward and make a version of Visual that can be driven by the native Mac Python? After all, OpenGL doesn't need X11, it's just that lacking Mac-specific expertise the only way we could get VPython running on Mac OSX was to piggyback off the Linux/Unix version. What is needed is really just one file, equivalent to wgl.cpp which handles Windows aspects (creating the graphics window, handling keyset and moust inputs, etc.). Is there anyone in the VPython commmunity who could write macgl.cpp?
On Tue, 2005-06-07 at 11:54 -0400, Jon Schull wrote:
That would be a very big step forward in lots of ways....
Is it clear that this requires understanding of VPython internals?
Only somewhat. The platform-specific parts of VPython are fairly
limited; the hardest part is probably learning the OSX GUI APIs.
You would need to write implementations of glContext and glFont
(declared in glcontext.h). You will probably also need to write a
platmac.{cpp,h} files that contains all of the functionality present in
plat{linux,win}.{cpp,h}. You should be able to get a considerable
amount of reuse from the platlinux.{h,cpp} files. If there is any
ambiguity about the responsibilities of these classes, I'll be happy to
help out anyone who would be doing this work.
I would recommend using the Carbon or Core Platform C interfaces rather
than Cocoa via Objective-C++.
-Jonathan
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon Schull, Ph.D.
Associate Professor
Information Technology
Rochester Institute of Technology
102 Lomb Memorial Drive
Rochester, New York 14623
On Jun 7, 2005, at 9:53 PM, Bob Ippolito wrote:
On Jun 6, 2005, at 8:59 PM, Jon Schull wrote:
Please forgive the cross-post. I think this is a cross group issue.
I've newly installed Tiger and would like to avoid the dueling pythons problem that plagued me with 0SX 10.3. It would be nice to be running just one python, but I suppose that would be asking too much?
Double clicking the apps works fine. But when I type "python" from terminal I get python Apple's python 2.3.5. I'm sure this is obvious to many, but I'm also sure I'm not the only person who starts getting uneasy at this point. So before I go too deep, I thought I'd ask....
Is there a "right" way to be using just one (or just two) pythons and avoid conflicts?
Put /usr/local/bin before /usr/bin on your PATH. The default PATH includes ONLY Apple-installed components. This is an "issue" with any third party software that has a command-line interface, as they all (should be, anyway) install to /usr/local/bin.
-bob
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
_______________________________________________
Visualpython-users mailing list
