2011/11/7 dimitris chloupis <theki...@yahoo.co.uk>: > Hey there I posted this to the forum I will post it here , I hope you dont > mind. Hi!
> Because this started as a linux project I completely > understand the choice of GTK but on macos is meeeehhhhh. But then again GTK3 > offers native support and look in macos and looks lovely . But mypaint is > for GTK2 and also pygtk is only for GTK2. There is pyGobject but I fear that > this will mean a rewrite for the GUI of mypaint. And of course I still like > the idea of a fork that follow closely any developement in mypaint even > contributes new features in mypaint that are implemented to DragonSphere but > is not bound by the goal of mypaint to become the ultimate Natural medium > emulation app (see Painter competitor). We will port to PyGObject and GTK3. PyGObject + GTK introspection bindings are in many cases very similar to pyGTK, so it will not be a complete rewrite, but small changes will be required all over the code base. This will probably happen after 1.0 is out, which should be pretty soon. > I really need your advice as I am abit lost. I know a rewrite wont be easy > , it will not be fast, but I love developing guis so I dont mind. I also > dont mind droping the DragonSphere idea and only contribute to mypaint macos > port. Any developer who have an advice on this ? We would love help with MyPaint, especially on OSX. There is some effort going on on providing a MyPaint.app, and this alone would be a big step forward for MyPaint on this platform. Once we are ready to start GTK3 porting work you can help out a lot there. I think that unless one has fundamentally different goals, one should first try to contribute to existing projects. And then if that does not work out, one can always create a new software or fork at that point. -- Jon Nordby - www.jonnor.com _______________________________________________ Mypaint-discuss mailing list Mypaint-discuss@gna.org https://mail.gna.org/listinfo/mypaint-discuss
