diff options
author | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2011-05-17 17:10:36 +0100 |
---|---|---|
committer | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2011-05-17 17:10:36 +0100 |
commit | 1909039b191f0ac1c1fa2aeb9b9053b921471f1b (patch) | |
tree | ae1423a2df18bd4459d886db9fad86c5887c213e /doc | |
parent | f0f67e4329bfc219cf9f37a4e9f0dce9513b9ae0 (diff) | |
download | dbus-1909039b191f0ac1c1fa2aeb9b9053b921471f1b.tar.gz |
Describe best practices for property names, and recommend against dash-separated-words
Related to <https://bugs.freedesktop.org/show_bug.cgi?id=20948> whose
conclusion seemed to be that anything is allowed, but CamelCase is
considerably more interoperable.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/dbus-specification.xml | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 86e2b9b7..88360af5 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -3067,6 +3067,22 @@ </programlisting> </para> <para> + It is conventional to give D-Bus properties names consisting of + capitalized words without punctuation ("CamelCase"), like + <link linkend="message-protocol-names-member">member names</link>. + For instance, the GObject property + <literal>connection-status</literal> or the Qt property + <literal>connectionStatus</literal> could be represented on D-Bus + as <literal>ConnectionStatus</literal>. + </para> + <para> + Strictly speaking, D-Bus property names are not required to follow + the same naming restrictions as member names, but D-Bus property + names that would not be valid member names (in particular, + GObject-style dash-separated property names) can cause interoperability + problems and should be avoided. + </para> + <para> The available properties and whether they are writable can be determined by calling <literal>org.freedesktop.DBus.Introspectable.Introspect</literal>, see <xref linkend="standard-interfaces-introspectable"/>. |