Development/Tutorials/D-Bus/Accessing Interfaces - Revision history

AnneW at 12:34, 13 July 2012

2012-07-13T12:34:30Z

Neverendingo: Text replace - "" to ""

2011-06-29T20:50:53Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:44:41Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:44, 29 June 2011
			
Line 188:
Line 188:
  With the path to the XML in hand, we then add something like this to our {{path|CMakeLists.txt}}:   With the path to the XML in hand, we then add something like this to our {{path|CMakeLists.txt}}:
    
− <code> + <syntaxhighlight lang="text">
  PKGCONFIG_GETVAR(dbus-1 prefix DBUS_PREFIX)   PKGCONFIG_GETVAR(dbus-1 prefix DBUS_PREFIX)
  set(network_xml ${DBUS_PREFIX}/interfaces/org.foo.bar.xml)   set(network_xml ${DBUS_PREFIX}/interfaces/org.foo.bar.xml)



Neverendingo: Text replace - "" to ""

2011-06-29T20:31:44Z
Text replace - "<code cppqt n>" to "<syntaxhighlight lang="cpp-qt" line>"

				
				
				
				
			
			← Older revision
			Revision as of 20:31, 29 June 2011
			
Line 35:
Line 35:
    
  <!-- <pre> -->   <!-- <pre> -->
− <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + <syntaxhighlight lang="cpp-qt" line>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                 "/network",                                                  "/network",
                                                 "",                                                  "",
Line 53:
Line 53:
  Sending arguments along with the method call is quite straight forward. First we need to create a {{qt|QList}} of {{qt|QVariant}} objects and then add those to our D-Bus message. So if the <tt>ping</tt> method in the above took a hostname as a parameter, we might alter the code in this way (note lines 5 through 7):   Sending arguments along with the method call is quite straight forward. First we need to create a {{qt|QList}} of {{qt|QVariant}} objects and then add those to our D-Bus message. So if the <tt>ping</tt> method in the above took a hostname as a parameter, we might alter the code in this way (note lines 5 through 7):
    
− <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + <syntaxhighlight lang="cpp-qt" line>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                 "/network",                                                  "/network",
                                                 "",                                                  "",
Line 64:
Line 64:
  Alternatively, {{qt|QDBusMessage}} provides a convenience method to appending parameters to the message, by way of its "operator<<" function. The above example becomes:   Alternatively, {{qt|QDBusMessage}} provides a convenience method to appending parameters to the message, by way of its "operator<<" function. The above example becomes:
    
− <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + <syntaxhighlight lang="cpp-qt" line>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                 "/network",                                                  "/network",
                                                 "",                                                  "",
Line 78:
Line 78:
    
    
− <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + <syntaxhighlight lang="cpp-qt" line>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                  "/network",                                                   "/network",
                                                  "",                                                   "",
Line 103:
Line 103:
  Here is an example of {{qt|QDBusInterface}} usage which we will then step through line by line:   Here is an example of {{qt|QDBusInterface}} usage which we will then step through line by line:
    
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  QString hostname("kde.org");   QString hostname("kde.org");
  QDBusConnection bus = QDBusConnection::sessionBus();   QDBusConnection bus = QDBusConnection::sessionBus();
Line 172:
Line 172:
  What would be truly great is if we could simply instantiate a local object that represented a given service and start using it right away. Perhaps something like this:   What would be truly great is if we could simply instantiate a local object that represented a given service and start using it right away. Perhaps something like this:
    
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  org::foo::bar::network *interface =     org::foo::bar::network *interface =  
       new org::foo::bar::network("org.foo.bar", "/network",        new org::foo::bar::network("org.foo.bar", "/network",



OpenIDUser89: /* Using QDBusInterface */
2011-05-31T20:52:05Z
‎Using QDBusInterface

				
				
				
				
			
			← Older revision
			Revision as of 20:52, 31 May 2011
			
Line 134:
Line 134:
  interface->callWithCallback("listInterfaces", args,   interface->callWithCallback("listInterfaces", args,
                               this,                                this,
−                              SLOT(interfaceList(QDBusMessage)); +                              SLOT(interfaceList(QDBusMessage)));
    
  connect(interface, SIGNAL(interfaceUp(QString)),   connect(interface, SIGNAL(interfaceUp(QString)),



AnneW: Undo revision 53394 by Annewilson (Talk)
2010-08-11T18:12:40Z
Undo revision 53394 by Annewilson (Talk)

				
				
				
				
			
			← Older revision
			Revision as of 18:12, 11 August 2010
			
Line 34:
Line 34:
  By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:   By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:
    
− <pre> + <!-- <pre> -->
− QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                 "/network",                                                  "/network",
                                                 "",                                                  "",
                                                 "ping");                                                  "ping");
  bool queued = QDBusConnection::sessionBus().send(m);   bool queued = QDBusConnection::sessionBus().send(m);
−   + </code>
− </pre> + <!-- </pre> -->
    
  In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.   In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.



AnneW: Test using  tags
2010-08-11T14:50:51Z
Test using <pre> tags

				
				
				
				
			
			← Older revision
			Revision as of 14:50, 11 August 2010
			
Line 34:
Line 34:
  By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:   By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:
    
− <!-- <pre> --> + <pre>
− <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                 "/network",                                                  "/network",
                                                 "",                                                  "",
                                                 "ping");                                                  "ping");
  bool queued = QDBusConnection::sessionBus().send(m);   bool queued = QDBusConnection::sessionBus().send(m);
− </code> +  
− <!-- </pre> --> + </pre>
    
  In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.   In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.



Bluesnik: /* Calling a D-Bus Method */
2010-08-10T20:29:25Z
‎Calling a D-Bus Method

				
				
				
				
			
			← Older revision
			Revision as of 20:29, 10 August 2010
			
Line 34:
Line 34:
  By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:   By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:
    
− <!-- <code cppqt n> --> + <!-- <pre> -->
− <pre>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                 "/network",                                                  "/network",
                                                 "",                                                  "",
                                                 "ping");                                                  "ping");
  bool queued = QDBusConnection::sessionBus().send(m);   bool queued = QDBusConnection::sessionBus().send(m);
