SweetTooth and Live Extension Enabling/Disabling

["Jasper St. Pierre" <jstpierre mecheye net>]

Hey guys, it's Jasper.

Again, the last time I talked about SweetTooth, it was a month ago.
I'm here to say that enabling/disabling of extensions has landed!
Extension authors, you have to update to the new APIs if you want your
extensions to be compatible with 3.2. For more information, the
references from the old ML post. They're still valid. Additionally, I
just published a blog post with some information as well [0].

> Before this is reviewed and landed, I want to make sure that everybody here will be able to port their extensions to the new API. See the old, invalid BGO bug #635209 [5] for a quick overview and the previous ML post [6] for a more in-depth take on it.
> ...
> [5] https:/bugzilla.gnome.org/show_bug.cgi?id=635209
> [6] http://mail.gnome.org/archives/gnome-shell-list/2011-June/msg00283.html

I feel that this is fairly straightforward. Giovanni has ported the
gnome-shell-extensions repository to the new API [1], so this can land
without breaking much. If you are having trouble porting your
extension, just post a message on the list and I'll try to help you
out.

Additionally, last time I gave myself five goals for 3.2:

>  1. Writing and testing forward-compatibility in case I have to break the DBus API in the future. The website has to work from 3.2 onward for the rest of its life, even if most of the extensions don't. Using require.js and some clever hacking, I have this done and working in my local tree.
Done.

>  2. Extension code review. For now, this will probably be a secure link to a .zip file with the code and a yay/nay with a comment option.
Done.

>  3. After a crash, the fail-whale dialog will show you your enabled extensions with an option to disable them before restarting the Shell.
Done. [2]

>  4. Detecting a mismatch between your current Shell version and an extension's version, and prevent you from shooting yourself in the foot installing an out-of-date plugin.
Done.

>  5. If an extension errors out, I'll be adding an option to mail the stack trace to the author.
In progress.

For 3.2, besides item #5, I'm going to be working on all the "boring"
stuff that needs to be done in a webapp (user registration, etc.), a
simple page that lets you enable/disable all the extensions on your
machine, as well as general UI polish. For 3.4, I hope to get updates
working.

[0] http://blog.mecheye.net/2011/08/shell-extensions-live-enable-disable/
[1] http://git.gnome.org/browse/gnome-shell-extensions/log/?h=extension-live-disable
[2] https://bugzilla.gnome.org/show_bug.cgi?id=656747

  Jasper