visualpython-users

[Visualpython-users] polygon dependency

[Thomas S. <to...@fe...>]

Hi list,

is it possible to drop the polygon dependency somehow (or at least make
it optionally).

I just tried to package it for fedora and noticed the dependency to
gpc, which is non-free:
https://fedorahosted.org/fpc/ticket/74

When that can't be resolved by polygon upstream (and I bet it can't,
because they would be forced to rewrite the gpc library somehow),
vpython will never work on fedora, because polygon can't be imported...

Greetings,
   Thomas

Re: [Visualpython-users] a trouble in fedora 64

[Thomas S. <to...@fe...>]

Current scratch build for F14 in your case:
python-polygon:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2929798
TTFQuery:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2929820

	Thomas


On Mon, 21 Mar 2011 19:57:59 +0000
jorge a secas wrote:

> 
> thanks
> 
> i'm traying to install Polygon and TTFQuery but i have a lot of
> error, but if you have them in rpm that would be great, i have fedora
> 14 64
> 
> thanks again
> 
> regards.
> 
> > Date: Mon, 21 Mar 2011 20:48:44 +0100
> > From: to...@fe...
> > To: vin...@un...
> > CC: ta...@ho...; vis...@li...
> > Subject: Re: [Visualpython-users] a trouble in fedora 64
> > 
> > On Mon, 21 Mar 2011 13:29:36 -0400
> > Michael Vineyard wrote:
> > 
> > > Hi Jorge,
> > > 
> > > I think you need to make the following soft link in /usr/lib64:
> > > 
> > > ln -s libboost_thread-mt.so.1.44.0 libboost_thread.so
> > 
> > Or use:
> > sed -i 's/boost_thread/boost_thread-mt/g' src/Makefile.in
> > 
> > Sorry, that the fedora package is currently a bit broken.
> > I'm packaging polygon and ttfquery right now, to make it usable
> > again...
> > 
> > 	Thomas
>  		 	   		  

Re: [Visualpython-users] a trouble in fedora 64

[Thomas S. <to...@fe...>]

On Mon, 21 Mar 2011 13:29:36 -0400
Michael Vineyard wrote:

> Hi Jorge,
> 
> I think you need to make the following soft link in /usr/lib64:
> 
> ln -s libboost_thread-mt.so.1.44.0 libboost_thread.so

Or use:
sed -i 's/boost_thread/boost_thread-mt/g' src/Makefile.in

Sorry, that the fedora package is currently a bit broken.
I'm packaging polygon and ttfquery right now, to make it usable again...

	Thomas

Re: [Visualpython-users] a trouble in fedora 64

[Michael V. <vin...@un...>]

Hi Jorge,

I think you need to make the following soft link in /usr/lib64:

ln -s libboost_thread-mt.so.1.44.0 libboost_thread.so

Cheers,

Mike Vineyard

On Mon, Mar 21, 2011 at 1:12 PM, jorge a secas <ta...@ho...> wrote:

>  hi everybody
>
> i'm trying to install vpython in fedora 64, but i have some troubles when
> make
> i already have installed boost_thread
>
>
> ./configure --prefix=/usr
> .
> .
> .
> make
> .
> .
> .
>
> libtool: link: g++ -shared -nostdlib
> /usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../../../lib64/crti.o
> /usr/lib/gcc/x86_64-redhat-linux/4.5.1/crtbeginS.o  .libs/atomic_queue.o
> .libs/displaylist.o .libs/errors.o .libs/extent.o .libs/gl_extensions.o
> .libs/gl_free.o .libs/icososphere.o .libs/quadric.o .libs/render_manager.o
> .libs/rgba.o .libs/shader_program.o .libs/texture.o .libs/tmatrix.o
> .libs/vector.o .libs/arrow.o .libs/axial.o .libs/box.o .libs/cone.o
> .libs/cylinder.o .libs/display_kernel.o .libs/ellipsoid.o .libs/extrusion.o
> .libs/frame.o .libs/label.o .libs/light.o .libs/material.o
> .libs/mouse_manager.o .libs/mouseobject.o .libs/primitive.o .libs/pyramid.o
> .libs/rectangular.o .libs/renderable.o .libs/ring.o .libs/sphere.o
> .libs/text.o .libs/display.o .libs/font_renderer.o .libs/random_device.o
> .libs/render_surface.o .libs/timer.o .libs/arrayprim.o .libs/convex.o
> .libs/curve.o .libs/cvisualmodule.o .libs/faces.o .libs/num_util.o
> .libs/numeric_texture.o .libs/points.o .libs/slice.o
> .libs/wrap_arrayobjects.o .libs/wrap_display_kernel.o .libs/wrap_primitive.o
> .libs/wrap_rgba.o .libs/wrap_vector.o .libs/rate.o   -Wl,-rpath
> -Wl,/usr/lib64 -Wl,-rpath -Wl,/usr/lib64 /usr/lib64/
> libgtkglextmm-x11-1.2.so /usr/lib64/libgdkglextmm-x11-1.2.so-lgtkglext-x11-1.0 -lgdkglext-x11-1.0 -lGLU -lGL -lXmu -lXt -lSM -lICE
> -lpangox-1.0 -lX11 -lglademm-2.4 -lgtkmm-2.4 -lglade-2.0 -latkmm-1.6
> -lgdkmm-2.4 -lgiomm-2.4 -lpangomm-1.4 -lglibmm-2.4 -lcairomm-1.0 -lsigc-2.0
> -lgtk-x11-2.0 -lxml2 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
> -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpng12 -lpango-1.0 -lfontconfig
> -lgobject-2.0 -lgmodule-2.0 -lfreetype -lgthread-2.0 -lrt -lglib-2.0
> -lboost_python -lboost_thread -lboost_signals
> -L/usr/lib/gcc/x86_64-redhat-linux/4.5.1
> -L/usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../../../lib64 -L/lib/../lib64
> -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../..
> -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-redhat-linux/4.5.1/crtendS.o
> /usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../../../lib64/crtn.o
> -Wl,--export-dynamic -pthread -pthread
> -Wl,--version-script=./linux-symbols.map   -pthread -Wl,-soname
> -Wl,cvisualmodule.so.3 -o .libs/cvisualmodule.so.3.0.0
> /usr/bin/ld: cannot find -lboost_thread
> collect2: ld returned 1 exit status
>
>
>
>
> thanks
>
> regards.
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>


-- 
Michael F. Vineyard
Frank & Marie Louise Bailey Professor of Physics
Department of Physics & Astronomy
Union College
Schenectady, NY 12308
Email: vin...@un...
Web: http://www1.union.edu/vineyarm
Phone: (518) 388-8353
Fax: (518) 388-6947

[Visualpython-users] a trouble in fedora 64

[jorge a s. <ta...@ho...>]

hi everybody

i'm trying to install vpython in fedora 64, but i have some troubles when make
i already have installed boost_thread


./configure --prefix=/usr
.
.
.
make
.
.
. 

libtool: link: g++ -shared -nostdlib /usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../../../lib64/crti.o /usr/lib/gcc/x86_64-redhat-linux/4.5.1/crtbeginS.o  .libs/atomic_queue.o .libs/displaylist.o .libs/errors.o .libs/extent.o .libs/gl_extensions.o .libs/gl_free.o .libs/icososphere.o .libs/quadric.o .libs/render_manager.o .libs/rgba.o .libs/shader_program.o .libs/texture.o .libs/tmatrix.o .libs/vector.o .libs/arrow.o .libs/axial.o .libs/box.o .libs/cone.o .libs/cylinder.o .libs/display_kernel.o .libs/ellipsoid.o .libs/extrusion.o .libs/frame.o .libs/label.o .libs/light.o .libs/material.o .libs/mouse_manager.o .libs/mouseobject.o .libs/primitive.o .libs/pyramid.o .libs/rectangular.o .libs/renderable.o .libs/ring.o .libs/sphere.o .libs/text.o .libs/display.o .libs/font_renderer.o .libs/random_device.o .libs/render_surface.o .libs/timer.o .libs/arrayprim.o .libs/convex.o .libs/curve.o .libs/cvisualmodule.o .libs/faces.o .libs/num_util.o .libs/numeric_texture.o .libs/points.o .libs/slice.o .libs/wrap_arrayobjects.o .libs/wrap_display_kernel.o .libs/wrap_primitive.o .libs/wrap_rgba.o .libs/wrap_vector.o .libs/rate.o   -Wl,-rpath -Wl,/usr/lib64 -Wl,-rpath -Wl,/usr/lib64 /usr/lib64/libgtkglextmm-x11-1.2.so /usr/lib64/libgdkglextmm-x11-1.2.so -lgtkglext-x11-1.0 -lgdkglext-x11-1.0 -lGLU -lGL -lXmu -lXt -lSM -lICE -lpangox-1.0 -lX11 -lglademm-2.4 -lgtkmm-2.4 -lglade-2.0 -latkmm-1.6 -lgdkmm-2.4 -lgiomm-2.4 -lpangomm-1.4 -lglibmm-2.4 -lcairomm-1.0 -lsigc-2.0 -lgtk-x11-2.0 -lxml2 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpng12 -lpango-1.0 -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lfreetype -lgthread-2.0 -lrt -lglib-2.0 -lboost_python -lboost_thread -lboost_signals -L/usr/lib/gcc/x86_64-redhat-linux/4.5.1 -L/usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-redhat-linux/4.5.1/crtendS.o /usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../../../lib64/crtn.o  -Wl,--export-dynamic -pthread -pthread -Wl,--version-script=./linux-symbols.map   -pthread -Wl,-soname -Wl,cvisualmodule.so.3 -o .libs/cvisualmodule.so.3.0.0
/usr/bin/ld: cannot find -lboost_thread
collect2: ld returned 1 exit status




