On 9/7/07, Michael Droettboom <mdroe@...> wrote:
> [Moved to the devel list from users]
> On a related note, I'm curious about usage of the Gdk and Wx (non-Agg)
> rendering backends. They both have various shortcomings relative to Agg
> (no antialiasing, limited mathtext rotation, etc.). Is there a real
> performance or other reason to keep these maintained at this point? I
> don't see them as significantly easier for embedding in applications
> than Agg (since both GtkAgg and WxAgg spell out how to get a native
> image buffer from the Agg buffer without using C extensions).
> Hope the question doesn't offend -- I can see their "reason to be"
> historically, but maybe those reasons are no longer relevant.
The two adbantages of GTK that I am aware of are
-- a bit faster than GTKAgg
-- better support over X11 because you don't have to transfer the
entire bitmap on every redraws since the native X11 commands can be
But these advantages may not outweigh their disadvantages
(maintenance, inertia preventing us from refactoring). We could
consider adding an svn dir w/ a bunch of experimental and/or noncore
and/or not supported backends. If the backend lookup machinery were a
bit more sophisticated (eg if 'backend : myformat' is specified, the
imported will try and 'import backend_myformat' or something like
that, thern users could use backends outside the normal install tree.
Then we could remove backends we do not want to actively maintain,
while providing a location in svn for those who want to keep using
them and providing a friendly way for them to keep using them with