On Tue, 2011-06-21 at 23:03 -0400, Jasper St. Pierre wrote: > On Tue, Jun 21, 2011 at 10:55 PM, ecyrbe <ecy...@gmail.com> wrote: > > Thank you for the details. I do like what you are doing, just another bunch > > of questions : > > - is (validity-check) going to be added to prevent the shell from aborting? > > (validity-check) is an idea that Company had. I have no idea if it's > feasible, it's there as an idea to increase API stability. > > > if so, do you need help to make patches to gnome-shell libraries > > depedencies, and gjs as this seems to be a big review work? > > - shemas installation requires root priviledges (last time i checked), is > > policikit going to be used for installing extensions? > > I assume that https://bugzilla.gnome.org/show_bug.cgi?id=649717 will > be fixed instead.
Me too. You mentioned in your earlier mail about adding getExtensionStorage() (and similar). In a similar way perhaps you could provide getExtensionSettingsSafe(gsettings_schema) which does the list_schema dance to at least check for missing settings, before creating a settings object which could crash the shell. Although I suppose that is not actually required if all uploaded extensions are audited first - simply prohibit ones that need to install gsettings [1] John [1] It makes me sad that gsettings is unsuitable for this per-user case. So close, yet so far. _______________________________________________ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
