Re: [Visualpython-users] History and Status?

[Arthur <ajs...@op...>]

Bruce writes:

> Design Goals:
>
> 1.  Preserve at least the current level of usability and performance
> 2.  Make VPython easier to maintain
> 3.  Make VPython easier to extend.  There should be a gentle path
> between user and implementor, not a gaping chasm.
> 4.  Make VPython more useful and less limiting for experts, so as to
> increase the availability of expert help to the VPython community.
> 5.  Make VPython play nicer with other Python packages and tools

Well thought out.

As to point 5, I am quite convinced that a step toward that goal is the use
of Python's distutils as the basis for the distribution mechanism. I can be
and would be willing to be helpful here - as I have gotten hands on with it,
and find it friendly and flexible.

As I have said many times, I think VPython has some unique qualities.  Which
if built upon along the lines you suggest, will, I believe allow it be an
enduring and even more significant project.

But as you suggest, it would need to atttract some developers to get it over
the hump to a next phase.

I, for one, am willing to spend time on it.  The problem being I am more of
a Python person than a C++, or C guy. But I am willing to approach the
learning curve, especially if there are brains around to pick.  I do come to
it with a decent grasp of OpenGL. Though I would need to get up on some of
the newer version features.  That being VPython's fault - as I was doing
more directly in PyOpenGL before VPython came along, with much of what I was
trying to do - prebuilt.

I am even willing to try to do some recruiting for the project- perhaps at
the PyCon event in DC next month.

How do we work toward establishing some concrete ideas for bringing more of
your thought experiment to life.

Art