GnomeGoals Status Report

I’d like to share the status of some GnomeGoals, as some of them have been recently completed:

RemoveGnomeOpenGnomeHelp: completed!

DropLibsexy: completed!

RemoveLibGladeUseGtkBuilder: only remaining: sound-juicer. Updated automatical stats can be found at Frédéric Péters’ 299 report [1]

CleanupGTKIncludes: mostly complete. Remaining: gnome-disk-utility . Also, It’s needed to check gtk-sharp, gnome-desktop-sharp and some GNOME external dependencies.

CorrectDesktopFiles: mostly completed. I’ve been filling some bugs and I think this GnomeGoal is complete now. Anyway, please, check your module an update the wiki page. Updated automatical stats can be found here.

UseGseal: In progress. Some modules was already ported to use accessor functions instead direct access to prepare to GTK+3 transition. The GTK+ api to make the port is mostly complete now, but there still are some corner cases. Please, start porting you module ASAP and fille bugs agains GTK+ if you need some new api.

AddGObjectIntrospectionSupport: In progress. You can take a look to the modules marked as ‘done’ to help you to add introspection support inside your module. Updated automatical stats can be found at Frédéric Péters’ 299 report [1]

RemoveDeprecatedSymbols/Glib: Mostly complete. Anyway take a look on this as some new symbols can be deprecated in each cycle. Updated automatical stats can be found at Frédéric Péters’ 299 report [1]

RemoveDeprecatedSymbols/GTK+: Mostly complete. Anyway take a look on this as some new symbols can be deprecated in each cycle. Updated automatical stats can be found at Frédéric Péters’ 299 report [1]

As you can see, the status of the GnomeGoals is pretty good so congrats everyone!! :)

[1] http://www.gnome.org/~fpeters/reports/299.html

4 thoughts on “GnomeGoals Status Report”

  1. Regarding “Drop LibSexy”, do you know why “notification-daemon” is listed as “not needed”? Because the current version does have a hard dependency on libsexy – one trivially patched out, but necessary nontheless…

    Also, regarding deprecated symbols and libraries, how do you handle language bindings like gnome-sharp, or gnome-python? I’ve noticed that as of Gnome 2.30, pretty much the only thing still requiring libgnome and friends are the Mono and Python bindings. For Gnome 3.0, will those bindings also be dropping support for the unwanted libraries?

  2. @Simon:
    I can’t see the libsexy dependency in the git repo: http://git.gnome.org/browse/notification-daemon/tree/configure.ac

    About the bindings:
    Yes, I think the idea is not support these libraries; python bindings are modular so I think the maintainers will disable the non required libraries.
    Also, I think the plan is to use GObject instrospection and PyGI to make the bindings. Take a look here: http://live.gnome.org/PyGI
    I guess this will be discussed in the python hackfest [1]

    I don’t know about the mono case.

    [1] http://live.gnome.org/Hackfests/Python2010

  3. Ah, so the libsexy dependency has been dropped in the source, but not yet released. Maybe it’s time they did a new release, then – the last one was back in 2008…

Comments are closed.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>