visualpython-users

[Visualpython-users] Experimental Mac Installer on vpython.org, (and linux setup.py ready for testing)

[Steve S. <st...@sp...>]

Hi VPython Mac/Linux Users,

First mac folks...

If you're a brave soul, interested in testing the first experimental release of Visual Python for Macintosh you can get it here:

<http://vpython.org/contents/download_mac.html>

(See the paragraph: Experimental VPython based on the cross-platform library wxPython. First, download and install Python-2.7.3, then install Experimental VPython 6.01. See the documentation included with this VPython for a change in VPython: you must include a rate statement in animation loops.)

Links are there for both the Python and VPython downloads.

Here are more details, slightly modified from Bruce's Windows announcement of 12-26-2012:

On the Macintosh download page at vpython.org is an experimental VPython based on the cross-platform library wxPython. It requires the python.org universal (32 and 64-bit version of Python 2.7, link provided).

Like the windows version, this experimental version differs from the older VPython (5.74 and before) by eliminating nearly all platform-dependent code and by eliminating the threading associated with rendering. This makes it possible for the first time to run on 64-bit Python on the Mac and will simplify maintenance and further development of VPython. It is also likely to make possible adding standard buttons, menus, etc. to a window that contains a VPython scene. 

The new version makes one essential change to the syntax of VPython programs. Now, an animation loop MUST contain a rate statement, which limits the number of loop iterations per second as before but also when appropriate (about 30 times per second) updates the 3D scene and handles mouse and keyboard events. Without a rate statement, the scene will not be updated until and unless the loop is completed.

The heart of the user-interface code (creating windows and handling events) is the file site-packages/visual_common/create_display.py. It is imported by visual/__init__.py and by /vis/__init__.py; the difference is that for convenience visual imports math and numpy, whereas vis doesn't.

Please report issues to the Github repository https://github.com/BruceSherwood/vpython-wx, or to the VPython mailing list.

You can stop reading now, unless you are an expert mac user, or a linux user and want to really push the envelope. ;-)

-----------------------

Building vpython on linux and the mac is now easier than ever! You can find the instructions in the INSTALL.txt of the source distribution from github. Basically, once you have dependencies installed, it's just "python setup.py build" and "sudo python setup.py install". For the mac you'll need Xcode.app, and source downloads of wxPython-2.9.4, boost, and so on. For linux you can use apt-get (or equivalent) to install dependencies.

Please let us know if you choose to build it yourself and you have success, and especially if you have failure. We want to make this as foolproof as we can.

Finally, for mac experts: if you already have numpy/polygon/ttfquery installed you should "customize" your install and uncheck those items.

If you already have wxPython installed, make sure it's the cocoa universal version 2.9.4 and then "customize" and uncheck it as well.

Enjoy!
-steve

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Steve S. <st...@sp...>]

The source you need is wxPython-2.9.4.0 not 2.8. Sorry.

to apply the patch go to the wxPython-src-2.9.4.0 directory (not the wxPython directory that it contains) and type:

patch -p0 < path/to/the/patch/file

Let us know if that works!
-steve

On Jan 14, 2013, at 5:25 PM, Paul Camp wrote:

> Trying to follow the instructions in INSTALL.txt. I get up to the patch and when I try to execute that, I get the following error message: 
> 
> can't find file to patch at input line 5 
> Perhaps you used the wrong -p or --strip option? 
> The text leading up to this was: 
> -------------------------------------------------- 
> Index:configure 
> ============================================= 
> - - - configure (revision 72192) 
> + + + configure (working copy) 
> --------------------------------------------------- 
> 
> Its certainly plausible that I'm located in the wrong directory. The instruction "place the file in the wxPython directory" is a little inscrutable since I didn't know off the bat exactly where that is. However, /usr/include/wx-2.8 certainly seems to contain all the relevant files addressed by the patch. What am I missing? 
> 
> 
> Dr. Paul J. Camp
> Physics Department
> Spelman College
> Atlanta, GA   30314
> 404-270-5864
> 
> "The beauty of the cosmos derives not only from unity in variety
>       but also from variety in unity"
>                 -- Umberto Eco
>                     The Name of the Rose 
> 
> 
> 
> From:        Bruce Sherwood <Bru...@nc...> 
> To:        C Anthony Risinger <an...@xt...> 
> Cc:        vpusers <vis...@li...> 
> Date:        01/13/2013 10:42 AM 
> Subject:        Re: [Visualpython-users] How VPython 6 differs from VPython 5 
> 
> 
> 
> Thanks for pointing out the outdated reference. Here is where the source code is: 
> 
> https://github.com/BruceSherwood/vpython-wx 
> 
> Steve Spicklemire is doing terrific work on simplifying building on all platforms, including Linux. For the moment, read the file INSTALL.txt. We have no Linux "target", but as it happens Steve and I have been doing our testing on Ubuntu. Don't hesitate to ask for clarification if you run into difficulties. 
> 
> Bruce Sherwood 
> 
> 
> On Sun, Jan 13, 2013 at 3:36 AM, C Anthony Risinger <an...@xt...> wrote: 
> On Sun, Jan 13, 2013 at 1:15 AM, Bruce Sherwood <Bru...@nc...> wrote:
> > Here is detailed information on how VPython 6 differs from VPython 5, which
> > will be incorporated in the Help for upcoming releases of VPython 6.
> 
> the website directs me to https://github.com/vpython/visual/ but this
> repository has not been updated since August, and no other branches
> exist.
> 
> where is the development for VPython 6 happening?
> 
> ...i would like to get a Linux build running for an in-house demo this
> Thursday, so any notes appreciated.  note: i don't need a full-blown
> installable pip package or anything, just the code and any pertinent
> info related to the build :)
> 
> for what it's worth, this is fantastic work! i've been "patiently"
> anticipating a Linux package, but i've no problem at all handling that
> part myself (im on Arch anyway... i expect Ubuntu or something is the
> focused target)
> 
> thanks!
> 
> --
> 
> C Anthony 
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_123012_______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
> 
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512_______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Paul C. <PC...@sp...>]

Trying to follow the instructions in INSTALL.txt. I get up to the patch 
and when I try to execute that, I get the following error message:

can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------------------------------
Index:configure
=============================================
- - - configure (revision 72192)
+ + + configure (working copy)
---------------------------------------------------

Its certainly plausible that I'm located in the wrong directory. The 
instruction "place the file in the wxPython directory" is a little 
inscrutable since I didn't know off the bat exactly where that is. 
However, /usr/include/wx-2.8 certainly seems to contain all the relevant 
files addressed by the patch. What am I missing?


Dr. Paul J. Camp
Physics Department
Spelman College
Atlanta, GA   30314
404-270-5864

