I suppose they are very different pieces of software and one of the nice
things about vpython is how focused it is. I'm wishing that I could
build more complex shapes, especially with Boolean shape operations,
assemble them into mechanisms and have them simulated in a 'real'
environment. This is probably out of the scope of vpython.
=20
S
=20
-----Original Message-----
From: vis...@li...
[mailto:vis...@li...] On Behalf Of
Arthur
Sent: Tuesday, June 01, 2004 10:43 AM
To: vis...@li...
Subject: re: [Visualpython-users] openCASCADE
=20
=20
=20
_____ =20
From: Arthur [mailto:aj...@ix...]=20
Sent: Tuesday, June 01, 2004 1:42 PM
To: 'Kuzminski, Stefan R'; 'vis...@li...'
Subject: RE: [Visualpython-users] openCASCADE
=20
From: vis...@li...
[mailto:vis...@li...] On Behalf Of
Kuzminski, Stefan R
Sent: Tuesday, June 01, 2004 10:57 AM
To: vis...@li...
Subject: [Visualpython-users] openCASCADE
=20
Has anyone looked into bringing the OpenCASCADE python bindings into
vpython?
=20
http://www.pythonizer.org/pythoncascade/pythoncascade.html
=20
=20
=20
=20
To what end ?
=20
Don't OpenCASCADE and VPython have very different purposes and scopes.
=20
I tend to see the "smallness" and focus of VPython as one of its main
strengths. =20
=20
And if one wants to work with something broad and large, what does
VPython bring to OpenCascade that isn't already there? The question's
intention being more than rhetorical, as I don't know anything about
OpenCascade beyond what I see on the web site.
=20
Art
|
