scribbling tool (eg for labeling markers)

Steven,

I would love to get to as much of that functionality into mpl proper
as possible. Please open an issue / make a MEP for this.

Unfortunately I have not had a chance to take a close look at
image_inspector yet and I am a tad concerned about the potential for
re-invented wheels between yours tools and the existing widgets (and
to be fair, I only have a cursory understanding of those widgets). I
agree all the functionality should be in mpl (or as much as we can
shove down through our gui frame work independent filter), but don't
want to get pinned down to committing to specific implementation
details.

Another option might be to put all of these tools in a sibling repo to
mpl under the mpl organization.

I have cc'd the mpl-dev list.

Tom

···

On Thu, Sep 4, 2014 at 9:28 PM, Steven Silvester <steven.silvester@...149...> wrote:

Thomas,

How about the broader discussion of incorporating the tools in
https://github.com/blink1073/image_inspector into mpl (ideally as a
replacement or alternative for some of the existing tools)? If I combine
that with paint tool and we get those pushed into mpl proper, then we can
just use them as-is for skimage. Should I open an mpl issue to discuss?

- Steve

On Thursday, September 4, 2014 4:49:28 PM UTC-5, Thomas Caswell wrote:

If you are doing this with matplotlib, can you actually push the tools
back upstream?

Tom (a mpl dev)

On Thu, Sep 4, 2014 at 5:36 PM, Stéfan van der Walt <ste...@...1216.....> >> wrote:
> On Thu, Sep 4, 2014 at 10:01 PM, Emmanuelle Gouillart >> > <emmanuelle...@...1215...> wrote:
>> Answering my own question: I had forgotten that the viewer examples
>> include such kind of example, inside watershed_demo.py. Thanks Tony
>> for the example!
>
> I think this is an important enough use-case to make it a utility
> function--feel free to add an issue!
>
> Stéfan
>
> --
> You received this message because you are subscribed to the Google
> Groups "scikit-image" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to scikit-image...@...605...
> For more options, visit https://groups.google.com/d/optout.

--
Thomas Caswell
tcas...@...149...

--
You received this message because you are subscribed to the Google Groups
"scikit-image" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to scikit-image+unsubscribe@...605...
For more options, visit https://groups.google.com/d/optout.

--
Thomas Caswell
tcaswell@...149...

Steven

I just had a look at image_inspector.
The Tools (in mpl jargon are widgets) look great.

Some replicate what we already have but more modern (for me this is positive improvement).

Regarding the roi_inspector, this is a great fit for MEP22 tools (Almost done).

My suggestion would be to take a look at matplotlib.widgets.Widget and matplotlib.widgets.AxesWidget to see how easy/hard would it be to adapt or integrate your tools (widgets) there.

Personally I don’t like the idea of a separate sibling repo. It makes just things more confusing.

Federico

···

On 4 Sep 2014 23:42, “Thomas Caswell” <tcaswell@…149…> wrote:

Steven,

I would love to get to as much of that functionality into mpl proper

as possible. Please open an issue / make a MEP for this.

Unfortunately I have not had a chance to take a close look at

image_inspector yet and I am a tad concerned about the potential for

re-invented wheels between yours tools and the existing widgets (and

to be fair, I only have a cursory understanding of those widgets). I

agree all the functionality should be in mpl (or as much as we can

shove down through our gui frame work independent filter), but don’t

want to get pinned down to committing to specific implementation

details.

Another option might be to put all of these tools in a sibling repo to

mpl under the mpl organization.

I have cc’d the mpl-dev list.

Tom

On Thu, Sep 4, 2014 at 9:28 PM, Steven Silvester > > <steven.silvester@…714…> wrote:

Thomas,

How about the broader discussion of incorporating the tools in

https://github.com/blink1073/image_inspector into mpl (ideally as a

replacement or alternative for some of the existing tools)? If I combine

that with paint tool and we get those pushed into mpl proper, then we can

just use them as-is for skimage. Should I open an mpl issue to discuss?

  • Steve

On Thursday, September 4, 2014 4:49:28 PM UTC-5, Thomas Caswell wrote:

If you are doing this with matplotlib, can you actually push the tools

back upstream?

Tom (a mpl dev)

On Thu, Sep 4, 2014 at 5:36 PM, Stéfan van der Walt <ste…@…337…> > > >> wrote:

On Thu, Sep 4, 2014 at 10:01 PM, Emmanuelle Gouillart > > >> > <emmanuelle…@…1215…> wrote:

Answering my own question: I had forgotten that the viewer examples

include such kind of example, inside watershed_demo.py. Thanks Tony

for the example!

I think this is an important enough use-case to make it a utility

function–feel free to add an issue!

Stéfan

You received this message because you are subscribed to the Google

Groups “scikit-image” group.

To unsubscribe from this group and stop receiving emails from it, send

an email to scikit-image…@…614…

For more options, visit https://groups.google.com/d/optout.

Thomas Caswell

tcas…@…149…

You received this message because you are subscribed to the Google Groups

“scikit-image” group.

To unsubscribe from this group and stop receiving emails from it, send an

email to scikit-image+unsubscribe@…614…

For more options, visit https://groups.google.com/d/optout.

Thomas Caswell

tcaswell@…149…


Slashdot TV.

Video for Nerds. Stuff that matters.

http://tv.slashdot.org/


Matplotlib-devel mailing list

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel