On Fri, Aug 5, 2011 at 2:26 PM, Gonzalo Odiard <gonz...@laptop.org> wrote: > I have 3 questions: > > 1) Is the move to python 3 in your plans too? (I don't know if is included > in F15) > but if we need to break compatibility will be good break it one time.
I did look into this, and concluded "no". The Py3 move would be much less compatibility-breaking, and would make this task even more painful with no gain. Added my notes here: http://wiki.sugarlabs.org/go/Features/GTK3#Python_3 > 2) Sugar theme: with the change to GTK3 we will need rewrite the Sugar > theme, right? > I think GTK3 use only cairo to draw the widgets, I don't know how is our > theme working, > and I don't know who can do this work. Good point - this is something that we'll need to investigate. I'll look into it on next opportunity. > 3) I am not sure about the timing to do this work. I would be more > comfortable if we start > a planning period now, and start coding after 11.3.0 release. Sugar Labs should not be held back by OLPC's schedule. The longer you leave this transition, the more painful it gets. Sugar is broken now, and we should do our bit to fix this, even though it would not directly contribute to OLPC's next release it would definitely have a very positive effect for OLPC's future releases. Note that this change is not very disruptive, it just needs planning. No activities would need to be ported immediately, and Sugar components can be ported one by one. The porting process is expected to be easy. Disruption could perhaps be further minimized by requiring that sugar-toolkit is ported to GTK3 and running stable before any other work commences. But do remember that sugar-toolkit is proposed to include the GTK2 version as well. Daniel _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
