embed in traits?

[GoogleCodeExporter]

Any possibility of embedding in Traits (Enthought)?

Original issue reported on code.google.com by geovis...@gmail.com on 10 Jul 2011 at 11:35

[GoogleCodeExporter]

What do you mean by that? That you can "use" properties of visvis objects as 
treats?

Original comment by almar.klein@gmail.com on 11 Jul 2011 at 5:14

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I use Enthought's Traits for my GUI (with a wx backend under that). Mayavi can 
be be embedded in a Traits GUI so my suggestion was to look at something 
similar for visvis.

Original comment by geovis...@gmail.com on 12 Jul 2011 at 9:03

[GoogleCodeExporter]

It's just that although I do know approximately what Traits are, I've never 
actually worked with them, so I'm not sure what it means if visvis were 
embedded in a Traits GUI.

Could you tell me a bit more about what this means in practice (for you as a 
user)?

Traits seem like a good idea, so you've got my attention (although I might not 
rate it a very high priority right now).

Original comment by almar.klein@gmail.com on 12 Jul 2011 at 9:34

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Sent an email reply to visvis@googlecode.com with an image attached but don't 
know whether that got through or not so here it is again...

I find Traits gives you the ability to create a high quality GUI while coding 
at a high level. I don't require any low level wx or Qt knowledge. Obviously 
this is all leveraging the excellent work that the Enthought developers and 
some other key open source developers (Gael Varoquaux etc.) have done. I've 
attached a screenshot which shows the type of GUI I can build with a Mayavi 
view embedded.

Original comment by geovis...@gmail.com on 13 Jul 2011 at 9:03

Attachments:

• Traits.png

[GoogleCodeExporter]

Mmm, I've also checked out some examples on the web, and it looks like 
something really useful. Also to visvis, because visvis already makes good use 
of properties. 

One condition that I have, is that visvis should not depend on it. So it should 
like check if Traits is installed and "embed" it if it is.

I do not have time to dive into this, but maybe you can get some stuff started? 
For instance some example code that defines an object that would dynamically be 
Trait-able if Traits is installed and behave normally if it isnt. Something 
like a demonstration that its possible. Me or Robert can then later join you 
and make it work for visvis.

If you have the time, that is. If not, I'll leave this open and someone will 
start working on this in the future.

Original comment by almar.klein@gmail.com on 14 Jul 2011 at 7:09

• Changed state: Accepted