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: Frederic L. <fre...@ka...> - 2009-05-18 11:00:05
|
Hello, [ using vpython 3.2.9 , the standard package for ubuntu 9.03 , on an x86_64 box ] I'm trying to make objects "stick" in front of the camera (see attached hud.py) . In theory, combining scene.forward and scene.mouse.camera should do the trick? However, I can see some delay in the repositioning when using userspin and userzoom. To me, this looks like scene.forward and scene.mouse.camera are not updated at the same time. Am I right in my analysis ? Any hint on what I could use to get this done with a smooth rendering ? Thanks, Regards, -- Frederic Lionello |
|
From: Bruce S. <Bru...@nc...> - 2009-05-17 02:44:46
|
In additional testing I'm deeply puzzled by strange failures I've seen on the Mac in trying to run programs with either VIDLE (installed with VPython 5.1) or IDLE (installed with Python 2.5 or Python 2.6). If you are unable to get VIDLE to work, try using IDLE, found in MacPython2.5 or Python 2.6 in Applications. I would be interested in hearing about what Mac users experience with VPython 5.1. Thanks. Bruce Sherwood |
|
From: Bruce S. <Bru...@nc...> - 2009-05-16 05:19:55
|
Now available at vpython.org (and sourceforge) is a package for VPython 5.1 for Linux, to be built for Python 2.5 or Python 2.6. Be sure to read INSTALL.txt carefully before attempting to build. There are special instructions for the recent Ubuntu 9.04. Ubuntu 9.04 does not include site-packages on the Python module search path, which seems a huge mistake. To deal with this, copy src/gtk2/site-packages.pth into /usr/lib/python2.6/dist-packages so that Python can find the visual module, which is installed in site-packages. Bruce Sherwood |
|
From: Bruce S. <Bru...@nc...> - 2009-05-16 03:39:46
|
Thanks much for the report. The Python 2.6 installers for Macs have now been fixed. Sigh. The problem was that in order to be able to build all the Mac installer, I necessarily had both Python 2.5 and Python 2.6 installed on an Intel Mac and on a PowerPC Mac. After building the installers for Python 2.5 I built installers for Python 2.6 but failed to change the requirement of having Python 2.5 installed to having Python 2.6 installed. The requirement was met on these computers, but not on yours, which is why I missed catching the error. Sorry about that. Bruce Sherwood Mark Hammond wrote: > Installed Python 2.6.2 on my MacBook Pro (OSX 10.5.6). > > Then tried to install VPython-Mac-Py2.6-5.1. I immediately get a message > saying Python 2.5 must be installed in order to install VPython. I can't > get past this message. > > Mark > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
|
From: Mark H. <mha...@st...> - 2009-05-16 02:23:56
|
Installed Python 2.6.2 on my MacBook Pro (OSX 10.5.6). Then tried to install VPython-Mac-Py2.6-5.1. I immediately get a message saying Python 2.5 must be installed in order to install VPython. I can't get past this message. Mark |
|
From: Bruce S. <Bru...@nc...> - 2009-05-15 18:36:57
|
There is now available VPython 5.1 for Python 2.6 on Intel Macs. Work is in progress to prepare the same for PowerPC Macs. Bruce Sherwood |
|
From: Bruce S. <Bru...@nc...> - 2009-05-15 16:55:38
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> This is a pretty interesting suggestion. I've forwarded it to a student in Brazil who will be working on IDLE and Tk issues in the Google Summer of Code program. Thanks. Sorry about your loss!<br> <br> Bruce Sherwood<br> <br> Symion wrote: <blockquote cite="mid:4A0...@ip..." type="cite">Hello everyone,<br> I have been using V-IDLE without problems for the last few weeks and have just installed the the new Vpython 5.1, which works well, so far. I particularly like the Auto-Save action, when running recently modified programs.<br> A good development aid that saves time and hassle.<br> <br> <div align="left">However, my reason for writing is due to the fact that I recently lost some of my latest programs, thanks to a hardware failure!<br> A collection I had been working on called 'TheBestOf' was irretrievably lost.<br> Even though I had a strict regime for backing up on a regular basis, I still ended up losing valuable data! <br> When hardware FAILS, it always seems to happen just Before you backup!!<br> So I have been forced to re-think the flawed methods used when saving my work.<br> <br> These are my observations and conclusions.<br> <br> The method described here is designed to make it easier for Developers to make Backups and Save their unique Work at the Same Time - Automatically<br> <br> How it would work:<br> When using V-IDLE and a New window is opened it is called 'untitled' by default.<br> When creating NEW files, as opposed to copying existing files, the problem of saving the file and selecting a name becomes an issue.<br> When you decide to save your work, you must Save As, (even if you try to use the Save option.)<br> This enables (forces?) you to type in a New name for your New program, before saving it to the current folder or what ever device/directory has been chosen.<br> <br> However, it would be useful at this point to be able to Save a Copy of the file to somewhere else! <br> This means you Back-Up you programs at The Same Time as you Save them. <br> With minimum effort and a huge time saving.<br> <br> So the proposal is:<br> Develop a New Menu option for V-IDLE File menu called ZenSave. (or some such)<br> ZenSave would be a save option that has Two Destination Paths!<br> The First path is the currently selected path, called 'current'.<br> The Second path is called the 'other', and points to another device like a USB Drive or other HD. <br> (Exactly what you would want for backup purposes!)<br> You must be able to set the exact paths of 'current' and 'other'.<br> Now whenever you ZenSave a file, it will be saved in Both places at the same time - Automatically!<br> <br> Then if the dreaded HD failure should strike, you will at least have a portable BACKUP of your ORIGINAL work!<br> <br> This solution is elegant as it solves the problems of saving and backing up programs, and without the hassle and time consumed by the need to double save each file to different places.<br> It would also allow the use of different devices, which is vital for secure program storage and archival purposes.<br> <br> I have not seen any implementation like this anywhere, except for a dual hard drive system called Raid, which does the same thing in hardware!<br> This method is like a Raid backup system, but implemented in software.<br> <br> I believe that if this suggestion was taken up by any interested developers, it would be of great assistance to Vpython developers, and may save someone else from losing their valuable Original programs.<br> <br> Symion<br> <br> </div> <pre wrap=""> <hr size="4" width="90%"> ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/businessobjects">http://p.sf.net/sfu/businessobjects</a></pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ Visualpython-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Vis...@li...">Vis...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/visualpython-users">https://lists.sourceforge.net/lists/listinfo/visualpython-users</a> </pre> </blockquote> </body> </html> |
|
From: Symion <kn...@ip...> - 2009-05-15 09:47:48
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> Hello everyone,<br> I have been using V-IDLE without problems for the last few weeks and have just installed the the new Vpython 5.1, which works well, so far. I particularly like the Auto-Save action, when running recently modified programs.<br> A good development aid that saves time and hassle.<br> <br> <div align="left">However, my reason for writing is due to the fact that I recently lost some of my latest programs, thanks to a hardware failure!<br> A collection I had been working on called 'TheBestOf' was irretrievably lost.<br> Even though I had a strict regime for backing up on a regular basis, I still ended up losing valuable data! <br> When hardware FAILS, it always seems to happen just Before you backup!!<br> So I have been forced to re-think the flawed methods used when saving my work.<br> <br> These are my observations and conclusions.<br> <br> The method described here is designed to make it easier for Developers to make Backups and Save their unique Work at the Same Time - Automatically<br> <br> How it would work:<br> When using V-IDLE and a New window is opened it is called 'untitled' by default.<br> When creating NEW files, as opposed to copying existing files, the problem of saving the file and selecting a name becomes an issue.<br> When you decide to save your work, you must Save As, (even if you try to use the Save option.)<br> This enables (forces?) you to type in a New name for your New program, before saving it to the current folder or what ever device/directory has been chosen.<br> <br> However, it would be useful at this point to be able to Save a Copy of the file to somewhere else! <br> This means you Back-Up you programs at The Same Time as you Save them. <br> With minimum effort and a huge time saving.<br> <br> So the proposal is:<br> Develop a New Menu option for V-IDLE File menu called ZenSave. (or some such)<br> ZenSave would be a save option that has Two Destination Paths!<br> The First path is the currently selected path, called 'current'.<br> The Second path is called the 'other', and points to another device like a USB Drive or other HD. <br> (Exactly what you would want for backup purposes!)<br> You must be able to set the exact paths of 'current' and 'other'.<br> Now whenever you ZenSave a file, it will be saved in Both places at the same time - Automatically!<br> <br> Then if the dreaded HD failure should strike, you will at least have a portable BACKUP of your ORIGINAL work!<br> <br> This solution is elegant as it solves the problems of saving and backing up programs, and without the hassle and time consumed by the need to double save each file to different places.<br> It would also allow the use of different devices, which is vital for secure program storage and archival purposes.<br> <br> I have not seen any implementation like this anywhere, except for a dual hard drive system called Raid, which does the same thing in hardware!<br> This method is like a Raid backup system, but implemented in software.<br> <br> I believe that if this suggestion was taken up by any interested developers, it would be of great assistance to Vpython developers, and may save someone else from losing their valuable Original programs.<br> <br> Symion<br> <br> </div> </body> </html> |
|
From: Bruce S. <Bru...@nc...> - 2009-05-15 06:27:47
|
Now available: Visual 5.1 for Python 2.5 for Mac (Intel and PowerPC). There doesn't seem to be a version of numpy for Mac Python 2.6 yet, which is needed by VPython. Work is proceeding on packaging 5.1 for Linux; the requisite files are in CVS. In the process of implementing right-button and middle-button mouse events, similar to what was available for Visual 3, David Scherer and I have run into some issues that concern us. VPython 5.1 provides the basic mouse event functionality that was present in Visual 3 for handling events from right and middle buttons when userspin or userzoom is disabled, because we have been concerned about supporting old programs. However, we have become aware that there are limitations in this approach which could preclude some kinds of mouse handling that people might want to do in the future. For example, you might want to allow userspin with right drags yet also pick up right clicks. For that reason it is conceivable that future developments in this area might break existing programs, and therefore for maximum forward compatibility it is prudent to use only left-button interactions in new programs. Bruce Sherwood |
|
From: Bruce S. <Bru...@nc...> - 2009-05-14 05:20:21
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;">Visual 5.1 for Python 2.5 and 2.6 has been released for Windows. David Scherer provided crucial help for getting Visual to work on Python 2.6. Visual 5.1 includes formerly missing features of Visual 3, including right-button and middle-button mouse event handling. The documentation has been updated and improved. Mac and Linux installers are being prepared.<br> <br> Now that all features of Visual 3 have been implemented for both Python 2.5 and Python 2.6, the new release is now longer to be considered a "release candidate" but the actual production version, since very few bugs were reported in the release candidate.<br> <br> Bruce Sherwood<br> <br> </span> </body> </html> |
|
From: Joel K. <jj...@ya...> - 2009-05-13 18:47:44
|
Some of you might be interested in this upcoming event: http://geometryalgebra.zcu.cz/GraVisMa/Index.htm Best of luck. Joel |
|
From: Chris C. <cb...@un...> - 2009-05-12 17:10:46
|
On 5/12/2009 11:46 AM, Joe Heafner wrote: > Anyone seen this? It looks interesting. > > http://www.amazon.com/Python-Scripting-Computational-Science-Engineering/dp/3540739157/ref=wl_it_dp?ie=UTF8&coliid=I254OTO7T6CA36&colid=SN4L42BSUUQM It's very cookbook-like. You definitely want the new third edition if you get this because the older editions have recipes that are broken with more recent releases of Numpy, matplotlib, and Scipy. -- Sincerely, Chris Calloway http://www.secoora.org office: 332 Chapman Hall phone: (919) 599-3530 mail: Campus Box #3300, UNC-CH, Chapel Hill, NC 27599 |
|
From: Joe H. <hea...@gm...> - 2009-05-12 15:46:48
|
Anyone seen this? It looks interesting. http://www.amazon.com/Python-Scripting-Computational-Science-Engineering/dp/3540739157/ref=wl_it_dp?ie=UTF8&coliid=I254OTO7T6CA36&colid=SN4L42BSUUQM Joe Heafner (follow me on Twitter: twitter.com/heafnerj) email: heafnerj(at)gmail(dot)com URL: www(dot)SticksAndShadows(dot)com |
|
From: Bruce S. <Bru...@nc...> - 2009-05-11 14:41:17
|
I've been mostly successful with both Boost 1.37 and 1.38 but know of
three issues. Here's the first, which I found in a web search after
encountering problems trying to build, which seems to be a bug in Boost:
Furthermore building pyrap with boost-1.37 and gcc-4.3.2 gave an error
due to a missing include. The following patch has to be applied to
boost:
Index: boost/python/detail/translate_exception.hpp
===================================================================
--- boost/python/detail/translate_exception.hpp (revision 50228)
+++ boost/python/detail/translate_exception.hpp (working copy)
@@ -9,6 +9,7 @@
# include <boost/call_traits.hpp>
# include <boost/type_traits/add_const.hpp>
+# include <boost/type_traits/add_reference.hpp>
# include <boost/function/function0.hpp>
--------------------------------------
Here's the second issue:
You also need the threadpool resource:
sourceforge.net/projects/threadpool.
If you are using the 1_35_0 Boost libraries, you can use version
0.2.4 which
is included in the package (in dependencies). If you use a different
version
of the Boost libraries, you need to get an appropriate threadpool
version and
replace the files in "dependencies/threadpool/include". Copy into
the include
directory the contents of the boost directory in the threadpool package,
which includes a directory named "include" and a file "threadpool.hpp".
And the third, which I haven't yet figured out. After building Visual 5
on Ubuntu and Windows, I find that numpy.int32 is not recognized as an
integer that can be converted when needed as a double. For example,
vector(int,double,double) is okay, but vector(numpy.int32,double,double)
fails. This can occur if a vector argument comes from the use of arange,
and it causes several standard VPython example programs to fail. I've
been trying to install a manual converter using Boost, but have failed
so far due to lack of adequate knowledge of Boost.
Bruce Sherwood
Helmut Jarausch wrote:
> Hi,
>
> which version of the boost libraries are needed for visualpython?
>
> On my Gentoo system, the ebuild requires boost-1.35* which is in
> conflict with other packages.
> Does visualpython have problems with boost-1.37 ?
>
> Many thanks for a hint,
>
> Helmut Jarausch
>
> Lehrstuhl fuer Numerische Mathematik
> RWTH - Aachen University
> D 52056 Aachen, Germany
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
|
|
From: Helmut J. <jar...@ig...> - 2009-05-11 10:23:53
|
Hi, which version of the boost libraries are needed for visualpython? On my Gentoo system, the ebuild requires boost-1.35* which is in conflict with other packages. Does visualpython have problems with boost-1.37 ? Many thanks for a hint, Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany |
|
From: Bruce S. <Bru...@nc...> - 2009-05-11 00:46:10
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Frankly, such a revision has extremely low priority among the things
that really do need to be done.<br>
<br>
Bruce Sherwood<br>
<br>
Guy K. Kloss wrote:
<blockquote cite="mid:200...@ma..."
type="cite">
<pre wrap="">On Mon, 11 May 2009 09:19:10 Bruce Sherwood wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> It's likely that when David Scherer created Visual in 2000 these
conventions were not well established. For internal consistency we can't
really change now.
</pre>
</blockquote>
<pre wrap=""><!---->
You've got a point there, but ... even Python is reinventing itself with the
3.0 version to get rid of old annoyances.
So there could be a "parallel API" for an intermediate time, to keep things
working, and later the old API could be marked as deprecated to "wash them
out". If it works with Python (also to some lesser extent in older version
changes), why shouldn't it work with Visual?
Guy
</pre>
</blockquote>
</body>
</html>
|
|
From: Guy K. K. <g....@ma...> - 2009-05-10 21:54:02
|
On Mon, 11 May 2009 09:19:10 Bruce Sherwood wrote: > It's likely that when David Scherer created Visual in 2000 these > conventions were not well established. For internal consistency we can't > really change now. You've got a point there, but ... even Python is reinventing itself with the 3.0 version to get rid of old annoyances. So there could be a "parallel API" for an intermediate time, to keep things working, and later the old API could be marked as deprecated to "wash them out". If it works with Python (also to some lesser extent in older version changes), why shouldn't it work with Visual? Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: G....@ma... http://iims.massey.ac.nz |
|
From: Bruce S. <Bru...@nc...> - 2009-05-10 21:19:14
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Guy K. Kloss wrote:
<blockquote cite="mid:200...@ma..."
type="cite">
<pre wrap="">On Mon, 11 May 2009 03:25:28 Bruce Sherwood wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> if obj.__class__ is distant_light:
</pre>
</blockquote>
<pre wrap=""><!---->
Shouldn't that be rather
if isinstance(obj, distant_light):
to make it more Pythonic?
</pre>
</blockquote>
Good point. I've made that change and posted the program in the
contributed section of vpython.org. And I'll change the documentation
for Visual accordingly.<br>
<blockquote cite="mid:200...@ma..."
type="cite">
<pre wrap="">
On that same topic of "Pythonicness" of the Visual API. I've noticed, that the
classes don't really follow the common PEP-8 guide lines. They rather use the
notation of attributes than classes (lower case and joined with underscores,
rather than CamelCase). That confuses often when conditioned to Python naming
schemes to infer types of labels in code.
Guy
</pre>
</blockquote>
It's likely that when David Scherer created Visual in 2000 these
conventions were not well established. For internal consistency we
can't really change now.<br>
<br>
Bruce Sherwood<br>
</body>
</html>
|
|
From: Guy K. K. <g....@ma...> - 2009-05-10 20:16:48
|
On Mon, 11 May 2009 03:25:28 Bruce Sherwood wrote: > Here is an improved version of a program that effectively rotates the > scene rather than the camera. It makes sure that local lights rotate > with the scene; only distant lights are "fixed". Thanks for that. It does work nicely. However it puts one in the position to need that extra loop (in a thread) to handle these things, so it doesn't have that "ease" of simply using Visual for simple rendering. But it's a good start if one needs that feature. > if obj.__class__ is distant_light: Shouldn't that be rather if isinstance(obj, distant_light): to make it more Pythonic? On that same topic of "Pythonicness" of the Visual API. I've noticed, that the classes don't really follow the common PEP-8 guide lines. They rather use the notation of attributes than classes (lower case and joined with underscores, rather than CamelCase). That confuses often when conditioned to Python naming schemes to infer types of labels in code. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: G....@ma... http://iims.massey.ac.nz |
|
From: Bruce S. <Bru...@nc...> - 2009-05-10 15:25:31
|
Here is an improved version of a program that effectively rotates the
scene rather than the camera. It makes sure that local lights rotate
with the scene; only distant lights are "fixed".
It also incorporates a feature that I forgot to document:
"scene.material = materials.wood" makes the default material be wood
(overridden by specific material specifications).
from visual import *
# This routine watches scene.forward and changes the directions of
# the lights to stay fixed with respect to scene.forward.
# The effect is to let the user rotate the scene while keeping
# the lights fixed, as though one were rotating an object in the
# hand to examine it, with fixed lighting, rather than rotating
# the camera.
# To compare, comment out the while loop, in which case you'll see
# that when you rotate around to the back of the scene, it is dark.
# This requires Visual 5. A similar routine in Visual 3 would be
# somewhat more complicated because the lights were not objects
# and so could not be put in a frame. Instead, one would have to
# adjust the directions of the lights individually.
# Bruce Sherwood, May 2009
scene.material = materials.wood # default material for all objects
box(pos=(-2,0,0), color=color.red)
box(pos=(2,0,0), color=color.green, material=materials.marble)
cylinder(pos=(0,-0.5,0), radius=1, axis=(0,1,0), color=color.orange)
s = sphere(pos=(-2,0.8,0), radius=0.3, color=color.cyan,
material=materials.emissive)
local_light(pos=s.pos, color=s.color)
lframe = frame()
for obj in scene.lights:
if obj.__class__ is distant_light:
obj.frame = lframe # put distant lights in a frame
old = vector(scene.forward) # keep a copy of the old forward
while 1:
rate(50)
if scene.forward != old:
new = scene.forward
axis = cross(old,new)
angle = new.diff_angle(old)
lframe.rotate(axis=axis, angle=angle)
old = vector(new)
|
|
From: Guy K. K. <g....@ma...> - 2009-05-10 04:08:55
|
forgot to go to list ... ---------- Forwarded Message ---------- Subject: Re: [Visualpython-users] feature request Date: Sun, 10 May 2009 From: "Guy K. Kloss" <g....@ma...> To: Bruce Sherwood <Bru...@nc...> On Thu, 07 May 2009 16:00:12 you wrote: > Note too that in your application you might want to increase the "ambient" > light a bit, so that no part of an object is very dark. I have just played a little bit with a different ambient and modified light sources, as it was quite new to me that this is possible. Anyway ... here's a result: http://drop.io/yguobhm/asset/pointcloud3d-png I'm getting *much* better results from the Dark Side of the Moon, now. However, at the expense of the feeling for depth in the scene. So turning a scene model "in your hand" with stationary light sources would be still an awesome extension, but for now I'm quite happy with the enhanced ambient light intensity. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: G....@ma... http://iims.massey.ac.nz |
|
From: Bruce S. <Bru...@nc...> - 2009-05-10 04:07:34
|
from visual import *
# This routine watches scene.forward and changes the directions of
# the lights to stay fixed with respect to scene.forward.
# The effect is to let the user rotate the scene while keeping
# the lights fixed, as though one were rotating an object in the
# hand to examine it, with fixed lighting, rather than rotating
# the camera.
# To compare, comment out the while loop, in which case you'll see
# that when you rotate around to the back of the scene, it is dark.
# This requires Visual 5. A similar routine in Visual 3 would be
# somewhat more complicated because the lights were not objects
# and so could not be put in a frame. Instead, one would have to
# adjust the directions of the lights individually.
# Bruce Sherwood, May 2009
lframe = frame()
for obj in scene.lights:
obj.frame = lframe # put lights in a frame
box(pos=(-2,0,0), color=color.red)
box(pos=(2,0,0), color=color.cyan)
cylinder(pos=(0,-0.5,0), radius=1, axis=(0,1,0), color=color.orange)
old = vector(scene.forward) # keep a copy of the old forward
while 1:
rate(50)
if scene.forward != old:
new = scene.forward
axis = cross(old,new)
angle = new.diff_angle(old)
lframe.rotate(axis=axis, angle=angle)
old = vector(new)
|
|
From: Stef M. <s.m...@ru...> - 2009-05-07 16:31:31
|
My program (PyLab_Works) is heavily depending on VPython 5.0, and I want to make it available under Win, Linux(Ubuntu) and Mac. Although I know nothing of Ubuntu, I get my program (almost) perfectly working under Ubuntu, just by download and install from the Ubuntu database, except ... ... for VPython V5 Is'nt there an Ubuntu guru that can add VPython 5 to the Ubuntu database ? thanks, Stef Mientki David Froger wrote: > sudo apt-get install libgtkglextmm-x11-1.2-dev libglademm-2.4-dev > libboost-python1.35-dev > > A simple script now is ok: > > import visual > visual.sphere() > > 2009/5/7 David Froger <dav...@gm... > <mailto:dav...@gm...>> > > Hi, > > I'm new to python visual, I install it with > python-visual_5.0rc3~jaunty-1_i386.deb > <https://gutefee.massey.ac.nz/moin/Python/3D?action=AttachFile&do=view&target=python-visual_5.0rc3%7Ejaunty-1_i386.deb> > (thanks Guy K. Kloss!) from > https://gutefee.massey.ac.nz/moin/Python/3D > > When I try a 'import visual', I get: > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib/python2.6/dist-packages/visual/__init__.py", line > 59, in <module> > import cvisual > ImportError: libgtkglextmm-x11-1.2.so.0: cannot open shared object > file: No such file or directory > > Ubuntu 9.04, Python 2.6.2 > > Thanks for any help! > > David > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > ------------------------------------------------------------------------ > > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
|
From: Bruce S. <Bru...@nc...> - 2009-05-07 11:48:24
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I'm traveling and unable to do this myself right now, but you could
achieve the effect by putting the distant lights into a frame and then
sitting in a loop (maybe with rate(50) to limit processing) and
watching scene.forward. Use any change in scene.forward to determine
how to rotate the frame containing the distant lights. Should work.<br>
<br>
Bruce Sherwood<br>
<br>
Guy K. Kloss wrote:
<blockquote cite="mid:200...@ma..."
type="cite">
<pre wrap="">On Thu, 07 May 2009 16:00:12 Bruce Sherwood wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Note too that in your application you might want to increase the "ambient"
light a bit, so that no part of an object is very dark.
</pre>
</blockquote>
<pre wrap=""><!---->
Yes, some good ideas coming up here to experiment with.
</pre>
<blockquote type="cite">
<pre wrap="">I do see merit in an option to change from the default behavior (rotate the
camera around a scene that has lights to that scene) to a behavior where
the camera and lights are fixed and you rotate the scene, as though you
were turning a model in your hand to inspect it from different angles but
with a fixed light source.
What would this be called? scene.camera_rotate = False?
</pre>
</blockquote>
<pre wrap=""><!---->
Good question. That or maybe one of these?
scene.fixed_light = False
scene.light_on_camera = True
</pre>
<blockquote type="cite">
<pre wrap="">The hard part though is the implementation.....
</pre>
</blockquote>
<pre wrap=""><!---->
As so often ... :-)
Guy
</pre>
</blockquote>
</body>
</html>
|
|
From: Guy K. K. <g....@ma...> - 2009-05-07 04:19:39
|
On Thu, 07 May 2009 16:00:12 Bruce Sherwood wrote: > Note too that in your application you might want to increase the "ambient" > light a bit, so that no part of an object is very dark. Yes, some good ideas coming up here to experiment with. > I do see merit in an option to change from the default behavior (rotate the > camera around a scene that has lights to that scene) to a behavior where > the camera and lights are fixed and you rotate the scene, as though you > were turning a model in your hand to inspect it from different angles but > with a fixed light source. > > What would this be called? scene.camera_rotate = False? Good question. That or maybe one of these? scene.fixed_light = False scene.light_on_camera = True > The hard part though is the implementation..... As so often ... :-) Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: G....@ma... http://iims.massey.ac.nz |
33 messages has been excluded from this view by a project administrator.
