fred | 1 Jan 23:55
Picon

Re: file for lut

Prabhu Ramachandran a écrit :

>The standard LUTs are defined in mayavi/core/lut_manager.py.  The
>_lut_mode_changed method sets up the lut.
>  
>
Hi, and happy new year.

Ok, so I try to use wx_gradient_editor.py, but can't add some points,
clicking on the right button.

I get the following message:
Traceback (most recent call last):
  File
"/usr/local/src/enthought/src/lib/enthought/tvtk/util/wx_gradient_editor.py",
line 379, in on_right_button_up
    new_control_point.color =
self.table.get_pos_color(new_control_point.pos)
AttributeError: GradientTable instance has no attribute 'get_pos_color'

Any suggestion ?

Cheers,

--

-- 
http://scipy.org/FredericPetit
Picon
Gravatar

Re: file for lut

>>>>> "fred" == fred  <fredmfp@...> writes:

    fred> Ok, so I try to use wx_gradient_editor.py, but can't add
    fred> some points, clicking on the right button.
[...]
    fred> Any suggestion ?

Its a bug and I've checked in the fix.  Thanks for the report.

cheers,
prabhu
fred | 2 Jan 14:22
Picon

Re: file for lut

Prabhu Ramachandran a écrit :

>>>>>>"fred" == fred  <fredmfp@...> writes:
>>>>>>            
>>>>>>
>
>    fred> Ok, so I try to use wx_gradient_editor.py, but can't add
>    fred> some points, clicking on the right button.
>[...]
>    fred> Any suggestion ?
>
>Its a bug and I've checked in the fix.  Thanks for the report.
>  
>
Thanks.

Well, let's see if I understand right...
In lut_manager.py,
hue (red line in wx_gradient_editor.py) decreases from 0.6667 to 0,
following a sqrt func,
saturation (green line in w_g_e.py) is constant and equals to 1,
value (blue line in w_g_e.py) is constant and equals to 1.

So I have to set points (how many ? 5 ? more ?) to the red line that
follows a sqrt func, between 0.6667 and 0,
in order to get the same color bar as the lut color bar.

Am I right ?

Cheers,
(Continue reading)

Picon
Gravatar

Re: file for lut

>>>>> "Fred" == fred  <fredmfp@...> writes:

    Fred> Well, let's see if I understand right...  In lut_manager.py,
    Fred> hue (red line in wx_gradient_editor.py) decreases from
    Fred> 0.6667 to 0, following a sqrt func, saturation (green line
    Fred> in w_g_e.py) is constant and equals to 1, value (blue line
    Fred> in w_g_e.py) is constant and equals to 1.

    Fred> So I have to set points (how many ? 5 ? more ?) to the red
    Fred> line that follows a sqrt func, between 0.6667 and 0, in
    Fred> order to get the same color bar as the lut color bar.

I think that sounds correct but I am not sure.  You will have to take
a look at the VTK implementation to really check -- or experiment and
see.  I would suggest the reverse approach -- create a LUT using
w_g_e.py and use that as the default for your module manager.

BTW, I am going to be out of station till the weekend so am unlikely
to respond before that.

cheers,
prabhu
fred | 2 Jan 17:39
Picon

Re: file for lut

Prabhu Ramachandran a écrit :

>I think that sounds correct but I am not sure.  You will have to take
>a look at the VTK implementation to really check -- or experiment and
>see.  I would suggest the reverse approach -- create a LUT using
>w_g_e.py and use that as the default for your module manager.
>
>  
>
I agree, but unhappily, this is really the reverse problem I would like 
to fix : I want to
set a LUT equals to the default LUT.
I recall my problem ;-) : I want the same color bar for the Volume 
module as the default LUT,
and not the opposite. Simply because it's nicer, imho. ;-)

Before you have fixed some bugs in w_g_e.py, default color bar was set 
to the default LUT,
(changeset 9761, IIRC), in reverse, in fact, because red color was for 
low values, blue for high.
This was almost good ;-)

After fixed these bugs, default color bar has been set equal to
the Volume module color bar, so not equal to the default LUT, that I wanted.
Thus I could have set the Volume color bar to the default LUT easily.

>BTW, I am going to be out of station till the weekend so am unlikely
>to respond before that.
>  
>
(Continue reading)

Janet Swisher | 2 Jan 17:53

Re: Contributing a view to MayaVi2 (was Re: Envisage basics)

Prabhu Ramachandran wrote:
> Thats all I have time for this year.  It would be great if my
> ramblings above, the code and so on were put up on the Wiki for all to
> read and change if needed.
>   
I've made a ticket and assigned it to myself: 
https://svn.enthought.com/enthought/ticket/972

--

-- 
Janet Swisher --- Senior Technical Writer
Enthought, Inc. http://www.enthought.com
Dave Peterson | 2 Jan 21:16

Re: repository plugin

Hi Eli,

It definitely sounds like the repository plugin in 
enthought.envisage.repository will fit your needs well. Here is my 
rundown of the plugin's features:

* Allows for multiple, hierarchical repositories, the locations of which 
are specified through contributions to the plugin's Envisage extension 
point. There are contributions that can be used to pass locations from 
environment variables, from config files, and from hardcoded strings, 
into the plugin.

* Currently all repositories are file-system based, but we think it 
shouldn't be too difficult to extend to database stores, webdav stores, 
version-control stores, etc.

* Includes GUIs, with a tree-view of the repositories, for importing and 
exporting. The importing GUI includes a mechanism for a preview of the 
currently selected resource within the repository.

* The import API requires the programmer to provide a ResourceType 
representing the type of resource to be imported. The plugin uses 
information on this type to filter the displayed items in the import 
tree to only those that are of the appropriate type within the 
repositories. Likewise, information on this type provides the mechanism 
to use to preview a selected resource.

Unfortunately, I haven't actually written code to use the plugin in 
myself so I can't give any first-hand pointers, though I have put some 
thoughts inline with your requests anyway. The author of the plugin, 
(Continue reading)

Dave Kammeyer | 2 Jan 21:53

Interesting article

Some of you might find this interesting -- it is some thoughts on levels 
of customer interaction based vs. levels of innovation required.  
Perhaps something others have already thought about, but I found it 
quite interesting.

http://www.zedshaw.com/essays/c2i2_hypothesis.html
Paul Waddell | 3 Jan 20:34

PyTables

I see that PyTables is included in the Enthought release  of Python, but 
am unclear how much has been done to integrate this into the Enthought 
Tool Suite.  Has it been adapted to use Traits?  Or is there any work to 
develop an Envisage plugin for it?  This would be very interesting to see.

Paul
Dave Peterson | 3 Jan 22:26

Re: PyTables

Hi Paul,

I'm not 100% sure on these answers but I'll answer anyway since I have 
confidence someone will correct me if I'm wrong. :-)

I don't think we've done anything to integrate PyTables into a Traits 
world, nor have we setup an Envisage plugin. I'm not even sure what an 
Envisage plugin would look like for this. Perhaps we could integrate 
storage, using PyTables, into our repository plugin though. What were 
you hoping to see for a plugin?

-- Dave

Paul Waddell wrote:
> I see that PyTables is included in the Enthought release  of Python, but 
> am unclear how much has been done to integrate this into the Enthought 
> Tool Suite.  Has it been adapted to use Traits?  Or is there any work to 
> develop an Envisage plugin for it?  This would be very interesting to see.
>
> Paul
>
> _______________________________________________
> Enthought-dev mailing list
> Enthought-dev@...
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>   

Gmane