thanks

regards. 		 	   		  

[Visualpython-users] a trouble in fedora 64

[jorge a s. <ta...@ho...>]

[Visualpython-users] Reposting of VPython 5.60 for Python 2.6

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

I made a mistake in the file uploaded for VPython 5.60 for Python 2.6;
it wasn't quite the very latest version. Now fixed.

Bruce Sherwood

[Visualpython-users] Making installers for the Mac

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

I wonder whether a Mac expert who reads this list might have an
insight into a very strange problem I've encountered in building
VPython installers for Python 2.6, 2.7, and 3.1.

I use Apple PackageMaker to create the Mac installers posted at
vpython.org. Only recently I became aware that using one of these
installers (say for Python 2.6) deletes the contents of the folders
FontTools, numpy, Poygon, and ttfquery in site-packages for other
installed Pythons!! The folders vidle, vis, and visual are not
affected.

I cannot find any differences in the file permissions or other
parameters in PackageMaker between the folders that get emptied and
those that aren't affected, and it boggles the mind that an installer
that correctly places everything in the targeted site-packages folder
somehow manages to delete files from site-packages for other Pythons.
Of course the problem mainly affects me, since most people don't
maintain multiple Pythons and VPythons on their Macs.

Even if you don't have any advice on this bug, perhaps you can
recommend a different installer. I did at one time try another
installer (I forget which one) and didn't find it congenial.

Bruce Sherwood

[Visualpython-users] VPython 5.60

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

New in Visual 5.60 for Windows, Mac, and Linux:

* Facilities to extract faces data from extrusion and text objects;
see the documentation for these two objects. I had hoped that
converting an extrusion or text object to a faces object would result
in faster rendering, but in fact it usually doesn't, and in some cases
it renders significantly more slowly. I suspect this has to do with
the unavoidable manipulation of large arrays in the faces object,
though I'm surprised, because I would have thought that reading up the
vertices and normals for a triangle would be faster than figuring out
what vertices and normals to draw (as the extrusion code must do).

However, we are using the new conversion facilities to upgrade the
povexport module to permit exporting extrusion and text objects to
Pov-ray for high-quality (non-real-time) creation of high-resolution
versions of VPython scenes. This work is not quite done.

* The ability to make extrusion and text objects single-sided for
increased speed. By default, all VPython objects other than the faces
object are two-sided. For example, if you move inside a box, you see
the inner sides of the box. In many cases you might not care about
this two-sidedness, and an extrusion or text object will render a
little bit faster if you say twosided=False.

* Kadir Haldenbilen has improved the gear facilities in the shapes
library, and added rack gears (linear gears, that mesh with circular
gears). He has also contributed another example program,
extrusion_examples.py, that you will find quite useful as an overview
of what one can do with extrusion objects.

