From 14716e2d8d8bf7ccd8ba3ee2e9607a718bf2ff66 Mon Sep 17 00:00:00 2001
From: Lars Uebernickel <lars.uebernickel@canonical.com>
Date: Mon, 21 May 2012 16:45:58 +0200
Subject: Use a gsettings list for finding out which apps should appear in the
 menu

Previously, this was handled by looking for .desktop files in various system
and user directories.  The messaging menu should not display any applications
by default anymore, so a simple per-user gsettings list suffices.  A neat side
effect is that the hairy blacklist handling is not needed anymore, either.

Small regression: apps are not configurable at runtime anymore (settings key is
not listened to for changes).
---
 data/com.canonical.indicator.messages.gschema.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 data/com.canonical.indicator.messages.gschema.xml

(limited to 'data/com.canonical.indicator.messages.gschema.xml')

diff --git a/data/com.canonical.indicator.messages.gschema.xml b/data/com.canonical.indicator.messages.gschema.xml
new file mode 100644
index 0000000..d9165cd
--- /dev/null
+++ b/data/com.canonical.indicator.messages.gschema.xml
@@ -0,0 +1,12 @@
+<schemalist>
+  <schema id="com.canonical.indicator.messages" path="/com/canonical/indicator/messages/" gettext-domain="indicator-messages">
+    <key name="applications" type="as">
+      <summary>List of applications that are shown in the messaging menu</summary>
+      <description>
+        Applications corresponding to the desktop file ids in this list are shown in the messaging menu.
+      </description>
+      <default>[]</default>
+    </key>
+  </schema>
+</schemalist>
+
-- 
cgit v1.2.3