[dconf-editor] Add more cases to the demo.

[Arnaud Bonatti <arnaudb src gnome org>]

commit 0f455e59458b837696543e1380f9d2dd5fc6f9fe
Author: Arnaud Bonatti <arnaud bonatti gmail com>
Date:   Sun Oct 11 02:28:33 2015 +0200

    Add more cases to the demo.

 editor/ca.desrt.dconf-editor.gschema.xml |  114 ++++++++++++++++++++++++------
 1 files changed, 91 insertions(+), 23 deletions(-)
---
diff --git a/editor/ca.desrt.dconf-editor.gschema.xml b/editor/ca.desrt.dconf-editor.gschema.xml
index adb1ab3..5416562 100644
--- a/editor/ca.desrt.dconf-editor.gschema.xml
+++ b/editor/ca.desrt.dconf-editor.gschema.xml
@@ -49,10 +49,58 @@
     <key name="boolean" type="b">
       <default>true</default>
       <summary>A boolean, type "b"</summary>
-      <description>Booleans can only take two values, "true" or "false" (lowercase).</description>
+      <description>Booleans can only take two values, "true" or "false".</description>
+    </key>
+    <key name="boolean-nullable" type="mb">
+      <default>nothing</default>
+      <summary>A nullable boolean, type "mb"</summary>
+      <description>GSettings allows nullable types, that are similar to other types but could take a 
"nothing" value. A nullable boolean can only take three values, "true", "false" and "nothing".</description>
+    </key>
+    <key name="byte" type="y">
+      <default>66</default>
+      <summary>A byte (unsigned), type "y"</summary>
+      <description>A byte value is an integer between 0 and 255. It may be used to pass around 
characters.</description>
+    </key>
+    <key name="bytestring" type="ay">
+      <default>[72, 101, 108, 108, 108]</default>
+      <summary>A bytestring, type "ay"</summary>
+      <description>The bytestring type is commonly used to pass around strings that may not be valid utf8. 
In that case, the convention is that the nul terminator character should be included as the last character in 
the array.</description>
+    </key>
+    <key name="bytestring-array" type="aay">
+      <default>[[72, 101, 108, 108, 108], [87, 111, 114, 108, 100], [33]]</default>
+      <summary>A bytestring array, type "aay"</summary>
+      <description>This is the type of an array of bytestrings. The bytestring type is commonly used to pass 
around strings that may not be valid utf8.</description>
+    </key>
+    <key name="dbus-handle" type="h">
+      <default>0</default>
+      <summary>A D-Bus handle type, type "h"</summary>
+      <description>The handle type is a 32bit signed integer value that is, by convention, used as an index 
into an array of file descriptors that are sent alongside a D-Bus message.
+
+If you are not interacting with D-Bus, then there is no reason to make use of this type.</description>
+    </key>
+    <key name="dbus-object-path" type="o">
+      <default>'/ca/desrt/dconf_editor'</default>
+      <summary>A D-Bus object path, type "o"</summary>
+      <description>An object path is used to identify D-Bus objects at a given destination on the bus.
+
+If you are not interacting with D-Bus, then there is no reason to make use of this type.</description>
+    </key>
+    <key name="dbus-object-path-array" type="ao">
+      <default>['/ca/desrt/dconf_editor/menus/appmenu', '/ca/desrt/dconf_editor/window/1']</default>
+      <summary>A D-Bus object path array, type "ao"</summary>
+      <description>An object path array could contain any number of object paths (including 0: "[]").
+
+If you are not interacting with D-Bus, then there is no reason to make use of this type.</description>
+    </key>
+    <key name="dbus-signature" type="g">
+      <default>'ii'</default>
+      <summary>A D-Bus signature, type "g"</summary>
+      <description>A D-Bus signature is a string used as type signature for a D-Bus method or message.
+
+If you are not interacting with D-Bus, then there is no reason to make use of this type.</description>
     </key>
     <key name="double" type="d">
-      <default>3.14159265358979324</default>
+      <default>3.1415926535897933</default>
       <summary>A double, type "d"</summary>
       <description>A double value could represent any real number.</description>
     </key>
@@ -61,42 +109,62 @@
       <summary>A 5-choices enumeration</summary>
       <description>Enumerations could be done either with the "enum" attribute, or with a "choices" 
tag.</description>
     </key>
