Re: [matplotlib-devel] First cut on a QtAgg backend

[John H. <jdh...@ac...>]

>>>>> "Ted" == Ted Drain <ted...@jp...> writes:

    Ted> We've also been working on a Qt front end.  It's been going
    Ted> slow because we've only been able to spend about 1 oerson-day
    Ted> per week on it.  But, starting this week I have someone full
    Ted> time on it.  He's gotten a basic widget working using the
    Ted> same organization that the GTK code uses.  Sigve's code has a
    Ted> lot more functionality in the tool bars than ours right now.

Great -- it looks like there will be a good opportunity to merge the
best features from both backends -- two functional qt backends is
definitely an improvement over what we had a week ago!  Particularly
useful might be to retain the current implementation which uses string
methods to transfer the agg image to the qt canvas as a fallback for
your extension code method.  That way, people who have trouble getting
the extension code version working can always fallback to something
slower that still works.

    Ted> The guy working on it doesn't think it would take more than a
    Ted> day or two to incorporate Sigve's code for the tool bar
    Ted> handling into our code.  We're close enough to finishing that
    Ted> it probably doesn't make a lot of sense to try and set up a
    Ted> collaboration right now but I'm open to that possibility if
    Ted> that's what people want.  All I really interested in is
    Ted> seeing the QtAgg front end in matplotlib as a supported
    Ted> component (which we'd be happy to help maintain) so whatever
    Ted> gets us there the quickest sounds good to me.

Whatever works for you and Sigve works for me.  My guess is that it
will be easy to cross-pollinate from one implementation to the other.

Thanks!
JDH