m (Depends -> license)
m (User:Nielsslot/RubyPlasmaGettingStartedPort moved to Development/Tutorials/Plasma/Ruby/GettingStarted: This is a 'translation' of the Python tutorial to Ruby. It's tested and works with 4.2rc1. Which is more then I can say about the old Ruby tutor)
Warning: This is a plain 'port' of the Getting Started article on Python and Plasma. I have changed the text where necessary for Ruby, and of course changed the example. Some things however might be incorrect. For the Python Tutorial see here.
In this tutorial we'll cover setting up a very simple plasma applet in Ruby, and how to install it and run it, basically the edit, install, run and debug cycle. To follow this you will need to have KDE 4.2 or later installed, and also the ruby support for plasma and related dependencies. I'm going to assume that you are using a unix-style operating system such as Linux of *BSD and aren't adverse to the shell.
The first step for any software project is to set up your project's directory on disk. For this tutorial we are going to create a very simple "hello-ruby" applet. Create a directory on somewhere called hello-ruby which in turn contains a contents directory which then contains a code directory. This command below will do all this.
mkdir -p hello-ruby/contents/code
This creates a simple directory structure which also matches the package structure expect by the plasmapkg command. More on this later.
In the hello-ruby directory create a file called metadata.desktop and open it in your text editor. Copy the following code into metadata.desktop.
This metadata.desktop file list important information needed by Plasma to load the applet, and also information about what the applet is and who created it. The Name field lists the name of the applet. This field can also be listed multiple times as different translations. Here I've just given a Dutch translation of the name. The [nl] indicates the language of the field.
The Type and ServiceType fields identify what kind of thing this desktop file is describing. Here we say that we have a plasma applet.
The Icon field gives the name of the icon to associate with this applet. The icon is typically shown in things such as the "Add widget" dialog in Plasma.
The X-Plasma-API and X-Plasma-MainScript fields are used specifically by Plasma to find the correct script-engine to use when loading and running the applet.
Most of the X-KDE-PluginInfo-* fields give extra information about who created the applet. X-KDE-PluginInfo-Category lists a category which this applet belongs to. http://techbase.kde.org/Projects/Plasma/PIG has a list of acceptable category names.
Create a file in the contents/code directory called main.rb, open it up in your text editor and put this code in it and save it.
class Main < PlasmaScripting::Applet def initialize parent super parent end
def init self.has_configuration_interface = false resize 125, 125 self.aspect_ratio_mode = Plasma::Square end
def paintInterface(painter, option, rect) painter.save painter.pen = Qt::Color.new Qt::white painter.draw_text rect, Qt::AlignVCenter | Qt::AlignHCenter, "Hello Ruby!" painter.restore end end
This is basically the simplest applet which actually does something. The code starts out with the usual copyright notice and license information which I've actually left out for now.
Next up is the loading of Ruby support in Plasma. Only loading plasma_applet is enough as it will load the rest of the Qt and KDE Ruby bindings. In order to create applets which can be packaged and delivered to users across the network via KDE's Get Hot New Stuff (GHNS) framework, we need to use the PlasmaScripting::Applet class as a base class for our applet.
In our main class the constructor method (initialize) is almost empty and only forwards the call to the superclass. It's recommended to put most of the initialisation code in the init method. After Plasma has constructed and initialised the applet, Plasma will call the init method on the applet to let it continue setting itself up. Our init method is rather short. We just tell Plasma that we don't have a configuration dialog and we set up the initial size of the applet.
The paintInterface method is where we draw our "Hello Ruby" message. First we save the state / settings of the given QPainter object by calling save. Then we set the color to white and use drawText to draw our message. Finally we call restore which resets the QPainter settings back to how it was when paintInterface was called.
Plasma applets can be packaged in zip files and installed using the plasmapkg command line tool. The directory structure which we have used for our project matches that need in the zip file. All we have to do is zip it update. Run the following command from inside the hello-ruby directory.
zip -r ../hello-ruby.zip .
This will create the hello-ruby.zip file in the directory just above the hello-ruby directory. Go to this directory in the shell and run this plasmapkg command to install our little hello-ruby applet.
plasmapkg -i hello-ruby.zip
This installs the applet into your home directory. Now we can run it. When developing applets it is more convenient to use the plasmoidviewer. This is a little utility which displays an applet in a window instead of you having to use your desktop. This command below will run our applet.
You should now be able to see the fruits of your labor.
To uninstall our applet we use plasmapkg again with its -r option.
plasmapkg -r hello-ruby
This tutorial covers very basics of developing Plasma applets using Ruby. Most of the material discussed here is boring but important "boilerplate" stuff which stays mostly the same between every applet project. In future tutorials we can move on to move exciting things than just displaying a single line of static text.
In the next tutorial we explain how to use Plasma's specialized widgets in your applet instead of manually implementing the paintInterface method.