105
edits
Changes
Jump to navigation
Jump to search
Line 83:
Line 83: + − + Line 116:
Line 117: − +
no edit summary
# Port Sugar core to hippocanvas
# Port Sugar core to hippocanvas
# Some time later, remove sugar-toolkit's GTK2 compatibility.
# Some time later, remove sugar-toolkit's GTK2 compatibility.
#* I propose that this happens 1 year after release of the first sugar-toolkit GTK3 version
=== How to port ===
=== How to port ===
I plan to start a page at [[Features/GTK3/Porting]] that details the porting process, that could be provided as documentation to anyone involved in these efforts (including thsoe working on porting Sugar core, but also those working on activities). The content covered will be:
I plan to start a page at [[Features/GTK3/Porting]] that details the porting process, that could be provided as documentation to anyone involved in these efforts (including those working on porting Sugar core, but also those working on activities). The content covered will be:
# How to remove hippo and what to replace it with (links to commits that have done this for other activities, etc)
# How to remove hippo and what to replace it with (links to commits that have done this for other activities, etc)
== Dependencies ==
== Dependencies ==
Sugar would start depending on PyGObject built with gobject introspection support, GTK3, and (at the end of the transition) period would drop its dependencies on GTK2 and PyGTK.
Sugar would start depending on PyGObject built with gobject introspection support, GTK3, and (at the end of the transition period) would drop its dependencies on GTK2 and PyGTK.
== Release Notes ==
== Release Notes ==