628
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + − [[Category:Feature|GTK3]] Line 9:
Line 8: − + − + − + − + Line 60:
Line 59: − + + + Line 182:
Line 183: + + + + Line 189:
Line 194: − + Line 197:
Line 202: + +
no edit summary
<noinclude>{{TOCright}}
<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:FeatureLanded|GTK3]]
</noinclude>
</noinclude>
== Owner ==
== Owner ==
* This plan/proposal maintained by [[User:DanielDrake|Daniel Drake]] (other editors welcome!)
* This plan/proposal maintained by [[User:DanielDrake|Daniel Drake]] and [[User:Erikos|Simon Schampijer]]
* A number of developers will be needed at each stage to successfully execute this; Daniel offers his assistance for a coordination/oversight role if that would be useful.
* A number of developers will be needed at each stage to successfully execute this; Daniel offers his assistance for a coordination/oversight role if that would be useful.
== Current status ==
== Current status ==
* Targeted release: <b>0.96</b> (at least for sugar-toolkit port)
* Targeted release: <b>0.96</b> (the sugar-toolkit and sugar-artwork port)
* Last updated: (DATE)
* Last updated: 31.01.12
* Percentage of completion: XX%
* Percentage of completion: 35% (the sugar-toolkit and sugar-artwork port will count as 50% when finished)
At the Desktop summit, Raul Gutierrez Segales, Benjamin Berg and Paul Proteus successfully [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg22070.html prototyped] some of the ideas below. After only a few hours of effort, a minimal Sugar GTK3 activity was running alongside GTK2 activities. The plan below should therefore be quite credible, but some prerequisites remain.
At the Desktop summit, Raul Gutierrez Segales, Benjamin Berg and Paul Proteus successfully [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg22070.html prototyped] some of the ideas below. After only a few hours of effort, a minimal Sugar GTK3 activity was running alongside GTK2 activities. The plan below should therefore be quite credible, but some prerequisites remain.
A prerequisite to porting a Sugar process, component or activity is to remove all its usage of hippocanvas. This library is unmaintained, would be painful to port to GTK3, and can be done better with standard GTK+ code at the Python level. Most users of HippoCanvas can switch to custom GtkContainer widgets.
A prerequisite to porting a Sugar process, component or activity is to remove all its usage of hippocanvas. This library is unmaintained, would be painful to port to GTK3, and can be done better with standard GTK+ code at the Python level. Most users of HippoCanvas can switch to custom GtkContainer widgets.
One complication is that hippo usage is not limited to Sugar's core; some activities use hippo, or they pull on sugar-toolkit classes which are implemented with hippo. These are: Chat (<em>please list others here</em>).
One complication is that hippo usage is not limited to Sugar's core; some activities use hippo, or they pull on sugar-toolkit classes which are implemented with hippo. These are: Chat, Speak (<em>please list others here</em>).
=== Theme porting ===
=== Theme porting ===
[[/Theme|Theme status.]]
One major internal change in GTK3 is the way that themes are designed. GTK2 allowed themes to be implemented with a special format in a gtkrc file, but GTK3 now requires that themes are implemented using CSS. Therefore another non-trivial prerequisite for a GTK3-based sugar release of any visual component is the porting of the theme.
One major internal change in GTK3 is the way that themes are designed. GTK2 allowed themes to be implemented with a special format in a gtkrc file, but GTK3 now requires that themes are implemented using CSS. Therefore another non-trivial prerequisite for a GTK3-based sugar release of any visual component is the porting of the theme.
In the event of problems in the GTK3 version of sugar-toolkit, activity authors have the (default) choice of staying with GTK2. The transition period before the GTK2 version is removed would obviously be extended in the face of significant problems with GTK3 version.
In the event of problems in the GTK3 version of sugar-toolkit, activity authors have the (default) choice of staying with GTK2. The transition period before the GTK2 version is removed would obviously be extended in the face of significant problems with GTK3 version.
== Documentation ==
* [[Features/GTK3/Development | Development page]]
* [[Features/GTK3/Porting | Activity porting guide]]
== Release Notes ==
== Release Notes ==
This work would benefit from some focused attention at in-person meetings.
This work would benefit from some focused attention at in-person meetings.
See [[Features/GTK3/DesktopSummitActivities]] for earlier desktop summit ideas.
See [[Features/GTK3/Desktop Summit activities]] for earlier desktop summit ideas.
On September 10th-12th, a SugarCamp will be held in Paris. We will be working on this plan at the event, starting with the prerequisites.
On September 10th-12th, a SugarCamp will be held in Paris. We will be working on this plan at the event, starting with the prerequisites.
== Comments and Discussion ==
== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
== Subpages ==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}