"The beauty of the cosmos derives not only from unity in variety
       but also from variety in unity"
                 -- Umberto Eco
                     The Name of the Rose



From:   Bruce Sherwood <Bru...@nc...>
To:     C Anthony Risinger <an...@xt...>
Cc:     vpusers <vis...@li...>
Date:   01/13/2013 10:42 AM
Subject:        Re: [Visualpython-users] How VPython 6 differs from 
VPython 5



Thanks for pointing out the outdated reference. Here is where the source 
code is:

https://github.com/BruceSherwood/vpython-wx

Steve Spicklemire is doing terrific work on simplifying building on all 
platforms, including Linux. For the moment, read the file INSTALL.txt. We 
have no Linux "target", but as it happens Steve and I have been doing our 
testing on Ubuntu. Don't hesitate to ask for clarification if you run into 
difficulties.

Bruce Sherwood


On Sun, Jan 13, 2013 at 3:36 AM, C Anthony Risinger <an...@xt...> 
wrote:
On Sun, Jan 13, 2013 at 1:15 AM, Bruce Sherwood <Bru...@nc...> 
wrote:
> Here is detailed information on how VPython 6 differs from VPython 5, 
which
> will be incorporated in the Help for upcoming releases of VPython 6.

the website directs me to https://github.com/vpython/visual/ but this
repository has not been updated since August, and no other branches
exist.

where is the development for VPython 6 happening?

...i would like to get a Linux build running for an in-house demo this
Thursday, so any notes appreciated.  note: i don't need a full-blown
installable pip package or anything, just the code and any pertinent
info related to the build :)

for what it's worth, this is fantastic work! i've been "patiently"
anticipating a Linux package, but i've no problem at all handling that
part myself (im on Arch anyway... i expect Ubuntu or something is the
focused target)

thanks!

--

C Anthony
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_123012
_______________________________________________
Visualpython-users mailing list
Vis...@li...
https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Bruce S. <Bru...@nc...>]

Since this was copied to the Python-Dev list, I want to go on record as
stating firmly that there is no evidence whatsoever to substantiate claims
that there has ever been some kind of conflict between VPython and Python.

Since __future__ was also mentioned, I'll take the opportunity to say that
I've been very impressed by the way the Python community has handled the
difficult 2->3 transition. For example, it has been a big help to the
educational uses of VPython that we could tell students simply to start
with "from __future__ import division, print_function", put parens around
print arguments, and thereby make it irrelevant whether they used Python 2
or Python 3. Many thanks to the Python development community!

Bruce Sherwood


On Sun, Jan 13, 2013 at 6:41 PM, Mark Janssen <dre...@gm...>wrote:

> On Sun, Jan 13, 2013 at 12:14 PM, Bruce Sherwood
> <Bru...@nc...> wrote:
> > For the record, I do not know of any evidence whatsoever for a supposed
> > "split" between the tiny VPython community and the huge Python community
> > concerning floating point variables. Nor do I see anything in Python that
> > needs to be "fixed".
>
> Well it was bit enough that the python community created a brand-new
> language construct called import __future__ -- something never
> considered before then and which actually changes the behavior of
> python unlike any other module.  And perhaps I've just felt it more
> because I was a big proponent of both 3-d graphics as a way to keep
> python a draw for beginning programmers and also a big fan of
> scientific simulation.  No one had anything near vpython back then.
> (But ultimately I need to stop mentioning this issue to this vpython
> list because it's really the Python group which need to get back in
> sync.)
>
> > The new (currently experimental) version of VPython based on wxPython
> must,
> > in order to run in a Cocoa environment on the Mac, make the interact
> loop be
> > the primary thread, with the user's Python calculations at worst a
> secondary
> > thread, which is the opposite of the older VPython, where the
> > interval-driven rendering thread was secondary to the user's
> calculations.
> > By the unusual stratagem of having VPython import the user's program it
> has
> > been possible to make this work, and at the same time greatly simplify
> the
> > C++ component of VPython by eliminating threading, with additional
> important
> > simplification from eliminating essentially all platform-dependent code
> > thanks to the multiplatform character of wxPython. The result is that
> nearly
> > all existing VPython programs will work without change, at the very small
> > cost of a few marginal cases requiring minor tweaking. I should alter the
> > documentation to make this important property of the new version more
> > salient.
>
> I need to analyze this more carefully before commenting further....
>
> mark
>

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Mark J. <dre...@gm...>]

On Sun, Jan 13, 2013 at 12:14 PM, Bruce Sherwood
<Bru...@nc...> wrote:
> For the record, I do not know of any evidence whatsoever for a supposed
> "split" between the tiny VPython community and the huge Python community
> concerning floating point variables. Nor do I see anything in Python that
> needs to be "fixed".

Well it was bit enough that the python community created a brand-new
language construct called import __future__ -- something never
considered before then and which actually changes the behavior of
python unlike any other module.  And perhaps I've just felt it more
because I was a big proponent of both 3-d graphics as a way to keep
python a draw for beginning programmers and also a big fan of
scientific simulation.  No one had anything near vpython back then.
(But ultimately I need to stop mentioning this issue to this vpython
list because it's really the Python group which need to get back in
sync.)

> The new (currently experimental) version of VPython based on wxPython must,
> in order to run in a Cocoa environment on the Mac, make the interact loop be
> the primary thread, with the user's Python calculations at worst a secondary
> thread, which is the opposite of the older VPython, where the
> interval-driven rendering thread was secondary to the user's calculations.
> By the unusual stratagem of having VPython import the user's program it has
> been possible to make this work, and at the same time greatly simplify the
> C++ component of VPython by eliminating threading, with additional important
> simplification from eliminating essentially all platform-dependent code
> thanks to the multiplatform character of wxPython. The result is that nearly
> all existing VPython programs will work without change, at the very small
> cost of a few marginal cases requiring minor tweaking. I should alter the
> documentation to make this important property of the new version more
> salient.

I need to analyze this more carefully before commenting further....

mark

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Bruce S. <Bru...@nc...>]

Here's an improved version of the differences between VPython 5 and 6;

Changes from VPython 5

VPython 6 will run almost all old VPython programs correctly without change
The following details about changes may be important in a few unusual cases.

An animation loop must contain a rate or sleep statement, which limits the
number of loop iterations per second as before but also when appropriate
(about 30 times per second) updates the 3D scene and handles mouse and
keyboard events. Without a rate or sleep statement, the scene will not be
updated until and unless the loop is completed. Most animation loops
already contain a rate statement anyway, to make the animation not run too
fast.

You should use the new function sleep rather than time.sleep. The new
function periodically renders the scene and processes mouse events, making
it possible to continue using zoom and rotate, whereas time.sleep does not
do this. Programs that use time.sleep will work, but you won't be able to
zoom or rotate during the sleep period.

You must import visual or vis before importing graph or controls or
filedialog, which most users have always done anyway.

*Your own program is imported by VPython:* For technical reasons, it is
necessary for VPython 6 to do something rather unusual. When you import
visual (or vis), your own program is in turn imported by the visual module.
For this reason, you should import visual near the start of your program,
because any executable statements preceding the import will be executed
twice. The import of visual is also re-executed, but this is harmless
because in Python a repeated import doesn't repeat the calculations in the
imported module.

*Importing your own modules:* If you create your own module (lib.py, say)
that imports visual, and you import lib from a program named demo.py, you
need to import visual in demo.py before importing lib, so that demo is the
base program (when lib imports visual, that will be the second import of
visual and will not lead to lib being imported by visual). Note that the
standard trick of testing a module on the basis of __name__=='__main__'
won't work, because the program will be imported by visual. To test a
module, import it from a test program rather than trying to use
__name__=='__main__' within the module.

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Bruce S. <Bru...@nc...>]

For the record, I do not know of any evidence whatsoever for a supposed
"split" between the tiny VPython community and the huge Python community
concerning floating point variables. Nor do I see anything in Python that
needs to be "fixed".

The new (currently experimental) version of VPython based on wxPython must,
in order to run in a Cocoa environment on the Mac, make the interact loop
be the primary thread, with the user's Python calculations at worst a
secondary thread, which is the opposite of the older VPython, where the
interval-driven rendering thread was secondary to the user's calculations.
By the unusual stratagem of having VPython import the user's program it has
been possible to make this work, and at the same time greatly simplify the
C++ component of VPython by eliminating threading, with additional
important simplification from eliminating essentially all
platform-dependent code thanks to the multiplatform character of wxPython.
The result is that nearly all existing VPython programs will work without
change, at the very small cost of a few marginal cases requiring minor
tweaking. I should alter the documentation to make this important property
of the new version more salient.

Minor point: The meaning of the new VPython "sleep" is precisely to
relinquish control to the OS, including the GUI. During sleep one wants the
wxPython window controls to remain active, which will not be the case with
time.sleep, which knows nothing about the wxPython interact loop. So I
think the meaning of "sleep" is the usual meaning.

Bruce Sherwood


On Sun, Jan 13, 2013 at 9:13 AM, Mark Janssen <dre...@gm...>wrote:

> On Sun, Jan 13, 2013 at 1:15 AM, Bruce Sherwood <Bru...@nc...>
> wrote:
> > Here is detailed information on how VPython 6 differs from VPython 5,
> which
> > will be incorporated in the Help for upcoming releases of VPython 6. Note
> > that the fact that in a main program __name__ isn't '__main__' is an
> > unavoidable "feature", not a bug. That is, there doesn't seem to be a
> way to
> > make this work.
>
> Hi, Bruce.  I think there are two ways of fixing this.  One is to get
> down to the C language level, and share the C main() loop, which will
> percolate back up into the CPython loop.  The other involves mending
> the split that I've been mentioning that happened over floating point
> between the VPython developers and the Python-dev group.  Then perhaps
> Guido will accept VPython using/sharing the __main__ "loop".  (I'm
> CC'ing him in this message.)  So, either of these tracks should fix
> this problem.  This is why I keep mentioning the important of healing
> that split between the parties arguing in the two camps.  Perhaps Tim
> Peters will be able help bridge this gap.
>
> > Changes from VPython 5
> >
> > The new version makes an essential change to the syntax of VPython
> programs.
> > Now, an animation loop MUST contain a rate or sleep statement, which
> limits
> > the number of loop iterations per second as before but also when
> appropriate
> > (about 30 times per second) updates the 3D scene and handles mouse and
> > keyboard events. Without a rate or sleep statement, the scene will not be
> > updated until and unless the loop is completed.
>
> I think this is perfectly acceptible and is just a necessary
> restriction wherefrom the OS *must* maintain ultimate control of I/O.
> Python sits in userspace surrounded by the larger computation
> environment, so this is only fair that an OS call is made so that it
> can keep things in "check".   Naming it "sleep" is okay, but makes it
> sound more like a  voluntary thing, and as you probably know, is the
> traditional name for relinquishng some control to the OS.  (cf. Unix
> Systems Programming, Robbins, et al.)
>
> > You should use the new function sleep rather than time.sleep. The new
> > function periodically renders the scene and processes mouse events,
> making
> > it possible to continue using zoom and rotate, whereas time.sleep does
> not
> > do this.
>
> This is strange to me.  I think this is where VPython must be ahead of
> the curve and not close enough to the Linux development communities.
>
> > For technical reasons, it is necessary for VPython 6 to do something
> rather
> > unusual. When you import visual (or vis), your own program is in turn
> > imported by the visual module.
>
> Again this is because of the faction that was created by in 200?,
> regarding the Vpython community vs. the python-dev.  Really, this
> should be mended.
>
> Anyway, I hope that any of this made sense.
>
> Thanks for your help!
>
> Mark
>

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Mark J. <dre...@gm...>]

On Sun, Jan 13, 2013 at 1:15 AM, Bruce Sherwood <Bru...@nc...> wrote:
> Here is detailed information on how VPython 6 differs from VPython 5, which
> will be incorporated in the Help for upcoming releases of VPython 6. Note
> that the fact that in a main program __name__ isn't '__main__' is an
> unavoidable "feature", not a bug. That is, there doesn't seem to be a way to
> make this work.

Hi, Bruce.  I think there are two ways of fixing this.  One is to get
down to the C language level, and share the C main() loop, which will
percolate back up into the CPython loop.  The other involves mending
the split that I've been mentioning that happened over floating point
between the VPython developers and the Python-dev group.  Then perhaps
Guido will accept VPython using/sharing the __main__ "loop".  (I'm
CC'ing him in this message.)  So, either of these tracks should fix
this problem.  This is why I keep mentioning the important of healing
that split between the parties arguing in the two camps.  Perhaps Tim
Peters will be able help bridge this gap.

> Changes from VPython 5
>
> The new version makes an essential change to the syntax of VPython programs.
> Now, an animation loop MUST contain a rate or sleep statement, which limits
> the number of loop iterations per second as before but also when appropriate
> (about 30 times per second) updates the 3D scene and handles mouse and
> keyboard events. Without a rate or sleep statement, the scene will not be
> updated until and unless the loop is completed.

I think this is perfectly acceptible and is just a necessary
restriction wherefrom the OS *must* maintain ultimate control of I/O.
Python sits in userspace surrounded by the larger computation
environment, so this is only fair that an OS call is made so that it
can keep things in "check".   Naming it "sleep" is okay, but makes it
sound more like a  voluntary thing, and as you probably know, is the
traditional name for relinquishng some control to the OS.  (cf. Unix
Systems Programming, Robbins, et al.)

> You should use the new function sleep rather than time.sleep. The new
> function periodically renders the scene and processes mouse events, making
> it possible to continue using zoom and rotate, whereas time.sleep does not
> do this.

This is strange to me.  I think this is where VPython must be ahead of
the curve and not close enough to the Linux development communities.

> For technical reasons, it is necessary for VPython 6 to do something rather
> unusual. When you import visual (or vis), your own program is in turn
> imported by the visual module.

Again this is because of the faction that was created by in 200?,
regarding the Vpython community vs. the python-dev.  Really, this
should be mended.

Anyway, I hope that any of this made sense.

Thanks for your help!

Mark

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Bruce S. <Bru...@nc...>]

