|
|
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
D-Bus (Desktop Bus) is a low-latency, low-overhead, easy-to-use message bus technology which supports application launch and linking. It is primarly used on GNU/Linux desktops but has been ported to other platforms including Microsoft Windows and Apple Mac OS X.  This post provides a quick overview of D-Bus concepts, some history, and some examples of how to use D-Bus in your shell scripts. Originally both the KDE and GNOME desktop projects used CORBA for inter-application communication. Over time however, for various reasons, KDE migrated from CORBA to Desktop Comunications Protocol (DCOP) and GNOME migrated to Bonono. This lead to the situation
Recent releases of Fedora and other GNU/Linux distributions include a Hardware Abstraction Layer (HAL) which is used to support device plug-and-play capabilities. In this post I will show you how your shell scripts can use HAL to retrieve device and system information. The term HAL is overloaded as it used to refer both to a specification and the actual software which implements the specification. From an application developers viewpoint, HAL is way to enumerate the capabilities and features of hardware attached to a system and receive notification when something about the hardware changes. First, a very quick overview of HAL.
Pattern matching is an important component of any modern shell. The ksh93 shell supports both regular expressions as well as what is called extended patterns. Extended patterns can be thought of as class or type of extended regular expressions. The purpose of this post is to explain, with some examples, how to use the power of extended patterns in your ksh93 scripts.
In previous posts, I discussed the SpiderMonkey command line shell js and how to add support to it to enable full access (read, write, create, copy, delete, etc.) to the local filesystem via the File object and the NSPR library. While rumaging around in the source code and documentation for js, I found that js partially supported the EX4 XML extension via a user configurable option. This post looks at what it takes to load an XML document into js from your local filesystem, process it and write out the resulting document to your local filesystem using File objects and
|
|