matplotlib-devel Mailing List for matplotlib

It would be great if we can see the code for the style system.
However, for integration into MPL, rather than something which 'sits on top'
of the existing API (I presume you are therefore working with getter/setter
functions), the MEP I'm proposing is also trying to achieve the seperation
of the 'style' of artists from their data/logic. The idea being that it
heads towards a more streamlined and extensible API. 
Some of the techniques you are describing seem to cover some of the ideas
put forth in the MEP, so if you can make the code available, it would be a
great resource. 
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/MEP26-Artist-level-stylesheets-tp43664p43893.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

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" <tca...@gm...> 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
> <ste...@gm...> 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...@sun.ac.za>
> >> wrote:
> >> > On Thu, Sep 4, 2014 at 10:01 PM, Emmanuelle Gouillart
> >> > <emmanuelle...@nsup.org> 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...@googlegroups.com.
> >> > For more options, visit https://groups.google.com/d/optout.
> >>
> >>
> >>
> >> --
> >> Thomas Caswell
> >> tcas...@gmail.com
> >
> > --
> > 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 sci...@go....
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Thomas Caswell
> tca...@gm...
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds. Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

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
<ste...@gm...> 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...@sun.ac.za>
>> wrote:
>> > On Thu, Sep 4, 2014 at 10:01 PM, Emmanuelle Gouillart
>> > <emmanuelle...@nsup.org> 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...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Thomas Caswell
>> tcas...@gmail.com
>
> --
> 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 sci...@go....
> For more options, visit https://groups.google.com/d/optout.
-- 
Thomas Caswell
tca...@gm...