Menu
▾
▴
visualpython-users
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(15) |
Oct
(32) |
Nov
(35) |
Dec
(48) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(46) |
Feb
(22) |
Mar
(65) |
Apr
(49) |
May
(22) |
Jun
(29) |
Jul
(51) |
Aug
(34) |
Sep
(32) |
Oct
(46) |
Nov
(30) |
Dec
(32) |
| 2002 |
Jan
(48) |
Feb
(4) |
Mar
(20) |
Apr
(28) |
May
(13) |
Jun
(34) |
Jul
(51) |
Aug
(15) |
Sep
(15) |
Oct
(35) |
Nov
(15) |
Dec
(20) |
| 2003 |
Jan
(31) |
Feb
(111) |
Mar
(41) |
Apr
(28) |
May
(36) |
Jun
(29) |
Jul
(27) |
Aug
(29) |
Sep
(47) |
Oct
(28) |
Nov
(7) |
Dec
(26) |
| 2004 |
Jan
(44) |
Feb
(9) |
Mar
(17) |
Apr
(26) |
May
(58) |
Jun
(13) |
Jul
(44) |
Aug
(64) |
Sep
(30) |
Oct
(11) |
Nov
(21) |
Dec
(28) |
| 2005 |
Jan
(29) |
Feb
(11) |
Mar
(11) |
Apr
(22) |
May
(85) |
Jun
(46) |
Jul
(17) |
Aug
(18) |
Sep
(14) |
Oct
(22) |
Nov
(1) |
Dec
(45) |
| 2006 |
Jan
(20) |
Feb
(36) |
Mar
(18) |
Apr
(24) |
May
(21) |
Jun
(48) |
Jul
(23) |
Aug
(20) |
Sep
(10) |
Oct
(41) |
Nov
(46) |
Dec
(40) |
| 2007 |
Jan
(40) |
Feb
(20) |
Mar
(13) |
Apr
(6) |
May
(24) |
Jun
(31) |
Jul
(30) |
Aug
(11) |
Sep
(11) |
Oct
(10) |
Nov
(56) |
Dec
(64) |
| 2008 |
Jan
(64) |
Feb
(22) |
Mar
(63) |
Apr
(28) |
May
(25) |
Jun
(36) |
Jul
(11) |
Aug
(9) |
Sep
(14) |
Oct
(41) |
Nov
(46) |
Dec
(130) |
| 2009 |
Jan
(95) |
Feb
(41) |
Mar
(24) |
Apr
(35) |
May
(53) |
Jun
(67) |
Jul
(48) |
Aug
(48) |
Sep
(86) |
Oct
(75) |
Nov
(64) |
Dec
(52) |
| 2010 |
Jan
(57) |
Feb
(31) |
Mar
(28) |
Apr
(40) |
May
(25) |
Jun
(42) |
Jul
(79) |
Aug
(31) |
Sep
(49) |
Oct
(66) |
Nov
(38) |
Dec
(25) |
| 2011 |
Jan
(29) |
Feb
(18) |
Mar
(44) |
Apr
(6) |
May
(28) |
Jun
(31) |
Jul
(36) |
Aug
(24) |
Sep
(30) |
Oct
(23) |
Nov
(21) |
Dec
(27) |
| 2012 |
Jan
(14) |
Feb
(11) |
Mar
(2) |
Apr
(48) |
May
(7) |
Jun
(32) |
Jul
(22) |
Aug
(25) |
Sep
(31) |
Oct
(32) |
Nov
(21) |
Dec
(17) |
| 2013 |
Jan
(44) |
Feb
(27) |
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(4) |
Sep
(1) |
Oct
(7) |
Nov
(5) |
Dec
(5) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(2) |
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: David A. <dm...@an...> - 2001-06-21 10:55:21
|
I'm trying to move from Metrowerks Codewarrior 5.3 with Python 2.0 to CodeWarrior 6.2 and Python 2.1. At the moment, the "label" object isn't working, I'm trying to figure out why. |
|
From: Kirby U. <pd...@te...> - 2001-06-21 03:36:37
|
At 08:27 PM 6/20/2001 -0700, Kirby Urner wrote: >>P.S. We have just released VPython for Python 2.1 on Windows: >> >> http://cil.andrew.cmu.edu/projects/visual >> >>This new release installs Scherer's IDLE in Tools/idle_VPython, leaving >>the standard IDLE in place. Desktop and start-menu icons are added that >>access the VPython version of IDLE. > > >Excellent!! > >I'm gonna grab mine now. > >Cheers, > >Kirby Took only seconds to grab and install. Works like a charm. Arthur, your PyGeo package is running way smoother now that I have an official VPython 2.1. Pascal3d is trouble free -- was something of a mess earlier. This is great! Kirby |
|
From: Kirby U. <pd...@te...> - 2001-06-21 03:28:40
|
> >P.S. We have just released VPython for Python 2.1 on Windows: > > http://cil.andrew.cmu.edu/projects/visual > >This new release installs Scherer's IDLE in Tools/idle_VPython, leaving >the standard IDLE in place. Desktop and start-menu icons are added that >access the VPython version of IDLE. Excellent!! I'm gonna grab mine now. Cheers, Kirby |
|
From: Bruce S. <ba...@an...> - 2001-06-20 23:29:52
|
Concerning VPython and IDLE: At the same time that he created the Visual module, which provides remarkably easy 3D animated graphics for Python (Visual + Python = VPython), David Scherer made major changes to IDLE, including: executes scripts in a separate process for stability excludes system modules from tracebacks usability changes, including reorganized menus autosave on every run, with infinite un-do scrolling output has a header marking the start of each run This has turned out to be an ideal environment for novices (as measured by use by a large number of physics students), and is also an excellent rapid edit-run environment for experts. Alas, there is no active work on this at present, because Scherer is not currently in a situation where he can spend time on this, and we have no one else in the project currently capable of pushing this forward. It is certainly the case that Scherer's version of IDLE is an exceptionally promising candidate to become the "official" IDLE, but unfortunately we are not able to lead the charge right now. Bruce Sherwood P.S. We have just released VPython for Python 2.1 on Windows: http://cil.andrew.cmu.edu/projects/visual This new release installs Scherer's IDLE in Tools/idle_VPython, leaving the standard IDLE in place. Desktop and start-menu icons are added that access the VPython version of IDLE. |
|
From: Dethe E. <de...@al...> - 2001-06-20 23:15:29
|
>> That's great! Any ETA for the Mac version? > > David Andersen has VPython partially working on the Mac, but there are > problems. No estimate possible yet. In going from Python 2.0 to Python 2.1 > on the Mac, there was a change of compilers, which has made the upgrade > additionally difficult. That's interesting. What compilers are you switching to/from? -- Dethe Elza Chief Mad Scientist Burning Tiger Technologies |
|
From: Bruce S. <ba...@an...> - 2001-06-20 23:10:55
|
--On Wednesday, June 20, 2001 15:38 -0700 Dethe Elza <de...@al...> wrote: > That's great! Any ETA for the Mac version? David Andersen has VPython partially working on the Mac, but there are problems. No estimate possible yet. In going from Python 2.0 to Python 2.1 on the Mac, there was a change of compilers, which has made the upgrade additionally difficult. Bruce Sherwood |
|
From: Dethe E. <de...@al...> - 2001-06-20 22:38:49
|
That's great! Any ETA for the Mac version? --Dethe on 01/6/20 02:55 PM, Bruce Sherwood at ba...@an... wrote: > At http://cil.andrew.cmu.edu/projects/visual you can now download VPython > for Python 2.1 on Windows. > > Paul Dubois and Dave Scherer diagnosed the problem we were having with > Python 2.1, and David Andersen recompiled. Thanks, guys. > > The new package no longer overwrites the standard IDLE but creates another > folder Tools/idle_VPython and shortcuts on the desktop and the start menu > that point to it. Users also have access to the standard IDLE from the > start menu. > > There is a new demo program, doublependulum.py, which shows chaotic motion > in a simple system. > > The minor source changes to Visual have not yet been checked in to > sourceforge. They consist essentially of replacing tests such as "a == > None" with "a is None". Python 2.1 introduced "rich comparisons" to satisfy > users of Numeric who wanted to do more than test whether one array was > equal to another. They wanted instead to be able to get an array of true > and false results for element-by-element comparisons. They also wanted to > be able to do other comparisons (<, >, etc.). This had a side effect which > made "a == None" illegal if a is a Numeric array > > Bruce Sherwood > > > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > http://lists.sourceforge.net/lists/listinfo/visualpython-users > -- Dethe Elza Chief Mad Scientist Burning Tiger Technologies |
|
From: Bruce S. <ba...@an...> - 2001-06-20 21:56:47
|
At http://cil.andrew.cmu.edu/projects/visual you can now download VPython for Python 2.1 on Windows. Paul Dubois and Dave Scherer diagnosed the problem we were having with Python 2.1, and David Andersen recompiled. Thanks, guys. The new package no longer overwrites the standard IDLE but creates another folder Tools/idle_VPython and shortcuts on the desktop and the start menu that point to it. Users also have access to the standard IDLE from the start menu. There is a new demo program, doublependulum.py, which shows chaotic motion in a simple system. The minor source changes to Visual have not yet been checked in to sourceforge. They consist essentially of replacing tests such as "a == None" with "a is None". Python 2.1 introduced "rich comparisons" to satisfy users of Numeric who wanted to do more than test whether one array was equal to another. They wanted instead to be able to get an array of true and false results for element-by-element comparisons. They also wanted to be able to do other comparisons (<, >, etc.). This had a side effect which made "a == None" illegal if a is a Numeric array Bruce Sherwood |
|
From: Patrick K. O'B. <po...@or...> - 2001-06-20 21:42:11
|
Except that the VPython folks have a design goal that is quite tangential to IDLE's. They need a tool to support their visual python modules (which allow the manipulation of 3D objects and should not to be confused with ActiveState's IDE) and the teaching of physics. While I do think their needs should be accomodated, I don't know that they would want to be responsible for IDLE development as a whole. (But I could be wrong.) I've added them to the recipients of this message. We'll see if they respond. (The vpython list has been quiet lately.) --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: tut...@py... [mailto:tut...@py...]On Behalf Of Dethe Elza Sent: Wednesday, June 20, 2001 3:20 PM To: IDLE Developers List Cc: Python Edu SIG; Python Tutor Subject: [Tutor] Re: [Edu-sig] RE: [Idle-dev] IDLE "deemphasised"? Please not so... That's great news! Are the VPython folks listening? --Dethe on 01/6/20 11:06 AM, Guido van Rossum at gu...@di... wrote: >> It seems to me that the VPython folk are the perfect ones to pick up the >> IDLE development reins. They're actively working on IDLE already, have >> already implemented the autosave mentioned, as well as some others, and >> generally seem willing and interested. I'm not sure what the reasoning is >> for keeping the VPython IDLE off in its own fork and not bringing it in as >> the official IDLE, since it is being actively developed. > > I think it was that I wanted to keep control over the direction in > which IDLE was going. The idle-fork SourceForge project was created > so they could do their development. But I don't think much happened > there, and I haven't really done much except stifle IDLE development, > so I'm ready to relax my control. I do have that subprocess-running > code which I would like to get worked into IDLE first though... > > --Guido van Rossum (home page: http://www.python.org/~guido/) > > -- Dethe Elza Chief Mad Scientist Burning Tiger Technologies _______________________________________________ Tutor maillist - Tu...@py... http://mail.python.org/mailman/listinfo/tutor |
|
From: Rafael G. <rag...@ya...> - 2001-06-15 22:37:00
|
Hi: Im currently developing a speech recognition software, and I would like to add some sort of videos, for the learning purpose I think it can be done with Visual Python, but when I tried to install if from the RPM, I get a dependency problem, but I do not know how to solve it, so if anyone can help me I´ll appreciate it, by the way I´m using Linux Mandrake 7.0. Thanks in advance Luis Galvan __________________________________________________ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/ |
|
From: Radha K. <drr...@ho...> - 2001-06-11 23:47:50
|
<html><DIV><FONT size=6>Dear Colleagues,</FONT></DIV> <DIV><FONT size=6>I have downloaded the .exe versions of Python and Visualpython as indicated and installed them on Windows Me.</FONT></DIV> <DIV><FONT size=6>On starting a typical demo using Idle, the run command produces the error msg " visual not found" The visual module is apparently not available. Please let me know how to install this module etc, so that the demos might work.</FONT></DIV> <DIV><FONT size=6>The program VPython, in Konrad's Hinsen's module Scientific has the same problem on the Linux partition. </FONT></DIV> <DIV><FONT size=6>Thank you for your help.</FONT></DIV> <DIV><FONT size=6>Radha Krishna</FONT></DIV><br clear=all><hr>Get your FREE download of MSN Explorer at <a href="http://explorer.msn.com">http://explorer.msn.com</a><br></p></html> |
|
From: Patrick K. O'B. <po...@or...> - 2001-06-11 23:10:18
|
VPython inherited this same shortcoming. See below for details.
---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."
-----Original Message-----
From: idl...@py... [mailto:idl...@py...]On Behalf
Of Patrick K. O'Brien
Sent: Monday, June 11, 2001 5:33 PM
To: IDLE Developers List
Subject: [Idle-dev] Why are keybindings case sensitive?
Or rather, why aren't any of the keybindings (especially cut, copy and
paste) setup to work when one has caps lock on? I fixed this in my version
of keydefs.py but this seems like something that IDLE should do by default.
Here is the change I made, adding uppercase keybindings. It appears to work
fine.
windows_keydefs = \
{'<<Copy>>': ['<Control-c>', '<Control-C>'],
'<<Cut>>': ['<Control-x>', '<Control-X>'],
'<<Paste>>': ['<Control-v>', '<Control-V>'],
---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."
_______________________________________________
IDLE-dev mailing list
IDL...@py...
http://mail.python.org/mailman/listinfo/idle-dev
|
|
From: Patrick K. O'B. <po...@or...> - 2001-06-11 17:47:18
|
I can't guarantee that this will work with vpython for what you want to do, but pyGame is probably worth a look. It can work with a variety of input devices. Take a look at http://www.pygame.org/. --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: vis...@li... [mailto:vis...@li...]On Behalf Of Gary Strangman Sent: Monday, June 11, 2001 12:06 PM To: vis...@li... Cc: Gary Strangman Subject: [Visualpython-users] Input devices Hello, Sorry if this is a dumb question (and hope this hasn't already been posted--mail firewall issues), but ... I'm brand new to Visual Python (though a long-time Python user), and I was unable to find info on this question in the archives or doc. I'm interested in using VPython for a navigation-in-3D task which requires input devices other than the mouse (esp. joysticks and keyboard). I see that the mouse worked automatically when I ran the little demo program, and the archives suggest that a trackball (i.e., a mouse-alike) works fine too. Is there a way to handle other input devices as well? And if so, how? Cheers, Gary Strangman -------------------------------------------------------------- Gary Strangman, PhD | Neural Systems Group Office: 617-724-0662 | Massachusetts General Hospital Fax: 617-726-4078 | 13th Street, Bldg 149, Room 9103 st...@nm... | Charlestown, MA 02129 http://www.nmr.mgh.harvard.edu/Neural_Systems_Group/gary/ _______________________________________________ Visualpython-users mailing list Vis...@li... http://lists.sourceforge.net/lists/listinfo/visualpython-users |
|
From: Dethe E. <de...@al...> - 2001-06-11 17:18:21
|
Re: Non-mouse control in VPython. One of the examples that comes with VPython uses a regular Tkinter window to control the VPython scene, so if you go that route you have all the normal GUI input methods at your disposal. -- Dethe Elza Chief Mad Scientist Burning Tiger Technologies |
|
From: Gary S. <st...@nm...> - 2001-06-11 17:06:05
|
Hello, Sorry if this is a dumb question (and hope this hasn't already been posted--mail firewall issues), but ... I'm brand new to Visual Python (though a long-time Python user), and I was unable to find info on this question in the archives or doc. I'm interested in using VPython for a navigation-in-3D task which requires input devices other than the mouse (esp. joysticks and keyboard). I see that the mouse worked automatically when I ran the little demo program, and the archives suggest that a trackball (i.e., a mouse-alike) works fine too. Is there a way to handle other input devices as well? And if so, how? Cheers, Gary Strangman -------------------------------------------------------------- Gary Strangman, PhD | Neural Systems Group Office: 617-724-0662 | Massachusetts General Hospital Fax: 617-726-4078 | 13th Street, Bldg 149, Room 9103 st...@nm... | Charlestown, MA 02129 http://www.nmr.mgh.harvard.edu/Neural_Systems_Group/gary/ |
|
From: Arne K. <arn...@pp...> - 2001-06-11 09:18:01
|
I have the following problem with hasattr() on visual object: when I execute this simple code: ----------------------------------------------- #file Vtest.py from visual import * thecone = cone(pos=(-3,-2,-2),axis = (0,3,0),radius=2.5, color=color.yellow) thecone.attr_exists = 'test' print 'yes', hasattr(thecone,'attr_exists') print 'no', hasattr(thecone,'attr_no_exists') ----------------------------------------------- it returns: ------------------------------------------------ arne@requin:~/python/Vpython > python Vtest.py Visual-2001-02-20 yes 1 segmentation fault --------------------------------------------------- I have installed Vpython from the cvs on Linux 2.2.18 (suse 7.1 distribution) under python2.0. -- Arne Keller Laboratoire de Photophysique Moleculaire du CNRS, Bat. 213. Universite de Paris-Sud, 91405 Orsay Cedex, France. tel.: (33) 1 69 15 82 83 -- fax. : (33) 1 69 15 67 77 |
|
From: Bruce S. <ba...@an...> - 2001-06-10 04:08:30
|
Dave Scherer discovered the change in Python 2.1 that made Visual fail. It is no longer legal to do the direct comparison "numeric_array == None". Instead, you now have to do essentially "value.is(Nothing())" instead of "value == Nothing()". We'll make these changes and then be able to move up to Python 2.1 Bruce Sherwood |
|
From: Bruce S. <ba...@an...> - 2001-06-09 01:13:55
|
Can anyone give us advice on what changes there were in going from Python
2.0 to Python 2.1 that could lead to the following problem in Visual?
The following code running on VPython 2.1 for Windows shows that p.color is
a Numeric array, but that it is not possible to assign a Numeric array to
p.color. The problem evidently is in the C++ code for the Visual module,
but in order to understand how to fix it it would be wonderful if someone
happens to know what is changed in Python 2.1 (or Numeric) that would
invalidate the Visual handling of assigning a Numeric array to a Visual
object attribute. The existence of this bug is what is preventing us from
releasing Visual for Python 2.1
Bruce Sherwood
from visual import *
p = convex()
print type(p.color)
c = [.1, .2, .3]
d = array(c)
p.color = d
print p.color
----------------------------------------
<type 'array'>
Traceback (innermost last)
File "Untitled", line 6, in ?
p.color = d
TypeError: function not supported for these types, and can't coerce to
supported types
P.S. Attempting to assign p.color = p.color gives the same error.
|
|
From: Arne K. <arn...@pp...> - 2001-06-07 15:24:04
|
I just install Vpython (I compile it from the cvs) on Linux 2.2.18 (suse
7.1 distribution) under python2.0.
It seems that Vpython work fine.
But I have a problem with povexport.py (from povexport1-1.zip).
It seems that the problem comes from the call to hasattr() in the
add_texture() function in povexport.py.
for testing purpose, I have modified the add_texture function in
povexport.py as:
-------------------------------------------------------
def add_texture(a, code):
# add in user-specified texture (will override color)
print 'in add_texture',a,a.__class__,a.__members__ #added by A.K
if hasattr(a, 'pov_texture'):
print 'yes, has attr pov_texture' #added by A.K.
tstring = ' texture { '+ a.pov_texture + ' }\n'
end = rfind(code, '}')
code = code[:end] + tstring + code[end:]
else:#else block added by A.K.
print 'no, has not attr pov_texture'
return code
-------------------------------------------------
and I excute the following python povsimple.py module:
---------------------------------------------------
#file povsimple.py
from visual import *
import povexport #with the modified add_texture
print 'Instructions: zoom and rotate to get the viewing angle\n\
you want. Click the mouse to generate POV-Ray code.\n'
scene.x=scene.y=0
rod = cylinder(pos=(0,2,1), axis=(5,0,0), radius=1)
rod.color = (0,0,1) # make rod be blue
filename = 'povexample.pov'
scene.mouse.getclick() ## position camera somewhere, then click
code = povexport.export(display=scene)
ff = open(filename, 'w')
ff.write(code)
ff.close()
print 'PovRay code written to ',filename
-----------------------------------------------------------
then the execution of:
python povsimple.py
gives:
-------------------------------------------------
Visual-2001-02-20
Instructions: zoom and rotate to get the viewing angle
you want. Click the mouse to generate POV-Ray code.
in add_texture <Primitive object at 0x818f5c8> cylinder ['axis', 'blue',
'color', 'display', 'frame', 'green', 'length', 'pos', 'radius', 'red',
'up', 'visible', 'x', 'y', 'z']
Erreur de segmentation
------------------------------------------------
thanks for your help
--
Arne Keller
Laboratoire de Photophysique Moleculaire du CNRS, Bat. 213.
Universite de Paris-Sud, 91405 Orsay Cedex, France.
tel.: (33) 1 69 15 82 83 -- fax. : (33) 1 69 15 67 77
|
|
From: Ari H. <ahe...@an...> - 2001-06-04 14:41:18
|
my friend yossi wrote this as a brain exercise before leaving for his summer job with some game company. i thought it was so cool i had to share it here. ari |
|
From: <Art...@ao...> - 2001-05-31 00:30:03
|
>The VPython idle has a very large number of important enhancements which >are of particular importance to novices but useful for others as well: Bruce - FWIW, I don't fully agree. I certainly partially agree. Spawning a separate process is certainly a necessity. And I guess I would further agree that since this issue alone makes standard IDLE unusable as a VPython IDE, and VPython deserves an IDE, you may as well include whatever enhancements/amendments seem sensible for VPython. But much is being sacrificed - because I do think VPython is important - by the current state of separate IDLEs. Confusion on the issue abounds. IDLE is Guido's own, and there is something that bothers people about an install that will overwrite the latest and greatest official IDLE. Do you see the forks re-merging?? If not, why can't VPython's IDLE be distinctively named and re-located to live at peace with IDLE standard edition. Certainly don't think any technical issues will arise. This is only important because I believe VPython has a significant potential audience beyond that for which it was developed at CMU. The IDLE confusion is chronic, and greatly inhibiting VPython's acceptance, IMO. And it all seems quite solvable - so much more the frustration from the view of an interested observer of the situation. ART |
|
From: Patrick K. O'B. <po...@or...> - 2001-05-31 00:21:49
|
I think I have a better understanding of where you are coming from, and I agree that there are two types of users. (I guess I wouldn't have thought physics students would have that much trouble installing and using software, but I believe you.) At the same time, I'm still not ready to give in completely on this issue. Here is why - I think we can find a solution that satisfies the needs of both users. To begin with, I think we need to agree to leave the Python default stuff alone. So Guido gets tools/idle. VPython will need to create its own directory. Let's say it's called tools/vidle or tools/vpython. Nobody is ever really going to care and the students don't even need to know that it got put there. All they need is an icon to click on. So have the installer create an icon in Start | Programs | Python 2.1 that is labeled ... VPython, of course. "Okay, students. Click on Install to install VPython. After that is finished, go to Start | Programs | Python 2.1 and click on VPython to start the VPython tool. If you have any interest in learning how to program in Python, you can select IDLE (Python GUI) to get to the Python interactive mode. But do so on your own time because it isn't relevant to this class. For this class we will only be using VPython." What I have described above is exactly the setup I manually created on my machine. I am on my third day of teaching my fifth grade daughter how to program in Python (and having a blast, let me tell you). When we are doing regular programming I tell her "click on IDLE" and when we are messing around with VPython I tell her "click on VPython." If she can do it I would hope your physics students could also. (Or perhaps they shouldn't be studying physics.) Your thoughts? --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: vis...@li... [mailto:vis...@li...]On Behalf Of Bruce Sherwood Sent: Wednesday, May 30, 2001 5:54 PM To: vis...@li... Cc: gu...@py... Subject: RE: [Visualpython-users] VPython idle There seem to be incompatible needs, which we've run into before in a slightly different context. As in the previous case, I think what is needed is simply better documentation and installers on the VPython web site to explain what's happening, and I'll do that. There are two types of users of VPython with very different needs and expectations. One is the relatively expert programmer who comes to Python from other languages and then after some time comes to VPython. The other is the student (including in our own physics course) who may never have written a computer program before and for whom VPython is their first programming environment. Such a student needs utterly simple installation procedures and completely obvious shortcuts to using VPython productively right away. After much experimentation, we've solved the nontrivial problem of making this work for such users. This includes keeping students out of the interactive mode, which can be a good place for experts but is quite inappropriate for novices. The sophisticated user needs an explanation that this is what we've done, and how to get around it (easily), and that's where we've not done an adequate job. After recovering from a major textbook submission, I'll improve the web site and installers. Bruce Sherwood _______________________________________________ Visualpython-users mailing list Vis...@li... http://lists.sourceforge.net/lists/listinfo/visualpython-users |
|
From: Bruce S. <ba...@an...> - 2001-05-30 22:54:13
|
There seem to be incompatible needs, which we've run into before in a slightly different context. As in the previous case, I think what is needed is simply better documentation and installers on the VPython web site to explain what's happening, and I'll do that. There are two types of users of VPython with very different needs and expectations. One is the relatively expert programmer who comes to Python from other languages and then after some time comes to VPython. The other is the student (including in our own physics course) who may never have written a computer program before and for whom VPython is their first programming environment. Such a student needs utterly simple installation procedures and completely obvious shortcuts to using VPython productively right away. After much experimentation, we've solved the nontrivial problem of making this work for such users. This includes keeping students out of the interactive mode, which can be a good place for experts but is quite inappropriate for novices. The sophisticated user needs an explanation that this is what we've done, and how to get around it (easily), and that's where we've not done an adequate job. After recovering from a major textbook submission, I'll improve the web site and installers. Bruce Sherwood |
|
From: Patrick K. O'B. <po...@or...> - 2001-05-30 21:45:51
|
Bruce, This idea of replacing the default IDLE with the one from VPython strikes me as backwards. And I am baffled by your assertion that the interpretive environment is not suitable for novices. I would think most people would install Python first and start working with it. Then they will discover VPython and install it. I would expect VPython to install itself in its own directory and leave all the existing Python stuff alone. Even if your version of IDLE is a huge improvement, that doesn't seem like a good enough reason to replace the regular IDLE and then leave it up to the user to figure out how to get the regular IDLE working again. I can't think of any reason why VPython couldn't just install into its own folder, such as c:\python21\tools\vidle (on Windows), and add its own *additional* links to the start menu and desktop. I happen to like both versions of IDLE and would like to see them play nicely together. Your approach strikes me as a wee bit adversarial. I'd rather not see it become the standard for VPython. I copied Guido in on this message to give both of you the chance to be involved in this discussion. If either of you think I'm way off base please feel free to enlighten me. Otherwise, please take this message in the spirit of helpfulness in which it is given. --- Patrick K. O'Brien Orbtech "I am, therefore I think." -----Original Message----- From: vis...@li... [mailto:vis...@li...]On Behalf Of Bruce Sherwood Sent: Wednesday, May 30, 2001 9:16 AM To: vis...@li... Subject: [Visualpython-users] VPython idle --On Tuesday, May 29, 2001 14:29 -0500 "Patrick K. O'Brien" <po...@or...> wrote: > Mistakes happen. Thanks for the info. I will reinstall as you suggest. Any > idea what the future folder name will be so that I can manually set my > system up in anticipation of the official procedure? I'm assuming python's > IDLE will continue to go into tools\idle while vpython's version will go > into, what? Tools\vpython? Tools\vidle? I don't know what name to give the "official" idle folder. But for the sake of novice users it is the VPython idle that will go in Tools/idle, so that all the shortcuts will point to it (experts who want the "official" one can of course make a shortcut to it). The VPython idle has a very large number of important enhancements which are of particular importance to novices but useful for others as well: Spawns a separate process, so if anything goes wrong during the run, IDLE stays up. One-button (F5) user interface much better for rapid edit/run cycle. This is particularly important for novices, for whom the interpretative environment is not suitable, but it works very well for experts, too. Infinite undo. Automatically saves file at start of run, so very difficult to lose any work. Rationalized menus. Maintains scrolling output window across runs, scrolling forward on each run, so easy to scroll back to earlier run, which has a header. For Visual programs it is important that upon reaching the end of the program the graphics window should NOT go away but be inspectable while examining code. The VPython Idle and Visual environment conspire to make this work properly. _______________________________________________ Visualpython-users mailing list Vis...@li... http://lists.sourceforge.net/lists/listinfo/visualpython-users |
|
From: Bruce S. <ba...@an...> - 2001-05-30 18:55:57
|
--On Tuesday, May 29, 2001 14:29 -0500 "Patrick K. O'Brien" <po...@or...> wrote: > Mistakes happen. Thanks for the info. I will reinstall as you suggest. Any > idea what the future folder name will be so that I can manually set my > system up in anticipation of the official procedure? I'm assuming python's > IDLE will continue to go into tools\idle while vpython's version will go > into, what? Tools\vpython? Tools\vidle? I don't know what name to give the "official" idle folder. But for the sake of novice users it is the VPython idle that will go in Tools/idle, so that all the shortcuts will point to it (experts who want the "official" one can of course make a shortcut to it). The VPython idle has a very large number of important enhancements which are of particular importance to novices but useful for others as well: Spawns a separate process, so if anything goes wrong during the run, IDLE stays up. One-button (F5) user interface much better for rapid edit/run cycle. This is particularly important for novices, for whom the interpretative environment is not suitable, but it works very well for experts, too. Infinite undo. Automatically saves file at start of run, so very difficult to lose any work. Rationalized menus. Maintains scrolling output window across runs, scrolling forward on each run, so easy to scroll back to earlier run, which has a header. For Visual programs it is important that upon reaching the end of the program the graphics window should NOT go away but be inspectable while examining code. The VPython Idle and Visual environment conspire to make this work properly. |
33 messages has been excluded from this view by a project administrator.
