matplotlib-devel Mailing List for matplotlib

Bill Baxter wrote:
> 
> On 9/24/07, *Eric Firing*
> <ef...@ha...
> <mailto:ef...@ha...>> wrote:
> 
> John et al.,
> 
> "Agg 2.5 will ship with a libsigc++ license that will allow us to treat
> the code as MIT X11 unless the code is pulled out, allowing Antigrain to
> be used internally for Silverlight and allowing them to license
> Antigrain for other customers."
> 
> I found the above quote on this page:
> http://www.mono-project.com/Moonlight
> 
> I don't understand it; does it mean that we, too, can continue using
> future versions of Agg?
> 
> Weird. It reads to me more like they struck some sort of deal whereby
> the code can be used as MIT X11 as long as it's an internal part of
> Silverlight, but if removed from Silverlight, then it will revert to the
> current GPL/commercial dual license.
Unfortunately, that's not how these licenses work. Moonlight is LGPL/commercial
dual-licensed. If they intend to continue that way and incorporate Agg 2.5 into
it under special terms from Maxim, then Moonlight will still be LGPL/commercial,
*including* Agg 2.5. The LGPL allows one to extract a part of the LGPLed work
and use it separately under the LGPL license. If Maxim agrees to let Agg 2.5 be
used in an LGPLed Moonlight, then he can't then require that Agg 2.5 will only
be used in the context of Moonlight. Someone is confused, here (and it's not me
:-)).
Also unfortunately, this has no bearing on matplotlib. matplotlib still can't
use Agg 2.5 under an MIT/X11-style license. Asking Maxim for a special license
won't help because that license can't be MIT/X11 or anything near as free as
matplotlib's license without his giving away Agg 2.5 as a whole under that free
license.
-- 
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
 -- Umberto Eco

Hi!
I'm writing a gtk application that uses matplotlib heavily for data visualisation, but all the time consuming redrawing of the figure canvases took away much of the usability. So I wrote a FigureCanvas that delays redraws until it hasn't seen any new resize_events for a short while. It works much more smoothly on ubuntulinux than on winxp (where many redraws slip through the seams and I'm not sure why that happens), but anyway - tell me what you think! Is this a good solution, or is there a smarter approach?
Cheers!
/Joel