a64c84395f
Right now, we are hard-depending on the presence of Evolution by using its settings schemas. This is likely to be unpopular, and also causes instability if someone happens not to have Evolution installed, so install a schema that has the same data path as the Evolution schema, but a different name and install that for the keys we need. To avoid a string-freeze break, we rely on the translations in Evolution - if Evolution isn't installed, the key descriptions will be untranslated in dconf-editor. https://bugzilla.gnome.org/show_bug.cgi?id=674424
22 lines
918 B
XML
22 lines
918 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!-- NOTE: This schema is a GNOME 3.4 workaround - it uses the same path
|
|
as org.gnome.evolution.calendar, but avoids us requiring Evolution
|
|
be installed. In GNOME 3.6 the selected state will become a flag
|
|
on the calendar. Because the translations are in Evolution,
|
|
this is untranslated and in POTFILES.skip.
|
|
-->
|
|
<schemalist>
|
|
<schema path="/org/gnome/evolution/calendar/" id="org.gnome.shell.evolution.calendar" gettext-domain="evolution">
|
|
<key type="as" name="selected-calendars">
|
|
<default>[]</default>
|
|
<summary>List of selected calendars</summary>
|
|
<description>List of calendars to load</description>
|
|
</key>
|
|
<key type="as" name="selected-tasks">
|
|
<default>[]</default>
|
|
<summary>List of selected task lists</summary>
|
|
<description>List of task lists to load</description>
|
|
</key>
|
|
</schema>
|
|
</schemalist>
|