* The feature scene.show_rendertime = True has been revised because it
was discovered that it was not displaying accurate information. Now if
you set scene.show_rendertime = True, in the lower left corner of the
display you will see something like "cycle: 40" (without the estimate
of the time required to render the scene), meaning 40 milliseconds
between renderings of the scene. The minimum cycle time is about 30
milliseconds (about 30 renderings per second). Approximately half of
the cycle time is devoted to rendering the scene, and about half to
your own computations; longer cycle times reflect longer render times
(but with 50% of the time still dedicated to computations). If the
scene is not very complicated, very little time is needed to render
the scene, and almost all the time is given to your computations.

Along with this correction to the reporting, a mistake was corrected
that could lead to very short cycle times, which is pointless, because
producing 150 images per second serves no human purpose.

Bruce Sherwood

Re: [Visualpython-users] vertical_spacing error

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

Darn. The statement paintText() should be self.paintText().

Thanks much for catching the error. It will be fixed in the next release.

Bruce Sherwood

On Tue, Mar 8, 2011 at 2:22 AM, Symion <kn...@ip...> wrote:
>
> I have found problem in vis.primitives.
>
> from visual import *
>
> #  works correctly
> word = text(text="A\nB\nC\nD",
>     vertical_spacing=10)
>
> # Generates the error
> word.vertical_spacing=1
>
> Traceback (most recent call last):
>   File "<pyshell#2>", line 1
>     word.vertical_spacing=1
>   File "C:\Python27\lib\site-packages\vis\primitives.py", line 880, in
> set_vertical_spacing
>     paintText()
> NameError: global name 'paintText' is not defined

[Visualpython-users] vertical_spacing error

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    <br>
    I have found problem in vis.primitives. <br>
    <br>
    from visual import *<br>
    <br>
    #&nbsp; works correctly<br>
    word = text(text="A\nB\nC\nD",<br>
    &nbsp;&nbsp;&nbsp; vertical_spacing=10)<br>
    <br>
    # Generates the error<br>
    word.vertical_spacing=1<br>
    <br>
    Traceback (most recent call last):<br>
    &nbsp; File "&lt;pyshell#2&gt;", line 1<br>
    &nbsp;&nbsp;&nbsp; word.vertical_spacing=1<br>
    &nbsp; File "C:\Python27\lib\site-packages\vis\primitives.py", line 880,
    in set_vertical_spacing<br>
    &nbsp;&nbsp;&nbsp; paintText()<br>
    NameError: global name 'paintText' is not defined<br>
    <br>
    <br>
  </body>
</html>

Re: [Visualpython-users] Error with Vidle

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

Try this, and report the results:

Open a Terminal program.
Enter "python3.1", which should start up Python 3.1.
Enter "from visual import *".
Then enter "box()". You should see a white box, and by holding the cmd
or option keys you should be able to rotate or zoom.

Presumably you'll get error messages, which will help debug your problem.

Bruce Sherwood

On Sat, Mar 5, 2011 at 1:44 AM, Georges Arsouze
<geo...@gm...> wrote:
> I'm under Snow  Leopard mac Os
> I have Python 3.1.3 in /Library/frameworks/Python.framework/versions/3.1/bin
> I install VPython-Py 3.1
> Now in my menu Application I have
>  a folder Python .1 and a folder VPython-Py 3.1
> When i click the icon Idle.app in the folder Python 3.1 it's go in the dock
> and then disappears
> when I click the icon Vidle.app in the folder VPython-Py 3.1 i obtain a new
> window for Vidle. I load an example (cf tutorial bounce2.py). When I want to
> run this module I obtain a new window blank Python shell
>
> I don't understand.
> when i'm in a terminal et I use idle3.1
> (in /Library/frameworks/Python.framework/versions/3.1/bin) Idle works ok
> Can you help me ?
> I already done 3 install and unistall of Pthon3.1 and VPython 3.1
> Regards
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>

[Visualpython-users] Error with Vidle

[Georges A. <geo...@gm...>]

I'm under Snow  Leopard mac Os
I have Python 3.1.3 in /Library/frameworks/Python.framework/versions/3.1/bin
I install VPython-Py 3.1

Now in my menu Application I have
 a folder Python .1 and a folder VPython-Py 3.1

When i click the icon Idle.app in the folder Python 3.1 it's go in the dock
and then disappears