− </pre> + </code>
− <!-- </code> --> + <!-- </pre> -->
    
  In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.   In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.



Bluesnik: /* Calling a D-Bus Method */
2010-08-10T20:22:53Z
‎Calling a D-Bus Method

				
				
				
				
			
			← Older revision
			Revision as of 20:22, 10 August 2010
			
Line 34:
Line 34:
  By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:   By way of example, to access the (fictional) <tt>ping</tt> method on the {{path|/network}} object in the <tt>org.foo.bar</tt> service, one might do this:
    
− <code cppqt n>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar", + <!-- <code cppqt n> -->
  + <pre>QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
                                                 "/network",                                                  "/network",
                                                 "",                                                  "",
                                                 "ping");                                                  "ping");
− bool queued = QDBusConnection::sessionBus().send(m);</code> + bool queued = QDBusConnection::sessionBus().send(m);
  + </pre>
  + <!-- </code> -->
    
  In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.   In line 5 of the above example we queue the message for sending on the current session bus. We get a <tt>bool</tt> returned letting us know if the queueing was successful or not.





VHanda: Changed QT4_ADD_DBUS_INTERFACE to qt4_add_dbus_interface
2010-06-19T21:27:44Z
Changed QT4_ADD_DBUS_INTERFACE to qt4_add_dbus_interface

				
				
				
				
			
			← Older revision
			Revision as of 21:27, 19 June 2010
			
Line 188:
Line 188:
  PKGCONFIG_GETVAR(dbus-1 prefix DBUS_PREFIX)   PKGCONFIG_GETVAR(dbus-1 prefix DBUS_PREFIX)
  set(network_xml ${DBUS_PREFIX}/interfaces/org.foo.bar.xml)   set(network_xml ${DBUS_PREFIX}/interfaces/org.foo.bar.xml)
− QT4_ADD_DBUS_INTERFACE(myapp_SRCS ${network_xml} network_interface ) + qt4_add_dbus_interface(myapp_SRCS ${network_xml} network_interface )
  </code>   </code>

← Older revision		Revision as of 12:34, 13 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Tutorials/D-Bus/Accessing_Interfaces}}~~

	{{TutorialBrowser\|		{{TutorialBrowser\|

@@ Line 40: / Line 40: @@
                                                "ping");
 bool queued = QDBusConnection::sessionBus().send(m);
-</code>
+</syntaxhighlight>
 <!-- </pre> -->
@@ Line 60: / Line 60: @@
 args.append("kde.org");
 m.setArguments(args);
-bool queued = QDBusConnection::sessionBus().send(m);</code>
+bool queued = QDBusConnection::sessionBus().send(m);</syntaxhighlight>
 Alternatively, {{qt|QDBusMessage}} provides a convenience method to appending parameters to the message, by way of its "operator<<" function. The above example becomes:
@@ Line 69: / Line 69: @@
                                                "ping");
 m << "kde.org";
-bool queued = QDBusConnection::sessionBus().send(m);</code>
+bool queued = QDBusConnection::sessionBus().send(m);</syntaxhighlight>
 {{note|The arguments must appear in the {{qt|QList}} in the same order they are expected by the D-Bus method being called.}}
@@ Line 83: / Line 83: @@
                                                 "ping");
 m << "kde.org";
-QDBusMessage response = QDBusConnection::sessionBus().call(m);</code>
+QDBusMessage response = QDBusConnection::sessionBus().call(m);</syntaxhighlight>
 The <tt>response</tt> will be either of type <tt>QDBusMessage::ReplyMessage</tt> or <tt>QDBusMessage::ErrorMessage</tt> depending on whether it was successful or not. We can look through the values returned by retrieving the arguments with the <tt>{{qt|QDBusMessage}}::arguments()</tt> method which returns a <tt>{{qt|QList}}&lt;{{qt|QVariant}}&gt;</tt>.
@@ Line 138: / Line 138: @@
 connect(interface, SIGNAL(interfaceUp(QString)),
          this, SLOT(interfaceUp(QString)));
-</code>
+</syntaxhighlight>
 === Synchronous Calls ===
@@ Line 178: / Line 178: @@
                              this);
 interface->ping("kde.org");
-</code>
+</syntaxhighlight>
 Fortunately for us, this is precisely what Qt allows us to do. The only requirement is an XML file describing the D-Bus service. Such files are installed in the D-Bus prefix in the {{path|interfaces}} directory.
@@ Line 192: / Line 192: @@
 set(network_xml ${DBUS_PREFIX}/interfaces/org.foo.bar.xml)
 qt4_add_dbus_interface(myapp_SRCS ${network_xml} network_interface )
-</code>
+</syntaxhighlight>
 This will generate two files at build time, {{path|network_interface.h}} and {{path|network_interface.cpp}}, and add them to the compiled application. We can then simply <tt>#include "network_interface.h"</tt> and use the generated class as seen in the example above.