On 10 October 2011 00:43, Mihai Cozma <[email protected]> wrote: > Thanks for the reply, useful links. > I also found the next text there: > "The plan seems to wait GTK 3.x become stable for win32 which takes sometime > which ultimately invalidate this instruction as we will go with PyGI instead > of PyGTK which is also another problem because GI isn't ported to win32 yet. > That's the pity situation for mypaint win32." > So based on this information, is there any point in trying to fix bugs and > stuff, or we just have to wait until GI gets ported to windows and gtk 3 is > stable for windows and so on? I mean, would all the work done trying to fix > the problem in 2.24 get obsolete by the time GTK 3.x and this GI gets used? Fixing the critical/blocking issues in GTK 2.x on Windows is very valuable still.
Porting MyPaint to PyGI and GTK 3.x will likely not happen for the next release. Meaning that without GTK 2.x fixed it will be some additional months _after_ we get the next release out before Windows will get the new stuff. There are other projects that will benefit from having GTK 2.24 fixed as well. GIMP 2.8 is another release that is also blocking on this/these tablet bugs. And, I would not be totally surprised if fixes are also applicable to GTK 3.x -- Jon Nordby - www.jonnor.com _______________________________________________ Mypaint-discuss mailing list [email protected] https://mail.gna.org/listinfo/mypaint-discuss