vpython.org has been updated to reference the new source code repository.

Bruce Sherwood


On Sun, Jan 13, 2013 at 8:40 AM, Bruce Sherwood <Bru...@nc...>wrote:

> Thanks for pointing out the outdated reference. Here is where the source
> code is:
>
> https://github.com/BruceSherwood/vpython-wx
>
> Steve Spicklemire is doing terrific work on simplifying building on all
> platforms, including Linux. For the moment, read the file INSTALL.txt. We
> have no Linux "target", but as it happens Steve and I have been doing our
> testing on Ubuntu. Don't hesitate to ask for clarification if you run into
> difficulties.
>
> Bruce Sherwood
>
>
> On Sun, Jan 13, 2013 at 3:36 AM, C Anthony Risinger <an...@xt...>wrote:
>
>> On Sun, Jan 13, 2013 at 1:15 AM, Bruce Sherwood <Bru...@nc...>
>> wrote:
>> > Here is detailed information on how VPython 6 differs from VPython 5,
>> which
>> > will be incorporated in the Help for upcoming releases of VPython 6.
>>
>> the website directs me to https://github.com/vpython/visual/ but this
>> repository has not been updated since August, and no other branches
>> exist.
>>
>> where is the development for VPython 6 happening?
>>
>> ...i would like to get a Linux build running for an in-house demo this
>> Thursday, so any notes appreciated.  note: i don't need a full-blown
>> installable pip package or anything, just the code and any pertinent
>> info related to the build :)
>>
>> for what it's worth, this is fantastic work! i've been "patiently"
>> anticipating a Linux package, but i've no problem at all handling that
>> part myself (im on Arch anyway... i expect Ubuntu or something is the
>> focused target)
>>
>> thanks!
>>
>> --
>>
>> C Anthony
>>
>
>

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[Bruce S. <Bru...@nc...>]

Thanks for pointing out the outdated reference. Here is where the source
code is:

https://github.com/BruceSherwood/vpython-wx

Steve Spicklemire is doing terrific work on simplifying building on all
platforms, including Linux. For the moment, read the file INSTALL.txt. We
have no Linux "target", but as it happens Steve and I have been doing our
testing on Ubuntu. Don't hesitate to ask for clarification if you run into
difficulties.

Bruce Sherwood


On Sun, Jan 13, 2013 at 3:36 AM, C Anthony Risinger <an...@xt...> wrote:

> On Sun, Jan 13, 2013 at 1:15 AM, Bruce Sherwood <Bru...@nc...>
> wrote:
> > Here is detailed information on how VPython 6 differs from VPython 5,
> which
> > will be incorporated in the Help for upcoming releases of VPython 6.
>
> the website directs me to https://github.com/vpython/visual/ but this
> repository has not been updated since August, and no other branches
> exist.
>
> where is the development for VPython 6 happening?
>
> ...i would like to get a Linux build running for an in-house demo this
> Thursday, so any notes appreciated.  note: i don't need a full-blown
> installable pip package or anything, just the code and any pertinent
> info related to the build :)
>
> for what it's worth, this is fantastic work! i've been "patiently"
> anticipating a Linux package, but i've no problem at all handling that
> part myself (im on Arch anyway... i expect Ubuntu or something is the
> focused target)
>
> thanks!
>
> --
>
> C Anthony
>

Re: [Visualpython-users] How VPython 6 differs from VPython 5

[C A. R. <an...@xt...>]

On Sun, Jan 13, 2013 at 1:15 AM, Bruce Sherwood <Bru...@nc...> wrote:
> Here is detailed information on how VPython 6 differs from VPython 5, which
> will be incorporated in the Help for upcoming releases of VPython 6.

the website directs me to https://github.com/vpython/visual/ but this
repository has not been updated since August, and no other branches
exist.

where is the development for VPython 6 happening?

...i would like to get a Linux build running for an in-house demo this
Thursday, so any notes appreciated.  note: i don't need a full-blown
installable pip package or anything, just the code and any pertinent
info related to the build :)

for what it's worth, this is fantastic work! i've been "patiently"
anticipating a Linux package, but i've no problem at all handling that
part myself (im on Arch anyway... i expect Ubuntu or something is the
focused target)

thanks!

-- 

C Anthony

[Visualpython-users] How VPython 6 differs from VPython 5

[Bruce S. <Bru...@nc...>]

Here is detailed information on how VPython 6 differs from VPython 5, which
will be incorporated in the Help for upcoming releases of VPython 6. Note
that the fact that in a main program __name__ isn't '__main__' is an
unavoidable "feature", not a bug. That is, there doesn't seem to be a way
to make this work. As described below, the way to test a module is to
import it from a test routine.

Changes from VPython 5

The new version makes an essential change to the syntax of VPython
programs. Now, an animation loop *MUST* contain a rate or sleep statement,
which limits the number of loop iterations per second as before but also
when appropriate (about 30 times per second) updates the 3D scene and
handles mouse and keyboard events. Without a rate or sleep statement, the
scene will not be updated until and unless the loop is completed.

You should use the new function sleep rather than time.sleep. The new
function periodically renders the scene and processes mouse events, making
it possible to continue using zoom and rotate, whereas time.sleep does not
do this.

You must import visual or vis before importing graph or controls or
filedialog, which most users have always done anyway.

For technical reasons, it is necessary for VPython 6 to do something rather
unusual. When you import visual (or vis), your own program is in turn
imported by the visual module. For this reason, you should import visual
near the start of your program, because any executable statements preceding
the import will be executed twice. The import of visual is also
re-executed, but this is harmless because in Python a repeated import
doesn't repeat the calculations in the imported module.

