Image of Android Wireless Application Development
Image of Linux Kernel Development (3rd Edition)
Image of XSLT 2.0 and XPath 2.0 Programmer's Reference (Programmer to Programmer)
Image of Beginning Google Maps API 3

GNOME Shell 3.6 DBus Support

I have written before about the DBus support in GNOME Shell. In GNOME Shell 3.6, there are significant changes to the DBus interface; hence this post. The file that contains the DBus interface definitions is shellDBus.js. It contains the following two DBus interface definitions: <interface name=”org.gnome.Shell”> <method name=”Eval”> <arg type=”s” name=”script” direction=”in”> </arg> <arg type=”b” name=”success” direction=”out”> </arg> <arg type=”s” name=”result” direction=”out”> </arg> </method> <method name=”ScreenshotArea”> <arg type=”i” name=”x” direction=”in”> </arg> <arg type=”i” name=”y” direction=”in”> </arg> <arg type=”i” name=”width” direction=”in”> </arg> <arg type=”i” name=”height” direction=”in”> </arg> <arg type=”b” name=”flash” direction=”in”> </arg> <arg type=”s” name=”filename” direction=”in”> </arg> <arg type=”b” name=”success” direction=”out”>

Introduction to Udisks

Udisks (formerly called DeviceKit-disks) is a replacement for part of the functionality which used be provided by the now deprecated HAL (Hardware Abstraction Layer). Essentially it is an abstraction for enumerating disk and storage devices and performing operations on them. Udisks provides: A daemon (udisks-daemon) that implements well-defined D-Bus interfaces that can be used to query and manipulate disk and storage devices. A command-line tool (udisks), that can be used to query and use the daemon. Actions that a user can perform using udisks can be restricted using PolicyKit. Udisks relies on the kernel and udev where possible but does

Ruby D-Bus and Fedora 11

Earlier this year I wrote a number of posts about monitoring and interacting with D-Bus using shell scripts. In this post I use Ruby to monitor and interact with D-Bus enabled applications. If you are unfamiliar with D-Bus, a good starting point is this tutorial by the authors of the D-Bus specification. I used the standard out-of-the-box version of Ruby which comes with Fedora 11. $ ruby –version ruby 1.8.6 (2009-06-08 patchlevel 369) [x86_64-linux] Those readers who are familiar with Ruby will recognize that this version of Ruby is quite old by Ruby standards and is in maintenance mode

Monitoring D-Bus

Because D-Bus operates for the most part under the hood invisible to the user, means of monitoring D-Bus messages is important for both activation and debugging purposes.  In this post I examine how to monitor and act on such messages.  I assume that you are relatively familiar with D-Bus. If not, you should look at my previous posts on D-Bus to gain an understanding of the basic concepts. Probably the most commonly used tool is the command line utility dbus-monitor which was written by Philip Blundell as part of the reference D-Bus implementation and which is standard on most D-Bus

Scripting Tomboy

Tomboy is an open source GNOME desktop note-taking application which is written in C# and utilizing the Mono runtime, Gtk# and the GtkSpell spell-checker. The actual release of Tomboy which comes with Fedora 10 is version 0.12.0.  This includes a comprehensive D-Bus interface which makes it possible to create, modify and display Tomcat notes from your shell scripts.  This post provides an overview of the available D-Bus methods and includes a number of examples for you to experiment with.  See my previous post on D-Bus scripting if you are unfamilar with the basic concepts of D-Bus scripting. First we will