headers
Simon Burton | 1 Aug 2006 06:04

wiki links


Please Please Please link to the wiki from code.enthought.com !

Also Please Please put a link to https://svn.enthought.com/enthought/wiki/GrabbingAndBuilding from
the svn page:
http://code.enthought.com/svn.shtml

Unless you are _trying_ to hide the wiki ?

Simon.

--

-- 
Simon Burton, B.Sc.
Licensed PO Box 8066
ANU Canberra 2601
Australia
Ph. 61 2 6249 6940
http://arrowtheory.com
Permalink | Reply | 4 comments |
headers
Peter Wang | 1 Aug 2006 17:07

Re: Can envisage.get_application be used?

Jason Sugg wrote ..
> so enthought-dev is now our official means of internal technology 
> communications? i read it sometimes, but there's a lot of cruft that i
> skip over. if there are going to be official pronouncements like this
> then they need to be directed to another forum like, say, 
> science-developers?

I think it's appropriate to keep it on enthought-dev, but I agree that
such a significant change should be more visibly announced.  I follow most
of the discussions on enthought-dev but didn't actually realize that get_application()
was deprecated.  (And apparently I'm not the only one: there are 52 references
to it in cp.lab alone!)

-Peter
Permalink | Reply | 501 comments |
headers
Bryce Hendrix | 1 Aug 2006 17:20

Re: wiki links

Did someone already update the pages, because I see links to all but the 
GrabbingAndBuilding page? The text associated with the links could 
probably be more explicit, of course.

If no one else objects or wants to do it, I'll clean up the web site a 
little this week when I announce the 1.0.0 release.

Bryce

Simon Burton wrote:
> Please Please Please link to the wiki from code.enthought.com !
>
> Also Please Please put a link to https://svn.enthought.com/enthought/wiki/GrabbingAndBuilding from
> the svn page:
> http://code.enthought.com/svn.shtml
>
> Unless you are _trying_ to hide the wiki ?
>
> Simon.
>
>
Permalink | Reply | 0 comments |
headers
Peter Wang | 1 Aug 2006 17:29

Re: wiki links

Bryce Hendrix wrote ..
> Did someone already update the pages, because I see links to all but the
> GrabbingAndBuilding page? The text associated with the links could 
> probably be more explicit, of course.
           ^^^^^^^^^^^^^^^^

I think this is the key problem...  It would be great the migrate the content from the GrabbingAndBuilding
page to the code.enthought.com page.

I would like to update the content for the Chaco page as well, and coordinate it with the information on the
chaco wiki so that there is a logical division of what is where.  I can edit the wiki very easily, but the
code.enthought.com site not at all...

Who is in charge of the code.enthought web pages?  Is it you, or Travis, or... Jeff Marshall perhaps? :)

-Peter
Permalink | Reply | 0 comments |
headers
Prabhu Ramachandran | 1 Aug 2006 17:44
Picon
Gravatar

Re: wiki links

>>>>> "Simon" == Simon Burton <simon@...> writes:

    Simon> Please Please Please link to the wiki from
    Simon> code.enthought.com !

Isn't it there already -- it is listed as "Development Home" or do you
want it to be explicitly mentioned?

cheers,
prabhu
Permalink | Reply | 2 comments |
headers
Dave Peterson | 1 Aug 2006 17:57

Re: Can envisage.get_application be used?

I hear your complaints, and I've thought the same things myself. 
Verbally doesn't cut it because people may not have been present or can 
too easily forget.  The mailing list isn't quite appropriate either, 
though it is better than anything else we have at the moment.  Having a 
better form of communicating our standard coding practices is something 
I'll be working on as soon as I can roll off of P&G dev tasks.

Once that is established though, I'll be expecting people to actually 
conform to those standard coding practices!

-- Dave

Peter Wang wrote:
> Jason Sugg wrote ..
>> so enthought-dev is now our official means of internal technology 
>> communications? i read it sometimes, but there's a lot of cruft that i
>> skip over. if there are going to be official pronouncements like this
>> then they need to be directed to another forum like, say, 
>> science-developers?
> 
> I think it's appropriate to keep it on enthought-dev, but I agree that
> such a significant change should be more visibly announced.  I follow most
> of the discussions on enthought-dev but didn't actually realize that get_application()
> was deprecated.  (And apparently I'm not the only one: there are 52 references
> to it in cp.lab alone!)
> 
> 
> -Peter
> 
>
(Continue reading)

Permalink | Reply | 502 comments |
headers
Bryce Hendrix | 1 Aug 2006 18:39

Re: Can envisage.get_application be used?