*Importing your own modules:* If you create your own module (lib.py, say)
that imports visual, and you import lib from a program named demo.py, you
need to import visual in demo.py before importing lib, so that demo is the
base program (when lib imports visual, that will be the second import of
visual and will not lead to lib being imported by visual). Note that the
standard trick of testing a module on the basis of __name__=='__main__'
won't work, because the program will be imported by visual. To test a
module, import it from a test program rather than trying to use
__name__=='__main__' within the module.

Re: [Visualpython-users] Experimental 64-bit VPython for Windows based on wxPython

[Bruce S. <Bru...@nc...>]

Thanks again. Will look into.

Bruce Sherwood


On Fri, Jan 11, 2013 at 8:38 PM, Symion <kn...@ip...> wrote:

>  It seems I will have to look more closely at 'wx'.
>
> More bug reports:
>
> The following snippet returns an empty string for  '__name__'
>
> import vis
> print "My name is (%s)" %(__name__)
>
> -----------------------------------------------------
>
> The Second requires some explanation.
>
> When I spin the scene 'dragging the mouse with Right key pressed', the
> spin stops abruptly!
> Also when I Zoom in or out, I hit a barrier and the zoom freezes.
> After some experimentation, it appears the mouse cursor is hitting the
> Screen Boundary (even though the mouse is invisible).
>
> -----------------------------------------------------
> Symion
>
>
>
>
>
>
> On 11/01/2013 2:26 AM, Bruce Sherwood wrote:
>
> Thanks much for the report, including the bug report.
>
>  It is intended to open up VPython to make it possible to add buttons,
> sliders, etc., using the capabilities of wxPython (not Tcl). The first task
> was simply (well, not so simply) to replicate existing VPython
> capabilities. Currently, when you create a display object, that's a
> composite in the sense that it creates a window and also creates an OpenGL
> canvas that fills that window. Presumably what is needed is a window object
> that creates a window, and a canvas object that creates an OpenGL canvas
> somewhere in that window, in which case you could then add other widgets to
> the window. That would leave the display object as a convenience object,
> useful for many ordinary programs.
>
>  Bruce Sherwood
>
>
> On Wed, Jan 9, 2013 at 10:03 PM, Symion <kn...@ip...> wrote:
>
>>  This is wonderful!!
>> I now have Visual Python with a MENU item 'Files', running on Windows XP!
>> ALL examples have been run without error and everything seems very stable.
>>
>> Specifically I am using:
>>     Vpython ('6.00', 'release') running with Python 2.7.3 on Windows XP
>>
>> Of course this  raises lots of questions...
>>
>> Although 'help(vis)' provides much information and dir(vis.scene.window)
>> reveals 335 instancemethods and 82 other objects.
>> I do have a few questions that are not currently addressed by the
>> documentation.
>>
>> The main one is:
>>     How do I make new window Menu objects?
>>     Does Vpython use TCL? or do I have to learn wxPython methodologies?
>>      Is it possible to make Buttons, Sliders, List Boxes or even Window
>> Panes from WITHIN Visual?
>>
>> I hope the Documentation will eventually address these topics in detail.
>>
>> The Only 'error' I have found is this.
>> There is this anomalous error report when I am in V-IDLE shell and I
>> break program with 'ctrl-c'.
>>
>> Traceback (most recent call last):
>>   File "K:\Symion_12_12_12\visdemo.py", line 6
>>     import vis
>>   File "C:\Python27\lib\site-packages\vis\__init__.py", line 17
>>   File "C:\Python27\Lib\site-packages\visual_common\rate_plan.py", line
>> 122, in __call__
>>     sleep(desiredLoopTime - currTime)
>> TypeError: 'int' object is not callable
>>
>> Hope this means something to you...
>>
>> Finally, it is really good to see The Project evolving.
>>
>> Symion
>>
>>
>>
>> On 27/12/2012 4:59 AM, Bruce Sherwood wrote:
>>
>> Now available on the Windows download page at vpython.org is a 32-bit
>> version of the experimental VPython that's based on wxPython.
>>
>>  Bruce Sherwood
>>
>>
>>  _______________________________________________
>> Visualpython-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/visualpython-users
>>
>>  _______________________________________________
>> Visualpython-users mailing list
>> Vis...@li...
>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>>
>>
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122912
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>

Re: [Visualpython-users] Experimental 64-bit VPython for Windows based on wxPython

[Symion <kn...@ip...>]

It seems I will have to look more closely at 'wx'.

More bug reports:

The following snippet returns an empty string for  '__name__'

import vis
print "My name is (%s)" %(__name__)

-----------------------------------------------------

The Second requires some explanation.

When I spin the scene 'dragging the mouse with Right key pressed', the 
spin stops abruptly!
Also when I Zoom in or out, I hit a barrier and the zoom freezes.
After some experimentation, it appears the mouse cursor is hitting the 
Screen Boundary (even though the mouse is invisible).

-----------------------------------------------------
Symion





On 11/01/2013 2:26 AM, Bruce Sherwood wrote:
> Thanks much for the report, including the bug report.
>
> It is intended to open up VPython to make it possible to add buttons, 
> sliders, etc., using the capabilities of wxPython (not Tcl). The first 
> task was simply (well, not so simply) to replicate existing VPython 
> capabilities. Currently, when you create a display object, that's a 
> composite in the sense that it creates a window and also creates an 
> OpenGL canvas that fills that window. Presumably what is needed is a 
> window object that creates a window, and a canvas object that creates 
> an OpenGL canvas somewhere in that window, in which case you could 
> then add other widgets to the window. That would leave the display 
> object as a convenience object, useful for many ordinary programs.
>
> Bruce Sherwood
>
>
> On Wed, Jan 9, 2013 at 10:03 PM, Symion <kn...@ip... 
> <mailto:kn...@ip...>> wrote:
>
>     This is wonderful!!
>     I now have Visual Python with a MENU item 'Files', running on
>     Windows XP!
>     ALL examples have been run without error and everything seems very
>     stable.
>
>     Specifically I am using:
>         Vpython ('6.00', 'release') running with Python 2.7.3 on
>     Windows XP
>
>     Of course this  raises lots of questions...
>
>     Although 'help(vis)' provides much information and
>     dir(vis.scene.window) reveals 335 instancemethods and 82 other
>     objects.
>     I do have a few questions that are not currently addressed by the
>     documentation.
>
>     The main one is:
>         How do I make new window Menu objects?
>         Does Vpython use TCL? or do I have to learn wxPython
>     methodologies?
>          Is it possible to make Buttons, Sliders, List Boxes or even
>     Window Panes from WITHIN Visual?
>
>     I hope the Documentation will eventually address these topics in
>     detail.
>
>     The Only 'error' I have found is this.
>     There is this anomalous error report when I am in V-IDLE shell and
>     I break program with 'ctrl-c'.
>
>     Traceback (most recent call last):
>       File "K:\Symion_12_12_12\visdemo.py", line 6
>         import vis
>       File "C:\Python27\lib\site-packages\vis\__init__.py", line 17
>       File "C:\Python27\Lib\site-packages\visual_common\rate_plan.py",
>     line 122, in __call__
>         sleep(desiredLoopTime - currTime)
>     TypeError: 'int' object is not callable
>
>     Hope this means something to you...
>
>     Finally, it is really good to see The Project evolving.
>
>     Symion
>
>
>
>     On 27/12/2012 4:59 AM, Bruce Sherwood wrote:
>>     Now available on the Windows download page at vpython.org
>>     <http://vpython.org> is a 32-bit version of the experimental
>>     VPython that's based on wxPython.
>>
>>     Bruce Sherwood
>>
>>
>>     _______________________________________________
>>     Visualpython-users mailing list
>>     Vis...@li...  <mailto:Vis...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/visualpython-users
>     _______________________________________________
>     Visualpython-users mailing list
>     Vis...@li...
>     <mailto:Vis...@li...>
>     https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>

