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 S. <dsc...@vy...> - 2001-03-22 00:58:05
|
> > But then I go back to some of the demos - like Hanoi - that ran > > perfectly nicely when I first installed VPython and find that > > they also are not fully rendering. Get ugly half-rings. > > > > So re-install the cvisual .dll. No help. > > If you are running on Windows, it might be useful to run glinfo.py and > report its output. Also try disabling hardware acceleration (as suggested in the FAQ). Dave |
From: Ari H. <ahe...@an...> - 2001-03-21 21:07:18
|
On Wed, Mar 21, 2001 at 02:03:28PM -0600, Art...@rs... wrote: > > Actually on the plate for the second half of this semester is a bunch of new > > stuff in VPython. Transparency will be tricky to do due to structural issues > > in VPython (transparency in GL requires careful observance of zbuffer and > > render-order rules) but textures should be starting to happen in the next > > couple of weeks. > > What am I missing here on the transparency issue? I am thinking > basic Color4 with the alpha value component set to 1 by default > but with the ability to override the default and toggle on the appropriate > glEnables. Do I not understand something basic about how VPython does > OpenGL or are you referring to a more sophisticated transparency > implementation? > Dave Andersen was talking with Dave Scherer about this on visualpython-devel. The problem is, to get alpha right, you have to make sure you render the scene back-to-front, or the color values in the output buffer won't be correct when you use them to do alpha computations at each stage in the rendering. Unfortunately, the current VPython implementation's scene conception doesn't support this strong ordering on the objects in the scene ... Ari |
From: Bruce S. <ba...@an...> - 2001-03-21 20:18:53
|
--On Wednesday, March 21, 2001 2:11 PM -0600 Art...@rs... wrote: > But then I go back to some of the demos - like Hanoi - that ran > perfectly nicely when I first installed VPython and find that > they also are not fully rendering. Get ugly half-rings. > > So re-install the cvisual .dll. No help. If you are running on Windows, it might be useful to run glinfo.py and report its output. Clearly something has been corrupted on your machine, and evidently it isn't cvisual.dll. Perhaps you should uninstall VPython and Python, then reinstall Python and VPython. If you've saved copies of the installers this doesn't actually take very long. Bruce Sherwood |
From: <Art...@rs...> - 2001-03-21 19:22:11
|
So I'm doing my VPython thing, having a great time. Did I nice wireframe Sphere - but then it won't render completely when I have more than say ten stacks. Thought that an unfortunate limitation of VPython - not a clue why. But then I go back to some of the demos - like Hanoi - that ran perfectly nicely when I first installed VPython and find that they also are not fully rendering. Get ugly half-rings. So re-install the cvisual .dll. No help. Clueless. ART |
From: <Art...@rs...> - 2001-03-21 19:22:10
|
> Actually on the plate for the second half of this semester is a bunch of new > stuff in VPython. Transparency will be tricky to do due to structural issues > in VPython (transparency in GL requires careful observance of zbuffer and > render-order rules) but textures should be starting to happen in the next > couple of weeks. What am I missing here on the transparency issue? I am thinking basic Color4 with the alpha value component set to 1 by default but with the ability to override the default and toggle on the appropriate glEnables. Do I not understand something basic about how VPython does OpenGL or are you referring to a more sophisticated transparency implementation? In which case I would argue for a simple half-way implementation at least as a temporary alternative to full opaqueness, all the time. ART |
From: ruth c. <rc...@an...> - 2001-03-21 18:25:49
|
Thanks to Markus Gritsch there is a new version of povexport.py which fixes some problems and improves some features. povexport1-1.zip can be downloaded from the VPython website. Ruth Chabay |
From: Markus G. <gr...@iu...> - 2001-03-21 17:30:56
|
Ari Heitner wrote: > Clearly we need to add more transparency/soft shadows/reflection support to > the povray export module to slow down all this dangerous, irrationally > exuberant fast rendering. :-) First, implement it in VPython - povexport will continue reproducing VPython features. (Although textures are already there, even before this feature pops up in VPython ;-) Markus |
From: Ari H. <ahe...@an...> - 2001-03-21 17:23:59
|
On Wed, Mar 21, 2001 at 12:05:42PM -0500, ruth chabay wrote: > > > PovRay renderings will of course look nicer if you have the patience for > > them. > > > Huh? I export stuff to PovRay all the time to make figures for a physics > textbook. Rendering is fast -- no patience required. > I think computers got faster when I wasn't looking. ... Clearly we need to add more transparency/soft shadows/reflection support to the povray export module to slow down all this dangerous, irrationally exuberant fast rendering. ari |
From: Markus G. <gr...@iu...> - 2001-03-21 17:17:48
|
Bruce Sherwood wrote: > So really what is needed (I think) is for someone to write a module to go > from a Visual scene (or graph) to Postscript, analogous to what Ruth Chabay > has done for going to PovRay. This might be useful even for 3D scenes if > you don't care about the ray-traced quality obtained from PovRay. For a moment i thought about this, too, but this would be a *LOT* of work if you would like to reproduce the scene exactly, although it would not be impossible. Maybe things would simplify if only 2D is considered, but creating a reasonable PostScript image of a 3D scene is quite complicated (geometry transformation, color shading, ...). Markus |
From: Bruce S. <ba...@an...> - 2001-03-21 17:09:05
|
Going through PovRay makes sense for normal 3D Visual scenes, but doesn't make a lot of sense for the 2D graphs Fortemps is interested in (produced by importing visual.graph). And capturing a screen shot gives you low resolution when you go to print. So really what is needed (I think) is for someone to write a module to go from a Visual scene (or graph) to Postscript, analogous to what Ruth Chabay has done for going to PovRay. This might be useful even for 3D scenes if you don't care about the ray-traced quality obtained from PovRay. VPython is most definitely not built on Tk. The only connection is that Tk underlies IDLE, but not Visual. Bruce --On Wednesday, March 21, 2001 4:31 PM +0100 Fortemps Philippe <Phi...@fp...> wrote: > I really appreciate to use VPython to graph the output of my > programs. How could I send those graphs to a PostScript file ? > > If VPython is built on Tk, how can I reach canvas.postscript ? |
From: ruth c. <rc...@an...> - 2001-03-21 17:06:00
|
--On Wednesday, March 21, 2001 11:34 AM -0500 Ari Heitner <ahe...@an...> wrote: > On Wed, Mar 21, 2001 at 11:03:37AM -0500, David Andersen wrote: >> Exporting to PovRay is the way to go. >> > I would just capture a screenshot and convert that to PostScript. > > PovRay renderings will of course look nicer if you have the patience for > them. > Huh? I export stuff to PovRay all the time to make figures for a physics textbook. Rendering is fast -- no patience required. Ruth > > > ari > > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > http://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Markus G. <gr...@iu...> - 2001-03-21 17:01:04
|
Ari Heitner wrote: > Actually on the plate for the second half of this semester is a bunch of new > stuff in VPython. Transparency will be tricky to do due to structural issues > in VPython (transparency in GL requires careful observance of zbuffer and > render-order rules) but textures should be starting to happen in the next > couple of weeks. Looking forward to it! Markus |
From: Ari H. <ahe...@an...> - 2001-03-21 16:57:31
|
On Wed, Mar 21, 2001 at 05:48:22PM +0100, Markus Gritsch wrote: > Ari Heitner wrote: > > > PovRay renderings will of course look nicer if you have the patience for > > them. > > Well, PovRay rendering takes only a few seconds on my slow P200. Rendering > VPython scenes is quite fast, because most timeconsuming features in > rendering (transparency, reflection, area lights for soft shadows, > radiosity, ...) are not used. > Hm, I guess that's a good point. Actually on the plate for the second half of this semester is a bunch of new stuff in VPython. Transparency will be tricky to do due to structural issues in VPython (transparency in GL requires careful observance of zbuffer and render-order rules) but textures should be starting to happen in the next couple of weeks. Ari |
From: Markus G. <gr...@iu...> - 2001-03-21 16:48:35
|
Ari Heitner wrote: > PovRay renderings will of course look nicer if you have the patience for > them. Well, PovRay rendering takes only a few seconds on my slow P200. Rendering VPython scenes is quite fast, because most timeconsuming features in rendering (transparency, reflection, area lights for soft shadows, radiosity, ...) are not used. Markus |
From: Ari H. <ahe...@an...> - 2001-03-21 16:34:00
|
On Wed, Mar 21, 2001 at 11:03:37AM -0500, David Andersen wrote: > Exporting to PovRay is the way to go. > I would just capture a screenshot and convert that to PostScript. PovRay renderings will of course look nicer if you have the patience for them. ari |
From: David A. <dm...@an...> - 2001-03-21 16:03:35
|
Exporting to PovRay is the way to go. Visual is not built on Tk, tho you can use Tk with visual (in another window). |
From: Markus G. <gr...@iu...> - 2001-03-21 15:49:32
|
Fortemps Philippe wrote: > I really appreciate to use VPython to graph the output of my > programs. How could I send those graphs to a PostScript file ? Maybe you want to export the scene to a PovRay file and render it at a high resolution to get perfect pictures. > If VPython is built on Tk, how can I reach canvas.postscript ? I don't think that visual is build on Tk, is it? Markus |
From: Fortemps P. <Phi...@fp...> - 2001-03-21 15:31:11
|
Hello, I really appreciate to use VPython to graph the output of my programs. How could I send those graphs to a PostScript file ? If VPython is built on Tk, how can I reach canvas.postscript ? Many thanks, Philippe ********************************************************** FORTEMPS Philippe Mons Institute of Technology (F.P.Ms) Mathematic & O.R. tel:+32-65-374685 Rue de Houdain, 9 fax:+32-65-374689 B-7000 Mons BELGIUM email:Phi...@fp... ********************************************************** |
From: Fred Y. <fc...@ac...> - 2001-03-16 00:07:31
|
I've got a fairly simple VPython application that uses Tk Scale widgets to control the layout of a simple array of VPython spheres. It works OK, except that the whole application hangs in some cases. I'm looking for clues as to how I can fix that. The program works such that there are Tk scale/slider widgets that control the width and height of a displayed array of VPython spheres. The program reuses a pool of sphere objects, setting spheres to invisible when they're not needed. The display responds to manual changes to the sliders for a while, but eventually hangs when I move a slider to decrease the array width or height. It looks as though it gets stuck at the point where X.visible is set to zero for some sphere X. By hanging, I mean that both the Tk and VPython windows stop responding to any mouse actions, and the main loop in the VPython thread stops cycling. If I comment-out the line that sets .visible, the program never seems to hang (but also doesn't display the objects correctly). Although my program uses a separate thread for the VPython animation, it looks like that might be unnecessary for this case. If I comment-out the line that start the thread, everything works the same. I'm using the 2001-02-27 release of VPython on WinNT. My program is temporarily available at <http://ontosys.com/src/residue.py>. -- Fred Yankowski fr...@On... tel: +1.630.879.1312 Principal Consultant www.OntoSys.com fax: +1.630.879.1370 OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA |
From: Fred Y. <fc...@ac...> - 2001-03-15 19:54:21
|
I've got a fairly simple VPython application that uses Tk Scale widgets to control the layout of a simple array of VPython spheres. It works OK, except that the whole application hangs in some cases. I'm looking for clues as to how I can fix that. The program works such that there are Tk scale/slider widgets that control the width and height of a displayed array of VPython spheres. The program reuses a pool of sphere objects, setting spheres to invisible when they're not needed. The display responds to manual changes to the sliders for a while, but eventually hangs when I move a slider to decrease the array width or height. It looks as though it gets stuck at the point where X.visible is set to zero for some sphere X. By hanging, I mean that both the Tk and VPython windows stop responding to any mouse actions, and the main loop in the VPython thread stops cycling. If I comment-out the line that sets .visible, the program never seems to hang (but also doesn't display the objects correctly). Although my program uses a separate thread for the VPython animation, it looks like that might be unnecessary for this case. If I comment-out the line that start the thread, everything works the same. I'm using the 2001-02-27 release of VPython on WinNT. My program is temporarily available at <http://ontosys.com/src/residue.py>. -- Fred Yankowski fr...@On... tel: +1.630.879.1312 Principal Consultant www.OntoSys.com fax: +1.630.879.1370 OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA |
From: Markus G. <gr...@iu...> - 2001-03-09 23:47:20
|
Hi Ruth! I took a look at your very well done module, which exports a VPython scene to a POVray file. I made the following improvements to it: v.1.1 2001-03-09 *) replaced 'scene' by 'display' everywhere *) added spheres at the joints of a curve *) consistent pov_texture usage in process_arrow() also for the shaft *) ambient light, light sources, up, and fov are now handled correctly *) some cosmetic changes to the code Kind regards, Markus |
From: Bruce S. <ba...@an...> - 2001-03-09 04:53:18
|
Matt Moelter pointed out typos in some of the VPython documentation. (  should have been to work properly on Netscape). Now fixed, for Windows and Mac. Thanks, Matt. Bruce |
From: Bruce S. <ba...@an...> - 2001-03-07 18:09:22
|
Thanks to Jim Boyle for reporting that the Mac package had a couple files with the wrong kinds of carriage returns. Now fixed. Bruce Sherwood |
From: Markus G. <gr...@iu...> - 2001-03-06 09:01:54
|
Fred Yankowski wrote: > VPython works fine from a command shell. I edit my programs in Emacs > and run them directly from a Cygwin shell on NT. I am editing my Python scripts with SciTE (http://www.scintilla.org/SciTE.html), and start them by pressing F5 in this editor. The interpreter is also startet in a separate process. > The "Kinetics Kit", http://stud4.tuwien.ac.at/~e9326522/KineticsKit/, > provides some compelling examples of VPython's power. Thanks for mentioning my little Kit. I added a few screenshots and beautyfied example code. I hope now it's even more easy to understand how to use KineticsKit. Enjoy, Markus |
From: Bruce S. <ba...@an...> - 2001-03-05 21:17:13
|
Thanks to David Andersen, there is a new VPython for the Mac, which brings the Mac up to date in terms of features and documentation. (But not alas yet with a version of IDLE like the version for Windows.) Bruce Sherwood |