[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/doc/misc/dbus.texi,v
|
From: |
Michael Albinus |
|
Subject: |
[Emacs-diffs] Changes to emacs/doc/misc/dbus.texi,v |
|
Date: |
Fri, 18 Jul 2008 20:25:54 +0000 |
CVSROOT: /sources/emacs
Module name: emacs
Changes by: Michael Albinus <albinus> 08/07/18 20:25:54
Index: dbus.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/misc/dbus.texi,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- dbus.texi 13 Jul 2008 15:12:43 -0000 1.20
+++ dbus.texi 18 Jul 2008 20:25:54 -0000 1.21
@@ -27,6 +27,7 @@
* D-Bus: (dbus). Using D-Bus in Emacs.
@end direntry
+
@node Top, Overview, (dir), (dir)
@top D-Bus integration in Emacs
@@ -41,7 +42,7 @@
@menu
* Overview:: An overview of D-Bus.
-* Inspection:: Inspection of the bus names.
+* Inspection:: Inspection of D-Bus services.
* Type Conversion:: Mapping Lisp types and D-Bus types.
* Synchronous Methods:: Calling methods in a blocking way.
* Receiving Method Calls:: Offering own methods.
@@ -50,6 +51,7 @@
* GNU Free Documentation License:: The license for this documentation.
@end menu
+
@node Overview
@chapter An overview of D-Bus
@cindex overview
@@ -101,9 +103,22 @@
@node Inspection
address@hidden Inspection of the bus names.
address@hidden Inspection of D-Bus services.
@cindex inspection
address@hidden
+* Bus names:: Discovering D-Bus names.
+* Introspection:: Knowing the details of D-Bus services.
+* Nodes and Interfaces:: Detecting object paths and interfaces.
+* Methods and Signal:: Applying the functionality.
+* Properties and Annotations:: What else to know about interfaces.
+* Arguments and Signatures:: The final details.
address@hidden menu
+
+
address@hidden Bus names
address@hidden Bus names.
+
There are several basic functions which inspect the buses for
registered names. Internally they use the basic interface
@samp{org.freedesktop.DBus}, which is supported by all objects of a bus.
@@ -187,10 +202,120 @@
@code{:session}.
@end defun
+
address@hidden Introspection
address@hidden Knowing the details of D-Bus services.
+
+D-Bus services publish their interfaces. This can be retrieved and
+analyzed during runtime, in order to understand the used
+implementation.
+
+The resulting introspection data are in XML format. The root
+introspection element is always a @code{node} element. It might have
+a @code{name} attribute, which denotes the (absolute) object path an
+interface is introspected.
+
+The root @code{node} element may have @code{node} and @code{interface}
+children. A child @code{node} element must have a @code{name}
+attribute, this case it is the relative object path to the root
address@hidden element.
+
+An @code{interface} element has just one attribute, @code{name}, which
+is the full name of that interface. The default interface
address@hidden is always present. Example:
+
address@hidden
+<node name="/org/bluez">
+ <interface name="org.freedesktop.DBus.Introspectable">
+ @dots{}
+ </interface>
+ <interface name="org.bluez.Manager">
+ @dots{}
+ </interface>
+ <interface name="org.bluez.Database">
+ @dots{}
+ </interface>
+ <interface name="org.bluez.Security">
+ @dots{}
+ </interface>
+ <node name="service_audio"/>
+ <node name="service_input"/>
+ <node name="service_network"/>
+ <node name="service_serial"/>
+</node>
address@hidden example
+
+Children of an @code{interface} element can be @code{method},
address@hidden and @code{property} elements. A @code{method} element
+stands for a D-Bus method of the surrounding interface. The element
+itself has a @code{name} attribute, showing the method name. Children
+elements @code{arg} stand for the arguments of a method. Example:
+
address@hidden
+<method name="ResolveHostName">
+ <arg name="interface" type="i" direction="in"/>
+ <arg name="protocol" type="i" direction="in"/>
+ <arg name="name" type="s" direction="in"/>
+ <arg name="aprotocol" type="i" direction="in"/>
+ <arg name="flags" type="u" direction="in"/>
+ <arg name="interface" type="i" direction="out"/>
+ <arg name="protocol" type="i" direction="out"/>
+ <arg name="name" type="s" direction="out"/>
+ <arg name="aprotocol" type="i" direction="out"/>
+ <arg name="address" type="s" direction="out"/>
+ <arg name="flags" type="u" direction="out"/>
+</method>
address@hidden example
+
address@hidden elements can have the attributes @code{name}, @code{type}
+and @code{direction}. The @code{name} attribute is optional. The
address@hidden attribute stands for the @dfn{signature} of the argument
+in D-Bus. For a discussion of D-Bus types and their Lisp
+representation see @ref{Type address@hidden signatures
+are explained in the D-Bus specification
address@hidden://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-signatures}.}
+The @code{direction} attribute of an @code{arg} element can be only
address@hidden or @samp{out}; in case it is omitted, it defaults to
address@hidden
+
+A @code{signal} element of an @code{interface} has a similar
+structure. The @code{direction} attribute of an @code{arg} child
+element can be only @samp{out} here; which is also the default value.
+Example:
+
address@hidden
+<signal name="StateChanged">
+ <arg name="state" type="i"/>
+ <arg name="error" type="s"/>
+</signal>
address@hidden example
+
+A @code{property} element has no @code{arg} child
+element. It just has the attributes @code{name}, @code{type} and
address@hidden, which are all mandatory. The @code{access} attribute
+allows the values @samp{readwrite}, @samp{read}, and @samp{write}.
+Example:
+
address@hidden
+<property name="Status" type="u" direction="read"/>
address@hidden example
+
address@hidden elements can be children of @code{interface},
address@hidden, @code{signal}, and @code{property} elements. Unlike
+properties, which can change their values during lifetime of a D-Bus
+object, annotations are static. Often they are used for code
+generators of D-Bus langugae bindings. Example:
+
address@hidden
+<annotation name="de.berlios.Pinot.GetStatistics" value="pinotDBus"/>
address@hidden example
+
+Annotations have just @code{name} and @code{value} attributes, both
+must be strings.
+
@defun dbus-introspect bus service path
-Objects can publish there interfaces to the D-Bus. This function
-returns all interfaces of @var{service}, registered at object path
address@hidden at bus @var{bus}.
+This function returns all interfaces and sub-nodes of @var{service},
+registered at object path @var{path} at bus @var{bus}.
@var{bus} must be either the symbol @code{:system} or the symbol
@code{:session}. @var{service} must be a known service name, and
@@ -204,45 +329,506 @@
"/org/freedesktop/Hal/devices/computer")
@result{} "<!DOCTYPE node PUBLIC
- \"-//freedesktop//DTD D-BUS Object Introspection 1.0//EN\"
- \"http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd\";>
+ "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
+ "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd";>
<node>
- <interface name=\"org.freedesktop.Hal.Device\">
- <method name=\"GetAllProperties\">
- <arg name=\"properties\" direction=\"out\"
type=\"address@hidden@}\"/>
+ <interface name="org.freedesktop.Hal.Device">
+ <method name="GetAllProperties">
+ <arg name="properties" direction="out" type="address@hidden@}"/>
</method>
@dots{}
- <signal name=\"PropertyModified\">
- <arg name=\"num_updates\" type=\"i\"/>
- <arg name=\"updates\" type=\"a(sbb)\"/>
+ <signal name="PropertyModified">
+ <arg name="num_updates" type="i"/>
+ <arg name="updates" type="a(sbb)"/>
</signal>
</interface>
@dots{}
</node>"
@end lisp
-This example informs us, that the service @code{org.freedesktop.Hal}
-at object path @code{/org/freedesktop/Hal/devices/computer} offers the
-interface @code{org.freedesktop.Hal.Device} (and 2 other interfaces
+This example informs us, that the service @samp{org.freedesktop.Hal}
+at object path @samp{/org/freedesktop/Hal/devices/computer} offers the
+interface @samp{org.freedesktop.Hal.Device} (and 2 other interfaces
not documented here). This interface contains the method
address@hidden, which needs no input parameters, but returns
address@hidden, which needs no input parameters, but returns
as output parameter an array of dictionary entries (key-value pairs).
Every dictionary entry has a string as key, and a variant as value.
The interface offers also a signal, which returns 2 parameters: an
integer, and an array consisting of elements which are a struct of a
-string and 2 boolean values.
-
-Such type descriptions are called @dfn{signature} in D-Bus. For a
-discussion of D-Bus types and their Lisp representation see @ref{Type
address@hidden signatures are explained in the D-Bus
-specification
address@hidden://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-signatures}.
-The interfaces of the service @code{org.freedesktop.Hal} are described
-at
+string and 2 boolean address@hidden The interfaces of the service
address@hidden are described at
@uref{http://people.freedesktop.org/~david/hal-spec/hal-spec.html#interfaces}.}
@end defun
address@hidden dbus-introspect-xml bus service path
+This function has the same intention as function
address@hidden The returned value is a parsed XML tree,
+which can be used for further analysis. Example:
+
address@hidden
+(dbus-introspect-xml
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main")
+
address@hidden (node ((name . "/org/freedesktop/xesam/searcher/main"))
+ (interface ((name . "org.freedesktop.xesam.Search"))
+ (method ((name . "GetHitData"))
+ (arg ((name . "search") (type . "s") (direction . "in")))
+ (arg ((name . "hit_ids") (type . "au") (direction . "in")))
+ (arg ((name . "fields") (type . "as") (direction . "in")))
+ (arg ((name . "hit_data") (type . "aav") (direction . "out")))
+ )
+ @dots{}
+ (signal ((name . "HitsAdded"))
+ (arg ((name . "search") (type . "s")))
+ (arg ((name . "count") (type . "u")))
+ )
+ )
+ @dots{}
+ )
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-attribute object attribute
+It returns the @var{attribute} value of a D-Bus introspection
address@hidden @var{object} can be every subtree of a parsed XML tree
+as retrieved with @code{dbus-introspect-xml}. @var{attribute} must be
+a string according to the attribute names in the D-Bus specification.
+Example:
+
address@hidden
+(dbus-introspect-get-attribute
+ (dbus-introspect-xml :system "org.freedesktop.SystemToolsBackends"
+ "/org/freedesktop/SystemToolsBackends/UsersConfig")
+ "name")
+
address@hidden "/org/freedesktop/SystemToolsBackends/UsersConfig"
address@hidden lisp
+
+If @var{object} has no @var{attribute}, the function returns nil.
address@hidden defun
+
+
address@hidden Nodes and Interfaces
address@hidden Detecting object paths and interfaces.
+
+The first elements, to be introspected for a D-Bus object, are further
+object paths and interfaces.
+
address@hidden dbus-introspect-get-node-names bus service path
+All node names of @var{service} in D-Bus @var{bus} at object path
address@hidden are returned as list of strings. Example:
+
address@hidden
+(dbus-introspect-get-node-names
+ :session "org.gnome.seahorse" "/org/gnome/seahorse")
+
address@hidden ("crypto" "keys")
address@hidden lisp
+
+The node names stand for further object paths of the D-Bus
address@hidden, relative to @var{path}. In the example,
address@hidden/org/gnome/seahorse/crypto} and @samp{/org/gnome/seahorse/keys}
+are also object paths of the D-Bus service @samp{org.gnome.seahorse}.
address@hidden defun
+
address@hidden dbus-introspect-get-all-nodes bus service path
+This function returns all node names of @var{service} in D-Bus
address@hidden at object path @var{path}. It returns a list of strings
+with all object paths of @var{service}, starting at @var{path}.
+Example:
+
address@hidden
+(dbus-introspect-get-all-nodes :session "org.gnome.seahorse" "/")
+
address@hidden ("/" "/org" "/org/gnome" "/org/gnome/seahorse"
+ "/org/gnome/seahorse/crypto"
+ "/org/gnome/seahorse/keys"
+ "/org/gnome/seahorse/keys/openpgp"
+ "/org/gnome/seahorse/keys/openpgp/local"
+ "/org/gnome/seahorse/keys/openssh"
+ "/org/gnome/seahorse/keys/openssh/local")
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-interface-names bus service path
+There will be returned a list strings of all interface names of
address@hidden in D-Bus @var{bus} at object path @var{path}. This list
+will contain the default interface @samp{org.freedesktop.DBus.Introspectable}.
+
+Another default interface is @samp{org.freedesktop.DBus.Properties}.
+If present, @code{interface} elements can also have @code{property}
+children. Example:
+
address@hidden
+(dbus-introspect-get-interface-names
+ :system "org.freedesktop.Hal"
+ "/org/freedesktop/Hal/devices/computer")
+
address@hidden ("org.freedesktop.DBus.Introspectable"
+ "org.freedesktop.Hal.Device"
+ "org.freedesktop.Hal.Device.SystemPowerManagement"
+ "org.freedesktop.Hal.Device.CPUFreq")
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-interface bus service path interface
+Return @var{interface} of @var{service} in D-Bus @var{bus} at object
+path @var{path}. The return value is an XML element. @var{interface}
+must be a string, element of the list returned by
address@hidden Example:
+
address@hidden
+(dbus-introspect-get-interface
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search")
+
address@hidden (interface ((name . "org.freedesktop.xesam.Search"))
+ (method ((name . "GetHitData"))
+ (arg ((name . "search") (type . "s") (direction . "in")))
+ (arg ((name . "hit_ids") (type . "au") (direction . "in")))
+ (arg ((name . "fields") (type . "as") (direction . "in")))
+ (arg ((name . "hit_data") (type . "aav") (direction . "out")))
+ )
+ @dots{}
+ (signal ((name . "HitsAdded"))
+ (arg ((name . "search") (type . "s")))
+ (arg ((name . "count") (type . "u")))
+ )
+ )
address@hidden lisp
address@hidden defun
+
address@hidden
+With these functions, it is possible to retrieve all introspection
+data from a running system:
+
address@hidden
+(with-current-buffer (switch-to-buffer "*introspect*")
+ (erase-buffer)
+ (dolist (service (dbus-list-known-names :session))
+ (dolist (path (dbus-introspect-get-all-nodes :session service "/"))
+ ;; We want to introspect only elements, which have more than
+ ;; the default interface "org.freedesktop.DBus.Introspectable".
+ (when (delete
+ "org.freedesktop.DBus.Introspectable"
+ (dbus-introspect-get-interface-names :session service path))
+ (insert (message "\nservice: \"%s\" path: \"%s\"\n" service path)
+ (dbus-introspect :session service path))
+ (redisplay t)))))
address@hidden lisp
+
+
address@hidden Methods and Signal
address@hidden Applying the functionality.
+
+Methods and signals are the communicatione means to D-Bus. The
+following functions return their specifications.
+
address@hidden dbus-introspect-get-method-names bus service path interface
+Return a list of strings of all method names of @var{interface} of
address@hidden in D-Bus @var{bus} at object path @var{path}. Example:
+
address@hidden
+(dbus-introspect-get-method-names
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search")
+
address@hidden ("GetState" "StartSearch" "GetHitCount" "GetHits" "NewSession"
+ "CloseSession" "GetHitData" "SetProperty" "NewSearch"
+ "GetProperty" "CloseSearch")
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-method bus service path interface method
+This function returns @var{method} of @var{interface} as XML element.
+It must be located at @var{service} in D-Bus @var{bus} at object path
address@hidden @var{method} must be a string, element of the list
+returned by @code{dbus-introspect-get-method-names}. Example:
+
address@hidden
+(dbus-introspect-get-method
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search" "GetHitData")
+
address@hidden (method ((name . "GetHitData"))
+ (arg ((name . "search") (type . "s") (direction . "in")))
+ (arg ((name . "hit_ids") (type . "au") (direction . "in")))
+ (arg ((name . "fields") (type . "as") (direction . "in")))
+ (arg ((name . "hit_data") (type . "aav") (direction . "out")))
+ )
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-signal-names bus service path interface
+Return a list of strings of all signal names of @var{interface} of
address@hidden in D-Bus @var{bus} at object path @var{path}. Example:
+
address@hidden
+(dbus-introspect-get-signal-names
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search")
+
address@hidden ("StateChanged" "SearchDone" "HitsModified"
+ "HitsRemoved" "HitsAdded")
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-signal bus service path interface signal
+This function returns @var{signal} of @var{interface} as XML element.
+It must be located at @var{service} in D-Bus @var{bus} at object path
address@hidden @var{signal} must be a string, element of the list
+returned by @code{dbus-introspect-get-signal-names}. Example:
+
address@hidden
+(dbus-introspect-get-signal
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search" "HitsAdded")
+
address@hidden (signal ((name . "HitsAdded"))
+ (arg ((name . "search") (type . "s")))
+ (arg ((name . "count") (type . "u")))
+ )
address@hidden lisp
address@hidden defun
+
+
address@hidden Properties and Annotations
address@hidden What else to know about interfaces.
+
+Interfaces can have properties. These can be exposed via the
address@hidden address@hidden
address@hidden://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties}}.
+That is, properties can be retrieved and changed during lifetime of an
+element.
+
+Annotations, on the other hand, are static values for an element.
+Often, they are used to instruct generators, how to generate code from
+the interface for a given language binding.
+
address@hidden dbus-introspect-get-property-names bus service path interface
+Return a list of strings with all property names of @var{interface} of
address@hidden in D-Bus @var{bus} at object path @var{path}. Example:
+
address@hidden
+(dbus-introspect-get-property-names
+ :session "org.kde.kded" "/modules/networkstatus"
+ "org.kde.Solid.Networking.Client")
+
address@hidden ("Status")
address@hidden lisp
+
+If an interface declares properties, the corresponding element supports
+also the @samp{org.freedesktop.DBus.Properties} interface.
address@hidden defun
+
address@hidden dbus-introspect-get-property bus service path interface property
+This function returns @var{property} of @var{interface} as XML element.
+It must be located at @var{service} in D-Bus @var{bus} at object path
address@hidden @var{property} must be a string, element of the list
+returned by @code{dbus-introspect-get-property-names}.
+
+A @var{property} value can be retrieved by the function
address@hidden Example:
+
address@hidden
+(dbus-introspect-get-property
+ :session "org.kde.kded" "/modules/networkstatus"
+ "org.kde.Solid.Networking.Client" "Status")
+
address@hidden (property ((access . "read") (type . "u") (name . "Status")))
+
+(dbus-introspect-get-attribute
+ (dbus-introspect-get-property
+ :session "org.kde.kded" "/modules/networkstatus"
+ "org.kde.Solid.Networking.Client" "Status")
+ "access")
+
address@hidden "read"
address@hidden lisp
address@hidden defun
+
address@hidden dbus-get-property bus service path interface property
+This function returns the value of @var{property} of @var{interface}.
+It will be checked at @var{bus}, @var{service}, @var{path}. The
+result can be any valid D-Bus value, or nil if there is no
address@hidden Example:
+
address@hidden
+(dbus-get-property
+ :session "org.kde.kded" "/modules/networkstatus"
+ "org.kde.Solid.Networking.Client" "Status")
+
address@hidden 4
address@hidden lisp
address@hidden defun
+
address@hidden dbus-set-property bus service path interface property value
+Set value of @var{property} of @var{interface} to @var{value}. It
+will be checked at @var{bus}, @var{service}, @var{path}. When the
+value has been set successful, the result is @var{value}. Otherwise,
address@hidden is returned. Example:
+
address@hidden
+(dbus-set-property
+ :session "org.kde.kaccess" "/MainApplication"
+ "com.trolltech.Qt.QApplication" "doubleClickInterval" 500)
+
address@hidden 500
address@hidden lisp
address@hidden defun
+
address@hidden dbus-get-all-properties bus service path interface
+This function returns all properties of @var{interface}. It will be
+checked at @var{bus}, @var{service}, @var{path}. The result is a list
+of cons. Every cons contains the name of the property, and its value.
+If there are no properties, @code{nil} is returned. Example:
+
address@hidden
+(dbus-get-all-properties
+ :session "org.kde.kaccess" "/MainApplication"
+ "com.trolltech.Qt.QApplication")
+
address@hidden (("cursorFlashTime" . 1000) ("doubleClickInterval" . 500)
+ ("keyboardInputInterval" . 400) ("wheelScrollLines" . 3)
+ ("globalStrut" 0 0) ("startDragTime" . 500)
+ ("startDragDistance" . 4) ("quitOnLastWindowClosed" . t)
+ ("styleSheet" . ""))
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-annotation-names bus service path interface
&optional name
+Return a list of all annotation names as list of strings. If
address@hidden is @code{nil}, the annotations are children of
address@hidden, otherwise @var{name} must be a @code{method},
address@hidden, or @code{property} XML element, where the annotations
+belong to. Example:
+
address@hidden
+(dbus-introspect-get-annotation-names
+ :session "de.berlios.Pinot" "/de/berlios/Pinot"
+ "de.berlios.Pinot" "GetStatistics")
+
address@hidden ("de.berlios.Pinot.GetStatistics")
address@hidden lisp
+
+Default annotation address@hidden
address@hidden://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format}}
+are
+
address@hidden @samp
address@hidden org.freedesktop.DBus.Deprecated
+Whether or not the entity is deprecated; defaults to @code{nil}
+
address@hidden org.freedesktop.DBus.GLib.CSymbol
+The C symbol; may be used for @code{methods} and @code{interfaces}
+
address@hidden org.freedesktop.DBus.Method.NoReply
+If set, don't expect a reply to the @code{method} call; defaults to @code{nil}
address@hidden table
address@hidden defun
+
address@hidden dbus-introspect-get-annotation bus service path interface name
annotation
+Return annotation @var{ANNOTATION} as XML object. If @var{name} is
address@hidden, @var{ANNOTATION} is a child of @var{interface}, otherwise
address@hidden must be the name of a @code{method}, @code{signal}, or
address@hidden XML element, where the @var{ANNOTATION} belongs to.
+
+An attribute value can be retrieved by
address@hidden Example:
+
address@hidden
+(dbus-introspect-get-annotation
+ :session "de.berlios.Pinot" "/de/berlios/Pinot"
+ "de.berlios.Pinot" "GetStatistics"
+ "de.berlios.Pinot.GetStatistics")
+
address@hidden (annotation ((name . "de.berlios.Pinot.GetStatistics")
+ (value . "pinotDBus")))
+
+(dbus-introspect-get-attribute
+ (dbus-introspect-get-annotation
+ :session "de.berlios.Pinot" "/de/berlios/Pinot"
+ "de.berlios.Pinot" "GetStatistics"
+ "de.berlios.Pinot.GetStatistics")
+ "value")
+
address@hidden "pinotDBus"
address@hidden lisp
address@hidden defun
+
+
address@hidden Arguments and Signatures
address@hidden The final details.
+
+Methods and signals have arguments. They are described in the
address@hidden XML elements.
+
address@hidden dbus-introspect-get-argument-names bus service path interface
name
+Return a list of all argument names as list of strings. @var{name}
+must be a @code{method} or @code{signal} XML element. Example:
+
address@hidden
+(dbus-introspect-get-argument-names
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search" "GetHitData")
+
address@hidden ("search" "hit_ids" "fields" "hit_data")
address@hidden lisp
+
+Argument names are optional; the function can return @code{nil}
+therefore, even if the method or signal has arguments.
address@hidden defun
+
address@hidden dbus-introspect-get-argument bus service path interface name arg
+Return argument @var{ARG} as XML object. @var{name}
+must be a @code{method} or @code{signal} XML element. Example:
+
address@hidden
+(dbus-introspect-get-argument
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search" "GetHitData" "search")
+
address@hidden (arg ((name . "search") (type . "s") (direction . "in")))
address@hidden lisp
address@hidden defun
+
address@hidden dbus-introspect-get-signature bus service path interface name
&optional direction
+Return signature of a @code{method} or @code{signal}, represented by
address@hidden, as string.
+
+If @var{name} is a @code{method}, @var{direction} can be either
address@hidden or @samp{out}. If @var{direction} is @code{nil}, @samp{in}
+is assumed.
+
+If @var{name} is a @code{signal}, and @var{direction} is
address@hidden, @var{direction} must be @samp{out}. Example:
+
address@hidden
+(dbus-introspect-get-signature
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search" "GetHitData" "in")
+
address@hidden "sauas"
+
+(dbus-introspect-get-signature
+ :session "org.freedesktop.xesam.searcher"
+ "/org/freedesktop/xesam/searcher/main"
+ "org.freedesktop.xesam.Search" "HitsAdded")
+
address@hidden \"su\""
address@hidden lisp
address@hidden defun
+
@node Type Conversion
@chapter Mapping Lisp types and D-Bus types.
@@ -514,13 +1100,13 @@
Emacs can also offer own methods, which can be called by other
applications. These methods could be an implementation of an
-interface of a well known service, like @code{org.freedesktop.TextEditor}.
+interface of a well known service, like @samp{org.freedesktop.TextEditor}.
It could be also an implementation of an own interface. In this case,
-the service name must be @code{org.gnu.Emacs}. The object path shall
-begin with @code{/org/gnu/Emacs/@strong{Application}/}, and the
+the service name must be @samp{org.gnu.Emacs}. The object path shall
+begin with @samp{/org/gnu/Emacs/@strong{Application}/}, and the
interface name shall be @address@hidden
address@hidden@strong{Application}} is the name of the application which
address@hidden@strong{Application}} is the name of the application which
provides the interface.
@defun dbus-register-method bus service path interface method handler
@@ -574,7 +1160,7 @@
my-method-handler))
@end lisp
-If you invoke the method @code{org.freedesktop.TextEditor.OpenFile}
+If you invoke the method @samp{org.freedesktop.TextEditor.OpenFile}
from another D-Bus application with a filename as parameter, the file
is opened in Emacs, and the method returns either @var{true} or
@var{false}, indicating the success if the method. As test tool one
@@ -675,12 +1261,12 @@
my-signal-handler))
@end lisp
-As we know from the inspection data of interface
address@hidden, the signal @code{DeviceAdded}
+As we know from the introspection data of interface
address@hidden, the signal @samp{DeviceAdded}
provides one single parameter, which is mapped into a Lisp string.
The callback function @code{my-dbus-signal-handler} must define one
single string argument therefore. Plugging an USB device to your
-machine, when registered for signal @code{DeviceAdded}, will show you
+machine, when registered for signal @samp{DeviceAdded}, will show you
which objects the GNU/Linux @code{hal} daemon adds.
@end defun