Re: [Visualpython-users] Experimental 64-bit VPython for Windows based on wxPython

[Bruce S. <Bru...@nc...>]

Thanks much for the report, including the bug report.

It is intended to open up VPython to make it possible to add buttons,
sliders, etc., using the capabilities of wxPython (not Tcl). The first task
was simply (well, not so simply) to replicate existing VPython
capabilities. Currently, when you create a display object, that's a
composite in the sense that it creates a window and also creates an OpenGL
canvas that fills that window. Presumably what is needed is a window object
that creates a window, and a canvas object that creates an OpenGL canvas
somewhere in that window, in which case you could then add other widgets to
the window. That would leave the display object as a convenience object,
useful for many ordinary programs.

Bruce Sherwood


On Wed, Jan 9, 2013 at 10:03 PM, Symion <kn...@ip...> wrote:

>  This is wonderful!!
> I now have Visual Python with a MENU item 'Files', running on Windows XP!
> ALL examples have been run without error and everything seems very stable.
>
> Specifically I am using:
>     Vpython ('6.00', 'release') running with Python 2.7.3 on Windows XP
>
> Of course this  raises lots of questions...
>
> Although 'help(vis)' provides much information and dir(vis.scene.window)
> reveals 335 instancemethods and 82 other objects.
> I do have a few questions that are not currently addressed by the
> documentation.
>
> The main one is:
>     How do I make new window Menu objects?
>     Does Vpython use TCL? or do I have to learn wxPython methodologies?
>      Is it possible to make Buttons, Sliders, List Boxes or even Window
> Panes from WITHIN Visual?
>
> I hope the Documentation will eventually address these topics in detail.
>
> The Only 'error' I have found is this.
> There is this anomalous error report when I am in V-IDLE shell and I break
> program with 'ctrl-c'.
>
> Traceback (most recent call last):
>   File "K:\Symion_12_12_12\visdemo.py", line 6
>     import vis
>   File "C:\Python27\lib\site-packages\vis\__init__.py", line 17
>   File "C:\Python27\Lib\site-packages\visual_common\rate_plan.py", line
> 122, in __call__
>     sleep(desiredLoopTime - currTime)
> TypeError: 'int' object is not callable
>
> Hope this means something to you...
>
> Finally, it is really good to see The Project evolving.
>
> Symion
>
>
>
> On 27/12/2012 4:59 AM, Bruce Sherwood wrote:
>
> Now available on the Windows download page at vpython.org is a 32-bit
> version of the experimental VPython that's based on wxPython.
>
>  Bruce Sherwood
>
>
> ------------------------------------------------------------------------------
> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
> and much more. Keep your Java skills current with LearnJavaNow -
> 200+ hours of step-by-step video tutorials by Java experts.
> SALE $49.99 this month only -- learn more at:http://p.sf.net/sfu/learnmore_122612
>
>
>
> _______________________________________________
> Visualpython-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>

Re: [Visualpython-users] Experimental 64-bit VPython for Windows based on wxPython

[Symion <kn...@ip...>]

This is wonderful!!
I now have Visual Python with a MENU item 'Files', running on Windows XP!
ALL examples have been run without error and everything seems very stable.

Specifically I am using:
     Vpython ('6.00', 'release') running with Python 2.7.3 on Windows XP

Of course this  raises lots of questions...

Although 'help(vis)' provides much information and dir(vis.scene.window) 
reveals 335 instancemethods and 82 other objects.
I do have a few questions that are not currently addressed by the 
documentation.

The main one is:
     How do I make new window Menu objects?
     Does Vpython use TCL? or do I have to learn wxPython methodologies?
      Is it possible to make Buttons, Sliders, List Boxes or even Window 
Panes from WITHIN Visual?

I hope the Documentation will eventually address these topics in detail.

The Only 'error' I have found is this.
There is this anomalous error report when I am in V-IDLE shell and I 
break program with 'ctrl-c'.

Traceback (most recent call last):
   File "K:\Symion_12_12_12\visdemo.py", line 6
     import vis
   File "C:\Python27\lib\site-packages\vis\__init__.py", line 17
   File "C:\Python27\Lib\site-packages\visual_common\rate_plan.py", line 
122, in __call__
     sleep(desiredLoopTime - currTime)
TypeError: 'int' object is not callable

Hope this means something to you...

Finally, it is really good to see The Project evolving.

Symion


On 27/12/2012 4:59 AM, Bruce Sherwood wrote:
> Now available on the Windows download page at vpython.org 
> <http://vpython.org> is a 32-bit version of the experimental VPython 
> that's based on wxPython.
>
> Bruce Sherwood
>
>
> ------------------------------------------------------------------------------
> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
> and much more. Keep your Java skills current with LearnJavaNow -
> 200+ hours of step-by-step video tutorials by Java experts.
> SALE $49.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122612
>
>
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

[Visualpython-users] (no subject)

[sufyan f. <sis...@ya...>]

http://skyspark.net/wp-admin/wmnhl.php?owmi=owmi

Re: [Visualpython-users] issues with rotations

[CATIA <ca...@un...>]

Hi,

use origin instead of pos!
Hans

from visual import *
from time import sleep

#create a set of axes for a visual reference when rotating
xaxis=cylinder(pos=(0,0,0), axis=(5,0,0), color=(1,0,0), radius=0.2)
yaxis=cylinder(pos=(0,0,0), axis=(0,5,0), color=(0,1,0), radius=0.2)
zaxis=cylinder(pos=(0,0,0), axis=(0,0,5), color=(0,0,1), radius=0.2)

#create the ball to be rotated
ball = sphere(pos=(2,2,0), radius = 0.5)