when I click the icon Vidle.app in the folder VPython-Py 3.1 i obtain a new
window for Vidle. I load an example (cf tutorial bounce2.py). When I want to
run this module I obtain a new window blank Python shell


I don't understand.

when i'm in a terminal et I use idle3.1
(in /Library/frameworks/Python.framework/versions/3.1/bin) Idle works ok

Can you help me ?
I already done 3 install and unistall of Pthon3.1 and VPython 3.1
Regards

Re: [Visualpython-users] text color problem?

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

I haven't used decorators myself, and because Visual was initiated in
2000, there aren't any decorators anywhere in the Python portions of
Visual. So I'm tone-deaf to the issue here and don't understand what
advantage would accrue either to developers of Visual or users of
Visual by replacing the following code (currently found in
vis/primitives.py)

    def set_color(self, color):
        self.extrusion.color = color

    def get_color(self):
        return self.__color

    color = property( get_color, set_color, None)

with

   @color.setter
   def set_color(self, color):
       self.extrusion.color = color

   @property
   def get_color(self):
       return self.__color

What am I missing? If I were to change this tiny piece of code to use
decorators, for consistency it would seem advisable to change all such
code segments, and I have no idea why this is advisable. Calling the
older scheme "unpythonic" doesn't help me see the light.

Bruce Sherwood

On Tue, Mar 1, 2011 at 11:11 PM, Guy K. Kloss <guy...@au...> wrote:
> On Wed, 02 Mar 2011 06:45:04 Bruce Sherwood wrote:
>> In vis/primitives.py, the code for
>> changing color and material for a text object should look like this:
>>
>>     def set_material(self, material):
>>         self.extrusion.material = material
>>     def get_material(self):
>>         return self.__material
>>
>>     def set_color(self, color):
>>         self.extrusion.color = color
>>     def get_color(self):
>>         return self.__color
>
> Are you *really* sure about that? Python usually does not use the concept of
> getters and setters. This turns out to be *very* unpythonic. I'd rather
> suggest the following:
>
>    @material.setter
>    def material(self, material):
>        self.extrusion.material = material
>
>    @property
>    def material(self):
>        return self.__material
>
>    @color.setter
>    def set_color(self, color):
>        self.extrusion.color = color
>
>    @property
>    def get_color(self):
>        return self.__color
>
> This exposes the given methods to transparently handle access (setting and
> getting) to mock attributes as they would be normally used within Python
> classes. It makes a nice API that is idiomatically consistent to use for a
> Pythoneer.
>
> For further reference on how to use the property() built-in, particularly in
> the way of decorators, have a look here:
>
> http://docs.python.org/library/functions.html#property
>
> Guy
>
> --
> Guy K. Kloss
> School of Computing + Mathematical Sciences
> Auckland University of Technology
> Private Bag 92006, Auckland 1142
> phone: +64 9 921 9999 ext. 5032
> eMail: Guy...@au...
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>

Re: [Visualpython-users] vidle won't launch on WinXP

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

First, you might check that in c:\Python31\Lib\site-packages you do
find these folders: FontTools, numpy, Polygon, ttfquery, vidle, vis,
visual, and the files FontTools.pth and three files ending in
py3.1.egg-info.

Then try this: Click on the round Windows icon, and in the box labeled
"Search programs and files" type "command prompt" to bring up a
typescript, or find this in Accessories on the start menu. Execute "cd
c:\Python31", and type python. You should find yourself in the Python
shell. Type "from visual import *" and report what happens. Or if
there is no complaint, try typing "box()" and see what happens.

Another thing you can do is from Python31 execute "cd
Lib\site-packages\vidle", then execute "c:\Python31\python idle.pyw"
and see whether you can start VIDLE that way.

Bruce Sherwood

On Wed, Mar 2, 2011 at 1:48 PM, Joe Heafner <hea...@gm...> wrote:
> I just installed the very latest Python 3.1 and VPython for Windows XP running under VirtualBox 4.0.4. The VIDLE desktop shortcut won't launch and I also can't launch VIDLE from its home folder. Any suggestions? I've no idea how to troubleshoot Windows.
>
> Joe Heafner
> Sent from one of my Macs
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

[Visualpython-users] vidle won't launch on WinXP

[Joe H. <hea...@gm...>]

