This post assumes that you have already installed Fedora 17 and that all software packages are current, i.e. yum update has been run. As root, create a new text file called fedora-cinnamon in the /etc/yum.repos.d subdirectory containing the following lines: [fedora-cinnamon] name=Cinnamon user interface baseurl=http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-$releasever/$basearch/ enabled=1 skip_if_unavailable=1 gpgcheck=0 [fedora-cinnamon-source] name=Cinnamon user interface – Source baseurl=http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-$releasever/SRPMS enabled=0 skip_if_unavailable=1 gpgcheck=0 You can check that the fedora-cinnamon repo is available to yum as follows: # yum repolist Loaded plugins: langpacks, presto, refresh-packagekit repo id repo name status fedora Fedora 17 – x86_64 26,893 fedora-cinnamon Cinnamon provides core user interface functions for the 1
This post assumes that you already have the Cinnamon shell installed on your computer and you want to install new Cinnomon themes for your personnal use rather than for global use. If you do not already have a ~/.themes subdirectory, you need to create it. The default permissions are fine. You can either use the Cinnamon Settings tool (Menu->Preferences->Cinnamon Settings) to preview, select and download a new theme, or you can download a theme directly from here. Themes files are compressed and packaged as a single zip file. Move the downloaded zipped theme file to ~/.themes and unzip it. A
In this post, I demonstrate how you can add D-Bus support to a GNOME Shell or Cinnamon extension and allow a command line utility to control the operating characteristics of the extension via a command line utility.
This post discusses the D-Bus interface to the GNOME Shell and Cinnamon and shows you how a simple command line tool called cinnamon-tool can be used to enable or disable Cinnamon extensions via D-Bus.
The documentation on retrieving or setting an D-Bus object’s properties using Python is pityful and mostly inaccurate. Recently GDBus has replaced dbus-glib as the preferred way to interface with D-Bus on GNOME platforms. The central concepts of D-Bus are modelled in a very similar way in dbus-glib and GDBus. Both have objects representing connections, proxies and method invocations. However there are some important differences: dbus-glib uses the D-Bus libdbus reference implementation, GDBus does not. Instead, it relies on GIO streams as transport layer, and has its own implementation for the the D-Bus connection setup and authentication. dbus-glib uses the GObject