gmane.comp.python.enthought.devel

Re: no examples or docs installing ETSviaeasy_install

Mary Lou Knack — 2008-12-03T23:20:52

_______________________________________________ Enthought-dev mailing list Enthought-dev-oRDGkvazHdacsI7C1d+pp9BPR1lH4CV8< at >public.gmane.org https://mail.enthought.com/mailman/listinfo/enthought-dev

Re: [mv2] Object editor fails for some modules

Prabhu Ramachandran — 2008-12-03T20:47:54

[...] This is now fixed in SVN and all tests should pass. Turns out this was a bug with VTK-5.2 that I've worked around. It helped that I had a machine that built VTK in 4 minutes flat. :) Thanks for the report and patience. cheers, prabhu

Re: [TraitsBackendWX] Text Range editor improvement

Prabhu Ramachandran — 2008-12-03T20:43:15

Thanks, I found an easier patch for this (enclosed below). However, there is another irritating bug. Try this: from enthought.traits.api import * class A(HasTraits): r = Range(3L, 100000000000L) def _anytrait_changed(self): print "change" a = A() a.configure_traits() Now change the value of r on the UI to 1 say and you'll see very interesting behavior that I don't see how to fix. Anyway, I am checking in my one liner patch. cheers, prabhu Index: enthought/traits/ui/wx/editor_factory.py =================================================================== --- enthought/traits/ui/wx/editor_factory.py (revision 22624) +++ enthought/traits/ui/wx/editor_factory.py (working copy) < at >< at > -132,7 +132,8 < at >< at > """ Finishes initializing the editor by creating the underlying toolkit widget. """ - self.control = wx.TextCtrl( parent, -1, self.str_value ) + self.control = wx.TextCtrl( parent, -1, self.str_value, +

Re: Missing envisage docs on wiki

Janet Swisher — 2008-12-03T18:02:00

Yup, they were pointing to an outdated SVN location. Fixed those two, plus "Plugins".

Re: Missing envisage docs on wiki

Janet Swisher — 2008-12-03T17:26:16

Probably an issue of the links between the two. I'll look into it. Envisage 2 or Envisage 3?

Re: on_trait_change problems

Judah De Paula — 2008-12-03T14:24:20

I just checked "Getting Started with Enthought 3.x Technologies" wiki tutorial page and it was not using super(), but still worked since the xxx_changed() pattern was being followed. I've updated the tutorial. A couple of other tutorials I just looked at don't use __init__() at all, instead using xxx_default() to set up initial values. Since many demos don't overload __init__() the super() pattern may tend to be forgotten. I vaguely remember having the same problem myself when I first starting using the Traits decorators. I'm guessing there are a number of other ETS 2.x examples and tutorials out there that don't use super() because it wasn't necessary when decorators were not in effect. I did not attend this year, but I did attend back in '07. Cheers, Judah

Re: [mv2] Filter UserDefined:ImageMathematics on Windows

B. P. Thrane — 2008-12-03T14:17:27

Here is a new example that produces the attached image when adding ImagePlaneWidget, Glyph and ScalarCutPlane. The very season friendly christmas tree colors of the ImagePlaneWidget tells a different story from the ScalarCutPlane and Glyphs, which seem to be correct. When flipping between the 3 arrays in the source, the glyphs and ScalarCutPlane are updated, but the output from ImagePlaneWidget is randomized. from numpy import array, zeros from enthought.tvtk.api import tvtk from enthought.mayavi.sources.vtk_data_source import VTKDataSource o = zeros(27) for n in range(27): o[n] = (1+float(n))/10.0 i = o+1 m = o+2 p = tvtk.ImageData(dimensions=[3,3,3],spacing=[1,1,1], scalar_type='float') p.point_data.allocate_arrays(3) j1 = p.point_data.add_array(o) p.update() p.point_data.get_array(j1).name='first' p.update() j2 = p.point_data.add_array(i) p.update() p.point_data.get_array(j2).name='second' p.update() j3 = p.point_data.add_array(m) p.update() p.point_data.get_array(j3).name='third' p.update()

Re: on_trait_change problems

Charles McCreary — 2008-12-03T14:07:15

Re: on_trait_change problems

Judah De Paula — 2008-12-03T13:58:34

Hi Charles, There's been a spate of questions recently regarding the use of super() in __init__(). How did you learn about decorators and what would have helped to avoid this for future users? Thank you, Judah Robert Kern wrote:

Re: no examples or docs installing ETS viaeasy_install

Gary Pajer — 2008-12-03T13:38:39

On Wed, Dec 3, 2008 at 1:06 AM, Gael Varoquaux public.gmane.org> wrote: I'm not sure I know exactly what you mean, and I'm suspicious that you might be thinking of mayavi (?). ("menu entry" makes me think of the drop down menus of a GUI.) What comes to mind is something like a tarball that has the examples and docs. Be aware that I have no idea what the issues would be to implement such a thing. Honestly, what I do now works fine for me. I'm really thinking of people who are new to ETS. They do an easy_install, and then wonder where the docs are. They might find docs and help on the web, but they won't find examples. -gary

Re: Installing ETS-3.0.3 in Sage

Jaap Spies — 2008-12-03T13:36:26

[...] Ok, you have your point. I was speaking too early (before I studied the sources!). [...] On second thoughts I think the maintainers of the numpy.spkg are to blame here by the introduction the [DEFAULT] in the site.cfg. Thanks for making this clear. Jaap

Re: [mv2] Filter UserDefined:ImageMathematics on Windows

B. P. Thrane — 2008-12-03T13:27:29

Sorry about the bad example below, the arrays are not long enough, need 27 samples, not 9, and the scrambling in the attached image can also be due to incomplete array initialisation. I need to prepare a better example.

Re: [TraitsBackendWX] Text Range editor improvement

Vibha Srinivasan — 2008-12-03T12:31:02

Looks ok to me, Prabhu. You can check it in. (Also, thanks for checking in the fix to the range editor for large ranges). Vibha.

Re: [mv2] Filter UserDefined:ImageMathematics on Windows

B. P. Thrane — 2008-12-03T09:28:47

OK, then I need to do the math on the object in the import filter, which means I need to make a ImageData source with several scalar arrays. But I get problems with building up a StructuredPoints/ImageData source object with several arrays, similar to the first problem I sent you Prabhu. Now here is an example that should illustrate the problem: from numpy import array from enthought.tvtk.api import tvtk from enthought.mayavi.sources.vtk_data_source import VTKDataSource o = [0,0,0,0,0,0,0,0,0] i = [1,1,1,1,1,1,1,1,1] p = tvtk.ImageData(dimensions=[3,3,3],spacing=[1,1,1]) j1 = p.point_data.add_array(o) p.point_data.get_array(j1).name='zeros' j2 = p.point_data.add_array(i) p.point_data.get_array(j2).name='ones' p.update() src = VTKDataSource(data=p) mayavi.add_source(src, scene=None) Now, you should get a VTK Data(ImageData) source in the tree editor. In the 'Point scalars name' drop down menu there are two entries, 'zeros' and 'ones'. Now if I create an ImagePlaneWidget I get scrambled data, a mix of

Re: [mv2] LUT, ImagePlaneWidget and custom import module

B. P. Thrane — 2008-12-03T08:51:38

Yes, I tried that like this, but that should be the same. r = tvtk.StructuredPoints(origin=zzz.origin(),dimensions=zzz.dims(), spacing=zzz.spacing(), scalar_type='float') Well since this is not a fatal error, I will leave it. I still think this may be related to the fact that ImagePlaneWidget inherits the lookup table if present, but also has it's own. Regards, Bård

Re: on_trait_change problems

Robert Kern — 2008-12-03T06:17:01

On Tue, Dec 2, 2008 at 18:00, Charles McCreary public.gmane.org> wrote: You cannot override __init__ without calling HasTraits.__init__(). It will set up the machinery that < at >on_trait_change() uses.

on_trait_change problems

Charles McCreary — 2008-12-03T00:00:04

Re: no examples or docs installing ETSviaeasy_install

Gael Varoquaux — 2008-12-03T06:06:23

Would a download menu entry be a solution that satisfies you? Gaël

Re: Installing ETS-3.0.3 in Sage

Robert Kern — 2008-12-02T23:08:21

No, you haven't. If you present an alternative that works better, I am happy to concede the point. Build configuration across many disparate platforms is simply a hard problem. Demonstrating that one approach has issues does not mean that there are other approaches which are free of such issues. We're using numpy.distutils to build Enable for several other reasons (not least that the extension modules use numpy). That configuration mechanism happened to be there, so we are using it. Ultimately, it gives the person installing complete control via ~/.numpy-site.cfg, but it does sacrifice some automatic assumptions that might be made. If you would like to contribute some extra intelligence to the code, please do so.

Missing envisage docs on wiki

Gary Pajer — 2008-12-03T00:17:59

Re: no examples or docs installing ETS viaeasy_install

Gary Pajer — 2008-12-03T00:13:14