Re: 90% working GTK2 backend

Kalle Svensson <[email protected]>:
[snip]
> Okay, I've finally gotten around to testing this new GTK2 backend.  It
> basically works, with some test failures.  Still, it's mostly working
> and I've commited it to CVS.

Woohoo!

> Since the old backend didn't work anyway, I decided that moving from
> GTK+ 1.2 to 2.0 was not a problem.  If anyone feels differently, we
> could revert gtkgui.py and check the new code in as gtk2gui.py or
> something.  I'm not volunteering to write the code, though.

I don't think this is a problem -- at the rate we're progressing at
the moment (and with the relatively small user base, I guess) I don't
think it's problematic to use recent versions. We might even consider
using Python 2.2 features in the not too distant future... (Although
we should wait for Jython on that one -- it seems they are still at
2.1...?)

> Some test notes:
[snip]
> These two are probably easy to fix.
> 
> test_radiobutton - The radiobutton is always selected.  This is a
> feature of GTK+.  Otherwise, the test works as it should.

This test is somewhat bogus anyway, I think. Before 0.2 final, we
should review the test suite.

BTW: I removed the try/except-stuff at the beginning of gtkgui -- it
defeats the purpose of the DEBUG mechanism in anygui/__init__.py and
gives a traceback when pygtk isn't installed (which it certainly
shouldn't). It seems to be fine now.

[snip]
> As usual, I'll try to find time for fixing these (mostly small)
> problems, but can't promise anything.

Sounds good anyway :)

> Thanks again for the nice christmas present, Eugene!

Yeah, thanks from us all!

> Peace,
>   Kalle

-- 
Magnus Lie Hetland
http://hetland.org


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com