I just installed the very latest Python 3.1 and VPython for Windows XP running under VirtualBox 4.0.4. The VIDLE desktop shortcut won't launch and I also can't launch VIDLE from its home folder. Any suggestions? I've no idea how to troubleshoot Windows.

Joe Heafner
Sent from one of my Macs

[Visualpython-users] VPython 5.51

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

Now available at vpython.org is VPython 5.51: Fix memory leak on
Windows and Mac (there was no problem on Linux). Correct errors in
assigning color and material to a text object (Windows, Mac, Linux).

The memory leak on Windows and Mac was due to a misunderstanding of
how to manage the timer queue.

Bruce Sherwood

Re: [Visualpython-users] text color problem?

[Guy K. K. <guy...@au...>]

On Wed, 02 Mar 2011 06:45:04 Bruce Sherwood wrote:
> In vis/primitives.py, the code for
> changing color and material for a text object should look like this:
> 
>     def set_material(self, material):
>         self.extrusion.material = material
>     def get_material(self):
>         return self.__material
> 
>     def set_color(self, color):
>         self.extrusion.color = color
>     def get_color(self):
>         return self.__color

Are you *really* sure about that? Python usually does not use the concept of 
getters and setters. This turns out to be *very* unpythonic. I'd rather 
suggest the following:

    @material.setter
    def material(self, material):
        self.extrusion.material = material

    @property
    def material(self):
        return self.__material

    @color.setter
    def set_color(self, color):
        self.extrusion.color = color

    @property
    def get_color(self):
        return self.__color

This exposes the given methods to transparently handle access (setting and 
getting) to mock attributes as they would be normally used within Python 
classes. It makes a nice API that is idiomatically consistent to use for a 
Pythoneer.

For further reference on how to use the property() built-in, particularly in 
the way of decorators, have a look here:

http://docs.python.org/library/functions.html#property

Guy

-- 
Guy K. Kloss
School of Computing + Mathematical Sciences
Auckland University of Technology
Private Bag 92006, Auckland 1142
phone: +64 9 921 9999 ext. 5032
eMail: Guy...@au...

Re: [Visualpython-users] text color problem?

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

Thanks much for the report. In vis/primitives.py, the code for
changing color and material for a text object should look like this:

    def set_material(self, material):
        self.extrusion.material = material
    def get_material(self):
        return self.__material

    def set_color(self, color):
        self.extrusion.color = color
    def get_color(self):
        return self.__color

These corrections will of course be in the next update to VPython. I
also found a mistake in text.starts, but that's less used.

History: The year-old 3D text object had a component to convert text
to contours, and Python code to generate faces objects to render the
3D text. With the new extrusion object also needing to be able to
convert text to contours, that subroutine was split out as
shapes.text() and the text and extrusion objects both call
shapes.text(). In the process of doing this restructuring I failed to
change the setters for text.color and text.material. Note that the
text object creates an extrusion object, but this doesn't make the
text object obsolete, because it places emphasis on such things as
upper left and lower right locations, etc.

Bruce Sherwood

On Tue, Mar 1, 2011 at 2:54 AM, Symion <kn...@ip...> wrote:
> I have been exploring the Text object a little more and may have found a
> bug.
> I may not be using the text object correctly but I receive the following
> error when changing text color.
>
> from visual import *
>  words = text(text="Test")
>  words.color=(1,0,0)
>
> Traceback (most recent call last):
>   File "<pyshell#118>", line 1
>     words.color=(1,0,0)
>   File "C:\Python27\lib\site-packages\vis\primitives.py", line 945, in
> set_color
>     for line in range(len(self.lines)):
> AttributeError: 'text' object has no attribute 'lines'
>
> The same error occurs with.
>
> words.starts.__class__
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

[Visualpython-users] text color problem?

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

I have been exploring the Text object a little more and may have found a 
bug.
I may not be using the text object correctly but I receive the following 
error when changing text color.

from visual import *
  words = text(text="Test")
  words.color=(1,0,0)

Traceback (most recent call last):
   File "<pyshell#118>", line 1
     words.color=(1,0,0)
   File "C:\Python27\lib\site-packages\vis\primitives.py", line 945, in 
set_color
     for line in range(len(self.lines)):
AttributeError: 'text' object has no attribute 'lines'

