Should stop using gconf in oneiric

[Sebastien Bacher]

Unity trunk is still using gconf in a few places, that's wrong not only because gconf is deprecated (by gsettings) but also because the keys it's reading are not used in GNOME3.

[Sebastien Bacher (seb128)]

Looking to the current (2011-06-22) trunk:

* PlacesHomeView.cpp uses gconf to read the default email client, browser, etc values, that's wrong since GNOME moved to use mimetype handlers for those (Mimetype=x-scheme-handler/<protocol> where "protocol is i.e http or mailto)

* unitya11y.cpp uses gconf to see if the accessibility is on, it should use org.gnome.desktop.interface toolkit-accessibility in gsettings instead

* same for panel-a11y.c

[Sebastien Bacher (seb128)]

The migration script also use gconf but that's required and ok

[Sebastien Bacher (seb128)]

you also use the nautilus gconf key to know if you need a confirmation to empty the bin, but ideally you should just do that using the nautilus dbus interface in oneiric

[David Barth (dbarth)]

I opened https://bugs.launchpad.net/unity/+bug/813492 to specifically track the a11y code issues that Alejandro will take care of.

[Jeremy Bícha (jbicha)]

I noticed that compiz trunk appears to have switched to gsettings.

[Sam_ (and-sam)]

Isn't then Bug #805063 opposing when setting unity as triaged there?

[David Barth (dbarth)]

Compiz will not use gsettings this cycle, whereas the rest of unity has switched to gsettings.

[David Barth (dbarth)]

The rest of this bug, ie fixing the dash home screen is now essentially a duplicate of https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/805063