#set rotation angle for 1/20 of a rotation
rotationAngle = 6.28/20.0

#have the ball rotate about the x-axis while
#maintaining 2 units from the xy-plane

#allows viewing and zooming before the start of the loop
s = input("type number to start:")

for i in range(20):
     ball.rotate(angle=rotationAngle, origin=(2,0,0), axis=(1,0,0))
     sleep(0.2)







Am 28.12.2012 14:55, schrieb Zittlow, Mike:
> I wrote a little program to get an understanding of the rotation of 
> objects and have not been able to get things to work as I would like. 
> I cannot get objects rotate about their centers. Believe is some code 
> where I am trying to get a sphere to rotate about the x-axis while 
> maintaining a 2 unit distance from the yz-plane.
>
>
> Any assistance would be greatly appreciated.
>
> from visual import *
> from time import sleep
>
> #create a set of axes for a visual reference when rotating
> xaxis=cylinder(pos=(0,0,0), axis=(5,0,0), color=(1,0,0), radius=0.2)
> yaxis=cylinder(pos=(0,0,0), axis=(0,5,0), color=(0,1,0), radius=0.2)
> zaxis=cylinder(pos=(0,0,0), axis=(0,0,5), color=(0,0,1), radius=0.2)
>
> #create the ball to be rotated
> ball = sphere(pos=(2,2,0), radius = 0.5)
>
> #set rotation angle for 1/20 of a rotation
> rotationAngle = 6.28/20.0
>
> #have the ball rotate about the x-axis while
> #maintaining 2 units from the xy-plane
>
> for i in range(20):
> ball.rotate(angle=rotationAngle, pos=(2,0,0), axis=(1,0,0))
>     sleep(0.2)
> thanks again,
>
> Mike
>
> -- 
> Michael Zittlow
> Mathematics Department Chairperson
> Southern Door High School
> Brussels, WI 54204
>
>
> ------------------------------------------------------------------------------
> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
> much more. Get web development skills now with LearnDevNow -
> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122812
>
>
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] issues with rotations

[Bruce S. <Bru...@nc...>]

Your ball is rotating about the default origin, which is the ball's pos.
Change your rotate statement to say origin=(2,0,0) instead of pos=(2,0,0).

It's better form to say rate(5) rather than sleep, for subtle reasons.

Bruce Sherwood


On Fri, Dec 28, 2012 at 6:55 AM, Zittlow, Mike <
mzi...@so...> wrote:

> I wrote a little program to get an understanding of the rotation of
> objects and have not been able to get things to work as I would like. I
> cannot get objects rotate about their centers. Believe is some code where I
> am trying to get a sphere to rotate about the x-axis while maintaining a 2
> unit distance from the yz-plane.
>
>
> Any assistance would be greatly appreciated.
>
> from visual import *
> from time import sleep
>
> #create a set of axes for a visual reference when rotating
> xaxis=cylinder(pos=(0,0,0), axis=(5,0,0), color=(1,0,0), radius=0.2)
> yaxis=cylinder(pos=(0,0,0), axis=(0,5,0), color=(0,1,0), radius=0.2)
> zaxis=cylinder(pos=(0,0,0), axis=(0,0,5), color=(0,0,1), radius=0.2)
>
> #create the ball to be rotated
> ball = sphere(pos=(2,2,0), radius = 0.5)
>
> #set rotation angle for 1/20 of a rotation
> rotationAngle = 6.28/20.0
>
> #have the ball rotate about the x-axis while
> #maintaining 2 units from the xy-plane
>
> for i in range(20):
>     ball.rotate(angle=rotationAngle, pos=(2,0,0), axis=(1,0,0))
>     sleep(0.2)
>
> thanks again,
>
> Mike
>
> --
> Michael Zittlow
> Mathematics Department Chairperson
> Southern Door High School
> Brussels, WI 54204
>
>
> ------------------------------------------------------------------------------
> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
> much more. Get web development skills now with LearnDevNow -
> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122812
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>

[Visualpython-users] issues with rotations

[Zittlow, M. <mzi...@so...>]

I wrote a little program to get an understanding of the rotation of objects
and have not been able to get things to work as I would like. I cannot get
objects rotate about their centers. Believe is some code where I am trying
to get a sphere to rotate about the x-axis while maintaining a 2 unit
distance from the yz-plane.


Any assistance would be greatly appreciated.

from visual import *
from time import sleep

#create a set of axes for a visual reference when rotating
xaxis=cylinder(pos=(0,0,0), axis=(5,0,0), color=(1,0,0), radius=0.2)
yaxis=cylinder(pos=(0,0,0), axis=(0,5,0), color=(0,1,0), radius=0.2)
zaxis=cylinder(pos=(0,0,0), axis=(0,0,5), color=(0,0,1), radius=0.2)

#create the ball to be rotated
ball = sphere(pos=(2,2,0), radius = 0.5)

#set rotation angle for 1/20 of a rotation
rotationAngle = 6.28/20.0

#have the ball rotate about the x-axis while
#maintaining 2 units from the xy-plane

for i in range(20):
    ball.rotate(angle=rotationAngle, pos=(2,0,0), axis=(1,0,0))
    sleep(0.2)

thanks again,

Mike

-- 
Michael Zittlow
Mathematics Department Chairperson
Southern Door High School
Brussels, WI 54204

Re: [Visualpython-users] Experimental 64-bit VPython for Windows based on wxPython

[Bruce S. <Bru...@nc...>]

Now available on the Windows download page at vpython.org is a 32-bit
version of the experimental VPython that's based on wxPython.

Bruce Sherwood

Re: [Visualpython-users] Experimental 64-bit VPython for Windows based on wxPython

[Bruce S. <Bru...@nc...>]

In response to a question, I expect to build a version for 32-bit Python.

Bruce Sherwood


On Tue, Dec 25, 2012 at 11:45 PM, Bruce Sherwood <Bru...@nc...>wrote:

> On the Windows download page at vpython.org is an experimental VPython
> based on the cross-platform library wxPython. It requires the 64-bit
> version of Python 2.7 (link provided).
>
> This experimental version differs from the older VPython (5.74 and before)
> by eliminating nearly all platform-dependent code and by eliminating the
> threading associated with rendering. This makes it possible for the first
> time to run on 64-bit Python on the Mac and will simplify maintenance and
> further development of VPython. It is also likely to make possible adding
> standard buttons, menus, etc. to a window that contains a VPython scene.
>
> The new version makes one essential change to the syntax of VPython
> programs. Now, an animation loop MUST contain a rate statement, which
> limits the number of loop iterations per second as before but also when
> appropriate (about 30 times per second) updates the 3D scene and handles
> mouse and keyboard events. Without a rate statement, the scene will not be
> updated until and unless the loop is completed.
>
> The heart of the user-interface code (creating windows and handling
> events) is the file site-packages/visual_common/create_display.py. It is
> imported by visual/__init__.py and by /vis/__init__.py; the difference is
> that for convenience visual imports math and numpy, whereas vis doesn't.
>
> Please report issues to the Github repository
> https://github.com/BruceSherwood/vpython-wx, or to the VPython mailing
> list.
>
> Steve Spicklemire is developing simplified installers for all platforms,
> including Mac and Linux, which should be available in the near future. I've
> posted a Windows installer using older tools, to offer people an early look
> at the new VPython. A Python 3 version of wxPython has not yet been
> released, so we can't yet produce a Python 3 version of VPython based on
> wxPython.
>
> Bruce Sherwood
>