-    <key name="integer" type="i">
-      <default>3</default>
-      <summary>An integer</summary>
-      <description>See also unsigned-integer.</description> <!-- TODO better description -->
+    <key name="integer-16-signed" type="n">
+      <default>-32768</default>
+      <summary>A short integer, type "n"</summary>
+      <description>A 16bit signed integer. See also the "integer-16-unsigned" key.</description>
     </key>
-    <key name="nullable-boolean" type="mb">
-      <default>nothing</default>
-      <summary>A nullable boolean, type "mb"</summary>
-      <description>GSettings allows nullable types, that are similar to other types but could take a 
"nothing" value.</description>
+    <key name="integer-16-unsigned" type="q">
+      <default>65535</default>
+      <summary>An unsigned short integer, type "q"</summary>
+      <description>A 16bit unsigned integer. See also the "integer-16-signed" key.</description>
     </key>
-    <!-- TODO add a nullable-(unsigned-)integer -->
-    <key name="nullable-string" type="ms">
-      <default>nothing</default>
-      <summary>A nullable string, type "ms"</summary>
-      <description>GSettings allows nullable types, that are similar to other types but could take a 
"nothing" value.</description>
+    <key name="integer-32-signed" type="i">
+      <default>-2147483648</default>
+      <summary>An usual integer, type "i"</summary>
+      <description>A 32bit signed integer. See also the "integer-32-unsigned" key.</description>
     </key>
+    <key name="integer-32-unsigned" type="u">
+      <default>4294967295</default>
+      <summary>An unsigned usual integer, type "u"</summary>
+      <description>A 32bit unsigned integer. See also the "integer-32-signed" key.</description>
+    </key>
+    <key name="integer-64-signed" type="x">
+      <default>-9223372036854775808</default>
+      <summary>A long integer, type "x"</summary>
+      <description>A 64bit signed integer. See also the "integer-64-unsigned" key.</description>
+    </key>
+    <key name="integer-64-unsigned" type="t">
+      <default>18446744073709551615</default>
+      <summary>An unsigned long integer, type "t"</summary>
+      <description>A 64bit unsigned integer. See also the "integer-64-signed" key.</description>
+    </key>
+    <!-- TODO add a nullable-(unsigned-)integer -->
     <key name="number-with-range" type="i">
       <default>3</default>
       <range min="-5" max="9"/>
       <summary>A number with range</summary>
-      <description>Every numeral setting (integers and unsigned integers of every type, plus doubles) could 
be limited to a custom range of values. For example, this integer could only take a value between -5 and 
9.</description>
+      <description>Every numeral setting (integers and unsigned integers of every type, plus doubles) could 
be limited to a custom range of values. For example, this integer could only take a value between -5 and 
9.</description> <!-- TODO and handle? -->
     </key>
     <key name="pair-of-integers" type="(ii)">
       <default>(800, 600)</default>
-      <summary>A custom type</summary>
-      <description>Dconf Editor lets you edit any settings type supported by GSettings, falling back on a 
string entry when it doesn't have a better widget.</description>
+      <summary>A custom type, here "(ii)"</summary>
+      <description>Dconf Editor lets you edit any settings type supported by GSettings, falling back on a 
string entry when it doesn't have a better way to do. Here is a tuple of two 32bit signed 
integers.</description>
     </key>
     <key name="string" type="s">
       <default>'Lorem ipsum dolor sit amet, consectetur adipiscing elit.'</default>
       <summary>A string, type "s"</summary>
-      <description></description> <!-- TODO bug here -->
+      <description>The string type could accept any utf8 string. Note that an empty string "''" is not the 
same as NULL (nothing); see also the "string-nullable" key.</description>
     </key>
-    <key name="unsigned-integer" type="u">
-      <default>3</default>
-      <summary>An unsigned integer</summary>
-      <!-- TODO description -->
+    <key name="string-array" type="as">
+      <default>['orange', 'banana', 'pear']</default>
+      <summary>A string array, type "as"</summary>
+      <description>A string array contains any number of strings of whatever length. It may be an empty 
array, "[]".</description>
+    </key>
+    <key name="string-nullable" type="ms">
+      <default>nothing</default>
+      <summary>A nullable string, type "ms"</summary>
+      <description>GSettings allows nullable types, that are similar to other types but could take a 
"nothing" value. A nullable string can take any string as value, including the empty string "''", or can be 
NULL (nothing).</description>
     </key>
   </schema>
 </schemalist>