After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 690824 - Remove builtin settings search provider
Remove builtin settings search provider
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 691779 (view as bug list)
Depends on: 690577
Blocks:
 
 
Reported: 2012-12-28 17:06 UTC by Giovanni Campagna
Modified: 2013-02-18 15:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Remove builtin settings search provider (9.65 KB, patch)
2012-12-28 17:06 UTC, Giovanni Campagna
none Details | Review
Remove builtin settings search provider (7.93 KB, patch)
2013-02-18 15:42 UTC, Giovanni Campagna
committed Details | Review

Description Giovanni Campagna 2012-12-28 17:06:31 UTC
To be applied if and when bug 690577 lands.
Comment 1 Giovanni Campagna 2012-12-28 17:06:34 UTC
Created attachment 232338 [details] [review]
Remove builtin settings search provider

It is now provided as a remote provider by gnome-control-center.
Comment 2 Jasper St. Pierre (not reading bugmail) 2012-12-28 17:14:09 UTC
Cosimo wasn't sure this was the greatest idea, but I forget his rationale.
Comment 3 Florian Müllner 2013-01-08 11:14:18 UTC
Do we expect settings to be fixed, or should users be able to disable the provider or reorder it? In the former case, leaving it in the shell is probably cleaner than special-casing it in g-c-c; otherwise I can't think of a reason not to do this ...
Comment 4 Emmanuele Bassi (:ebassi) 2013-01-15 11:31:25 UTC
I can think of restricted user modes where settings as a whole are hidden from the user - so allowing a system administrator to disable the g-c-c search provider would make sense.
Comment 5 Giovanni Campagna 2013-02-18 15:42:26 UTC
Created attachment 236614 [details] [review]
Remove builtin settings search provider

It is now provided as a remote provider by gnome-control-center.
Comment 6 Giovanni Campagna 2013-02-18 15:42:54 UTC
For now, we decided that gnome-control-center is special cased and not configurable.
Comment 7 Giovanni Campagna 2013-02-18 15:46:28 UTC
*** Bug 691779 has been marked as a duplicate of this bug. ***
Comment 8 Cosimo Cecchi 2013-02-18 15:51:36 UTC
Review of attachment 236614 [details] [review]:

::: js/ui/remoteSearch.js
@@ +126,3 @@
+
+    // Special case gnome-control-center to be always active and always first
+    sortOrder.unshift('gnome-control-center.desktop');

Hmm, gnome-control-center.desktop should never be in GSettings, as it's not user-visible. You should sort the loadState.loadedProviders list normally and then put the control center one at the top.
Comment 9 Giovanni Campagna 2013-02-18 15:54:00 UTC
(In reply to comment #8)
> Review of attachment 236614 [details] [review]:
> 
> ::: js/ui/remoteSearch.js
> @@ +126,3 @@
> +
> +    // Special case gnome-control-center to be always active and always first
> +    sortOrder.unshift('gnome-control-center.desktop');
> 
> Hmm, gnome-control-center.desktop should never be in GSettings, as it's not
> user-visible. You should sort the loadState.loadedProviders list normally and
> then put the control center one at the top.

Indeed, this works because gnome-control-center is not in GSettings: unshift adds the control-center provider at the front of the sort order, so the later call to sort() ensures that the provider object is first.
Comment 10 Cosimo Cecchi 2013-02-18 15:56:04 UTC
Review of attachment 236614 [details] [review]:

Completely misread the patch, sorry.
Comment 11 Giovanni Campagna 2013-02-18 15:58:11 UTC
Attachment 236614 [details] pushed as 3044a6b - Remove builtin settings search provider