[wxPython-dev] 2.7 timeline

[Mart Raudsepp]

On Fri, 2006-09-29 at 15:30 -0400, Lanier, Paul wrote:
> Thanks.  I'll keep that in mind.
> 
> I don't follow the wxWidgets dev list so maybe it was discussed there
> but do you know if there are any firm (as in someone is working on it)
> plans for an anti-alias rendering system (anti-alias DC, whatever would
> be decided). 
> 
> I am interested in working on something along those lines.

Plans are there (in my mind and some other people's) but the time isn't
yet, apparently.
My own plans involve a wxCairoDC and then seeing what can be done
afterwards. A cairo based wxDC implementation at the very least will
allow us to start using the native GTK+ printing infrastructure in
>=gtk+-2.10, but also give an anti-aliasing capable implementation of
wxDC. There are some concern (not yet articulated on wx-dev) regarding
starting to use this implementation by default for wxGTK due to it being
a completely different drawing model in the background, leading to
different results when comparing pixel-by-pixel. But that's something
that can be thought of later on (if to plug wxCairoDC as a pimpl into
default wxDC or not on wxGTK).

Obviously any help is welcome here. Preferably on the C++ level, of
course.
In particular at first I'm looking for wxDC unit tests that would allow
me and others to compare the behaviour/result of the existing and new
wxDC implementations - including when such concepts as scaling, axis
orientation, origin, different logical operations, pens, map modes and
so on are involved, also when used combined.

Regards,
Mart Raudsepp