Maintenance Mode 6

In the last few weeks I’ve adopted a couple projects that, for whatever reason, had not been actively maintained for a while.

Cluttermm

Cluttermm wraps the Clutter Toolkit, “a software library for creating fast, compelling, portable, and dynamic graphical user interfaces”. Clutter has become an integral part of the GNOME project through its use in the GNOME Shell featured in GNOME 3. As such, I think it’d be a shame to not have high-quality C++ bindings.

Cluttermm had not really had much activity since early last year. With the rate of Clutter development, Cluttermm feel behind quickly. I’m trying to catch up now and as Murray mentioned, I’ve been able to wrap more API and fix a few bugs. So far I’ve got the 1.2 API almost fully wrapped. There are certainly bugs, some of which I’m finding now that I’m actually writing some examples. As I’m very much new to this wrapping business, I want to write a number of examples using the newly wrapped API. Once I’m comfortable that things are in good order, I’ll move onto the 1.4 and then 1.6 APIs.

GNOME System Monitor

GNOME System Monitor (g-s-m) is the default process viewer and system monitor in GNOME. I got involved by responding to the call to port g-s-m to Gtk3. Thanks goes to Openismus for allowing me to spend work time doing the porting (which I’ll blog about in the next couple days). During this process one always finds areas for improvement which spurred my interest in becoming the maintainer.

From what I can tell g-s-m hasn’t been actively developed in well over a year. You can imagine that bugzilla has a lot of suggestions for future tasks. My first order of business will be dealing with neglected patches and responding to bug reports.

So it appears as if I’ve filled all my free time for the foreseeable future. We’ll see how much I can get done between changing diapers and playing with the kids. ;)

Oh, and lastly… patches welcome. :P

6 thoughts on “Maintenance Mode

  1. Reply Matteo Mar 1, 2011 06:04

    I’m asking here before opening a bug in g.b.o, because I don’t know if it goes under applets or under g-s-m.

    The *only* applet I will miss with the transition to gnome3 is the g-s-m one. I really want to see at all time network, CPU and disk usage spikes, because they give me an idea if there is a problem, if a background task in a shell has finished (like compilation), etc.

    Where should I file a bug requesting for the g-s-m applet to be somewhat ported/integrated/rewritten in gnome-shell? This is a P1 usability issue for me, and my only worry about the transition. I don’t see why it can’t be there along with the battery status icon: I mean, both of them show the current and always-changing status of your system.

  2. Reply Chris Mar 1, 2011 06:25

    @Matteo: You’re talking about the multiload applet. You can file a bug here: https://bugzilla.gnome.org/browse.cgi?product=gnome-applets

  3. Reply Emmanuele Bassi Mar 1, 2011 07:25

    @chris: awesome work on the cluttermm bindings! feel free to poke us on the #clutter channel if you need any clarification on the API.

    @matteo: you or somebody else will have to rewrite the multi-load applet into a gnome-shell extension.

  4. Reply Chris Mar 2, 2011 02:17

    @ebassi: Thanks, I definitely will.

  5. Pingback: the blixtra blog » I’ve landed on Planet GNOME!

  6. Pingback: the blixtra blog » Gnome System Monitor: Swatting bugs

Leave a Reply