Not that this would solve the problem, but someone recommended a blog to 
summarize key happenings inside Enthought. We definitely need to clarify 
our communication with customers and open source contributers, a blog 
could go a long way towards this goal if its properly maintained.

Bryce

Dave Peterson wrote:
> I hear your complaints, and I've thought the same things myself. 
> Verbally doesn't cut it because people may not have been present or 
> can too easily forget.  The mailing list isn't quite appropriate 
> either, though it is better than anything else we have at the moment.  
> Having a better form of communicating our standard coding practices is 
> something I'll be working on as soon as I can roll off of P&G dev tasks.
>
> Once that is established though, I'll be expecting people to actually 
> conform to those standard coding practices!
>
> -- Dave
>
> Peter Wang wrote:
>> Jason Sugg wrote ..
>>> so enthought-dev is now our official means of internal technology 
>>> communications? i read it sometimes, but there's a lot of cruft that i
>>> skip over. if there are going to be official pronouncements like this
>>> then they need to be directed to another forum like, say, 
>>> science-developers?
>>
>> I think it's appropriate to keep it on enthought-dev, but I agree that
>> such a significant change should be more visibly announced.  I follow
(Continue reading)

Permalink | Reply | 7 comments |
headers
Prabhu Ramachandran | 1 Aug 2006 19:06
Picon
Gravatar

Re: How to add an ImagetracerWidget to Mayavi ?

>>>>> "Daniel" == Daniel Kornhauser <kornhauser@...> writes:

    Daniel> I want to use an ImagetracerWidget with mayavi2 in a such
    Daniel> way that it would give me the points from a region of
    Daniel> interest traced over a ImagePlaneWidget.

    Daniel> Am I out of my mind or is there a way to achieve this?

    Daniel> Can somebody hint me an overview of the steps to take?

I haven't used the ImagetracerWidget but from what I can see it
requires a vtkProp to operate on.  The ImagePlaneWidget does not
provide any methods to get the vtkProp it creates (the
TexturePlaneActor ivar).

However, you can get hold of the actor from the scene.  I just tested
this using examples/numeric_source.py and the python shell:

>>> dragged # Dragged the second IPW.
<enthought.mayavi.modules.image_plane_widget.ImagePlaneWidget object at 0xad3d323c>
>>> ipw = _
>>> ipw.interaction = 0 # Turn off interaction for the IPW.
>>> tvtk_scene_1 # Drag the scene to script it.
<enthought.mayavi.core.scene.Scene object at 0xafbd90bc>
>>> s = _
>>> a = s.scene.renderer.actors
>>> act = a[-3] # This lets you get to the actor added by the IPW! Ugly but works.
>>> act.visibility = 0 # Test if we have the right actor
>>> act.visibility = 1
>>> from enthought.tvtk.api import tvtk
(Continue reading)

Permalink | Reply | 2 comments |
headers
Prabhu Ramachandran | 1 Aug 2006 19:08
Picon
Gravatar

Re: Can envisage.get_application be used?

>>>>> "Bryce" == Bryce Hendrix <bhendrix@...> writes:

    Bryce> Not that this would solve the problem, but someone
    Bryce> recommended a blog to summarize key happenings inside
    Bryce> Enthought. We definitely need to clarify our communication
    Bryce> with customers and open source contributers, a blog could
    Bryce> go a long way towards this goal if its properly maintained.

We have 3 positive votes for a blog now.  The key though is the
"properly maintained" part. :)

cheers,
prabhu
Permalink | Reply | 6 comments |
headers
Daniel Kornhauser | 1 Aug 2006 22:44

Re: How to add an ImagetracerWidget to Mayavi ?

Thanks Prabhu, works like a charm.

An unrelated question:
    Is there currently a problem with the tvtk gui ?
    I get an empty frame when I click on my ImagePlaneWidget to edit the 
properties ...

                                           Daniel

Prabhu Ramachandran wrote:
>>>>>> "Daniel" == Daniel Kornhauser <kornhauser@...> writes:
>>>>>>             
>
>     Daniel> I want to use an ImagetracerWidget with mayavi2 in a such
>     Daniel> way that it would give me the points from a region of
>     Daniel> interest traced over a ImagePlaneWidget.
>
>     Daniel> Am I out of my mind or is there a way to achieve this?
>
>     Daniel> Can somebody hint me an overview of the steps to take?
>
> I haven't used the ImagetracerWidget but from what I can see it
> requires a vtkProp to operate on.  The ImagePlaneWidget does not
> provide any methods to get the vtkProp it creates (the
> TexturePlaneActor ivar).
>
> However, you can get hold of the actor from the scene.  I just tested
> this using examples/numeric_source.py and the python shell:
>
>
(Continue reading)

Permalink | Reply | 1 comment |

Gmane