[Visualpython-users] Experimental 64-bit VPython for Windows based on wxPython

[Bruce S. <Bru...@nc...>]

On the Windows download page at vpython.org is an experimental VPython
based on the cross-platform library wxPython. It requires the 64-bit
version of Python 2.7 (link provided).

This experimental version differs from the older VPython (5.74 and before)
by eliminating nearly all platform-dependent code and by eliminating the
threading associated with rendering. This makes it possible for the first
time to run on 64-bit Python on the Mac and will simplify maintenance and
further development of VPython. It is also likely to make possible adding
standard buttons, menus, etc. to a window that contains a VPython scene.

The new version makes one essential change to the syntax of VPython
programs. Now, an animation loop MUST contain a rate statement, which
limits the number of loop iterations per second as before but also when
appropriate (about 30 times per second) updates the 3D scene and handles
mouse and keyboard events. Without a rate statement, the scene will not be
updated until and unless the loop is completed.

The heart of the user-interface code (creating windows and handling events)
is the file site-packages/visual_common/create_display.py. It is imported
by visual/__init__.py and by /vis/__init__.py; the difference is that for
convenience visual imports math and numpy, whereas vis doesn't.

Please report issues to the Github repository
https://github.com/BruceSherwood/vpython-wx, or to the VPython mailing list.

Steve Spicklemire is developing simplified installers for all platforms,
including Mac and Linux, which should be available in the near future. I've
posted a Windows installer using older tools, to offer people an early look
at the new VPython. A Python 3 version of wxPython has not yet been
released, so we can't yet produce a Python 3 version of VPython based on
wxPython.

Bruce Sherwood

Re: [Visualpython-users] An important VPython-wx milestone

[Kevin K. <ka...@so...>]

Bruce Sherwood <Bru...@nc...> wrote to kmi...@gm..., vis...@li...:
 > Yes, a compiler is easily obtainable for the Mac, but that's not the point.
 > Most users won't want to be bothered with this and will want to have binary
 > installers. Of course there's no problem for developers or others with a
 > technical bent.

I strongly agree that if you want Vpython to be used, it must have a
standard binary installer on Mac and Windows systems.  If it is not
worth the effort for one person to build a proper binary installer,
then it isn't worth the effort for 100s of people to install all the
dependencies and compile it themselves.

(I've gotten very irked with the gnuplot community for having a
project that is damn near uninstallable on Macs---they expect people
to build a complete Linux shadow OS in order to install gnuplot.)

Re: [Visualpython-users] An important VPython-wx milestone

[Bruce S. <Bru...@nc...>]

Yes, a compiler is easily obtainable for the Mac, but that's not the point.
Most users won't want to be bothered with this and will want to have binary
installers. Of course there's no problem for developers or others with a
technical bent.

Bruce Sherwood


On Fri, Dec 21, 2012 at 9:44 PM, K.-Michael Aye <kmi...@gm...>wrote:

>
>
> On Dec 21, 2012, at 20:08, Bruce Sherwood <Bru...@nc...> wrote:
>
> The mistake I made is so arcane as to be of little value to others. I used
> DrawText to create an RGB bitmap to be used as a texture on an OpenGL quad
> in C++ to form the label object. Part of the bitmap is background pixels
> which by C++ program will be assigned opacity values of 0 to let the
> background quad show through. For subtle antialiasing issues in the
> preparation of the bitmap I used not the label background color but a color
> very similar to the foreground color. This led to a spreading of the text
> strokes which uglified the text. The cure was simply to use the label
> background color as the background color in the preparation of the bitmap
> using DrawText, an approach I had tried early on but abandoned when I ran
> into difficulties, difficulties that later were removed by other
> developments. Sorry you asked?
>
> I guess we should do the experiment of using the github machinery for the
> reporting of bugs. I encourage everyone to wait a short time before trying
> VPython-wx because Steve Spicklemire is in the process of finalizing the
> machinery for creating easy-to-use installers.
>
>
> Oh, I wanted to comment on that: Xcode is still freely available via App
> Store and with it come the compilers that should be able to build
> everything. So I'm not sure the requirement of building complete binary
> installers for Mac is really THAT stringent? Alternatively the 'brew'
> system delivers a lot of command line tools without much hassle so maybe I
> should give it a go with a trial of compilations?
>
> Michael
>
> Bruce Sherwood
>
>
> On Fri, Dec 21, 2012 at 8:18 PM, K.-Michael Aye <kmi...@gm...>wrote:
>
>> Could you briefly describe the mistake you made, so that we learn
>> something about what can go wrong with wxpython?
>>
>> Happy holidays!
>>
>> PS.: As I am a Mac user, I offer to test the stuff on my Mac, shall I
>> report via github issues or here in the mailing list?
>>
>>
>> On Dec 21, 2012, w52, at 7:12 PM, Bruce Sherwood <Bru...@nc...>
>> wrote:
>>
>> > Now fixed. As has happened a number of times in the past, someone in
>> the wxPython community immediately pointed out the (dumb) mistake I'd made.
>> The label fonts now look fine, and there are no major errors visible in the
>> standard demo suite.
>> >
>> > Bruce Sherwood
>> >
>> > On Fri, Dec 21, 2012 at 10:52 AM, Bruce Sherwood <
>> Bru...@nc...> wrote:
>> > The wxPython fonts look quite ugly in label objects, and I've asked the
>> wxPython community about this. I hope they'll tell me that I'm doing
>> something wrong.
>> >
>> >
>> ------------------------------------------------------------------------------
>> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> > Remotely access PCs and mobile devices and provide instant support
>> > Improve your efficiency, and focus on delivering more value-add services
>> > Discover what IT Professionals Know. Rescue delivers
>> >
>> http://p.sf.net/sfu/logmein_12329d2d_______________________________________________
>> > Visualpython-users mailing list
>> > Vis...@li...
>> > https://lists.sourceforge.net/lists/listinfo/visualpython-users
>>
>>
>