The same error occurs with.

words.starts.__class__

Re: [Visualpython-users] what has happened to string.lower?

[Peter B. <p.h...@bh...>]

Thank you to those who replied

>>> a = "HELLO"
>>> a.lower()
'hello'

Regards

Peter

P H Borcherds  +44 [0] 121 475 3029
________________________________
From: P H Borcherds [p.h...@bh...]
Sent: 25 February 2011 15:02
To: vpython
Subject: what has happened to string.lower?

In python 2.etc there is a useful function: string.lower which converts a
string into lower case. eg string.lower("ACE") returns 'ace'

in python 3.1 the string module no longer has any such function,

Please can anyone let me know if such a function exists in 3.1 and where it
is to be found

Regards

Peter
P H Borcherds   phone +44  121 475 3029
p.h...@bh...

Re: [Visualpython-users] what has happened to string.lower?

[James M. <mu...@pi...>]

It's a string method now.

word = "ACE"
word.lower()

On Feb 25, 2011, at 10:02 AM, P H Borcherds wrote:

> In python 2.etc there is a useful function: string.lower which converts a 
> string into lower case. eg string.lower("ACE") returns 'ace'
> 
> in python 3.1 the string module no longer has any such function,
> 
> Please can anyone let me know if such a function exists in 3.1 and where it 
> is to be found
> 
> Regards
> 
> Peter
> P H Borcherds   phone +44  121 475 3029
> p.h...@bh... 
> <myself.vcf><ATT00001..txt><ATT00002..txt>

[Visualpython-users] what has happened to string.lower?

[P H B. <p.h...@bh...>]

In python 2.etc there is a useful function: string.lower which converts a 
string into lower case. eg string.lower("ACE") returns 'ace'

in python 3.1 the string module no longer has any such function,

Please can anyone let me know if such a function exists in 3.1 and where it 
is to be found

Regards

Peter
P H Borcherds   phone +44  121 475 3029
p.h...@bh... 

Re: [Visualpython-users] vPython for Windows x64?

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

It's good to hear that you've found VPython useful. Thanks for the comments.

Someone else asked about 64-bit support just a few days ago, and I'll
reproduce below my response to the question. Certainly there will be
support for 64-bit systems, but it hasn't been as high a priority as
other matters, since performance is quite good in 32-bit mode on
Windows. Note that VPython is open source, so anyone can try building
for a 64 bit environment should they wish to do so.

Bruce Sherwood

-----------------------------------------
It's true that support for 64-bit machines is relevant, not just on
Windows but also on Mac and Linux. VPython programs run nicely as
32-bit programs on Windows, so it's not an urgent problem. Perhaps
more of an issue is that people have had difficulties trying to build
VPython from source on 64-bit Linux.

But the really big scary menacing problem is the Mac. For important
reasons, VPython uses the Carbon framework on the Mac (for creating a
window and interacting with it). Carbon will not be available on
64-bit Macs, and Cocoa for major threading reasons poses a serious
implementation challenge. Whether Apple goes completely to 64 bits, or
Python becomes available for the Mac only as a 64-bit program, VPython
as a pure Mac program is dead unless someone can figure out how to run
it in the Cocoa environment. An out presumably is to retreat to what
used to be the case, that VPython would run only within the X11 world
on the Mac, not as a native-mode application. That's a problem,
because many Mac users were very uncomfortable with that approach when
we used it in the past.

On Thu, Feb 24, 2011 at 3:02 PM, Dave Lindbergh
<dav...@gm...> wrote:
> vPython is great!
>
> I'm new to Python (coming from MATLAB) and was delighted to see how
> easily I can visualize my simulations.
>
> Is there any chance of a vPython build that works with 64-bit Python
> (I'm on 2.7.1) on Windows?  The current vPython only seems to work in
> x86 (32 bit) mode.
>
> Cheers,
>
> --Dave

[Visualpython-users] vPython for Windows x64?

[Dave L. <dav...@gm...>]

vPython is great!

I'm new to Python (coming from MATLAB) and was delighted to see how 
easily I can visualize my simulations.

Is there any chance of a vPython build that works with 64-bit Python 
(I'm on 2.7.1) on Windows?  The current vPython only seems to work in 
x86 (32 bit) mode.

Cheers,

--Dave