Changes

== Looking forward to 0.92 ==

== Looking forward to 0.92 ==

For 0.92 we plan to focus on some architectural work that won't have a direct impact as perceived by most users. Sugar is a very thin layer of code that sits on top of hundreds of other components developed by other projects. There are ongoing changes on the components we depend most directly, and we need to adapt Sugar to those changes so it keeps being shipped by Linux distributions and benefits from future improvements.  

For 0.92 we plan to focus on some architectural work that won't have a direct impact as perceived by most users. Sugar is a very thin layer of code that sits on top of hundreds of other components developed by other projects. There are ongoing changes to the components we depend on most directly, and we need to adapt Sugar to those changes so it keeps being shipped by Linux distributions and benefits from future improvements.  

The changes include that the Python bindings for GNOME will be available dynamically through [http://live.gnome.org/GObjectIntrospection GObjectIntrospection] rather then through the current static bindings provided by [http://www.pygtk.org/ PyGTK]. So a goal for 0.92 will be to port Sugar and all the activities to GNOME 3 through [http://live.gnome.org/GObjectIntrospection GObjectIntrospection].   

The changes include that the Python bindings for GNOME will be available dynamically through [http://live.gnome.org/GObjectIntrospection GObjectIntrospection] rather then through the current static bindings provided by [http://www.pygtk.org/ PyGTK]. So a goal for 0.92 will be to port Sugar and all the activities to GNOME 3 through [http://live.gnome.org/GObjectIntrospection GObjectIntrospection].