Difference between revisions of "Development/Tutorials/Plasma/RubyApplet"

Jump to: navigation, search
Line 1: Line 1:
 
==Abstract==
 
==Abstract==
  
This tutorial shows how to create your own Plasma Widget/Applet/Plasmoid using the Ruby scripting language.
+
This tutorial shows how to create your own Plasma Widget/Applet/Plasmoid using the Ruby scripting language.  
  
 
See also:
 
See also:
* [[Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]
 
 
* [http://www.kdedevelopers.org/node/3560 Writing Plasma Applets in C# and Ruby]
 
* [http://www.kdedevelopers.org/node/3560 Writing Plasma Applets in C# and Ruby]
 
* [http://websvn.kde.org/trunk/KDE/kdebindings/ruby/plasma/examples/ Ruby and Plasma examples]
 
* [http://websvn.kde.org/trunk/KDE/kdebindings/ruby/plasma/examples/ Ruby and Plasma examples]
 +
* [[Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]
 +
* [[Development/Tutorials/Plasma|Plasma Tutorials]]
  
 
==The desktop file==
 
==The desktop file==
Line 37: Line 38:
 
==The Ruby Script==
 
==The Ruby Script==
  
It follows the Ruby scripting code which does implement the whole functionality to display a webbrowser within the applet and to browse around using the displayed links.
+
It follows the Ruby scripting code which does implement the whole functionality to display a webbrowser within the applet and to browse around those content.
  
[http://websvn.kde.org/trunk/KDE/kdebindings/ruby/plasma/examples/applets/webapplet/web_applet.rb?view=markup web_applet.rb]
+
The [http://websvn.kde.org/trunk/KDE/kdebindings/ruby/plasma/examples/applets/webapplet/web_applet.rb?view=markup web_applet.rb] ruby script looks like;
  
 
<code ruby>
 
<code ruby>

Revision as of 00:50, 14 July 2008

Contents

Abstract

This tutorial shows how to create your own Plasma Widget/Applet/Plasmoid using the Ruby scripting language.

See also:

The desktop file

The desktop file is the entry-point to our applet. It does define what the applet is for and how it should be loaded and handled by plasma.

For our webbrowser applet we use the plasma-ruby-applet-web.desktop desktop file which looks like;

[Desktop Entry] Name=Ruby Web Browser Icon=internet-web-browser

Type=Service ServiceTypes=Plasma/Applet

X-KDE-Library=krubypluginfactory X-KDE-PluginKeyword=plasma_ruby_web_applet/web_applet.rb X-KDE-PluginInfo-Name=plasma-ruby-web-applet

X-KDE-PluginInfo-Version=0.1 X-KDE-PluginInfo-Category=Web X-KDE-PluginInfo-Depends=QtRuby X-KDE-PluginInfo-License=GPL X-KDE-PluginInfo-EnabledByDefault=true

The important parts within those desktop service file are the referenced X-KDE-Library which will be loaded on request and is responsible for executing our with X-KDE-PluginKeyword defined Ruby scrip file. Our applet will be known by Plasma under the unique name "plasma-ruby-web-applet".

The Ruby Script

It follows the Ruby scripting code which does implement the whole functionality to display a webbrowser within the applet and to browse around those content.

The web_applet.rb ruby script looks like;

  1. import the plasma-applet functionality which we need to
  2. implement our own webbrowser applet.

require 'plasma_applet'

  1. We define an own module

module PlasmaRubyWebApplet

 # The WebApplet class does implement a Plasma::Applet.
 class WebApplet < Plasma::Applet
   # The both slots used by our applet.
   slots 'load(QUrl)',
         'loadFinished(bool)'
   # Constructor for our WebApplet class.
   def initialize(parent, args)
     super
   end
   # On initialization this method will be called by plasma. Here we
   # are able to do expensive initialization work to show something
   # within our applet.
   def init
     # Let's start with a nice default size.
     resize(600, 400)
     # Create the Browser widget which will display the content
     # of webpages.
     @page = Plasma::WebContent.new(self)
     @page.page = Qt::WebPage.new(@page)
     @page.page.linkDelegationPolicy = Qt::WebPage::DelegateAllLinks
     @page.page.settings.setAttribute(
       Qt::WebSettings::LinksIncludedInFocusChain, true)
     # Connect signals the webbrowser provides with own functions.
     connect(@page, SIGNAL('loadFinished(bool)'),
             self, SLOT('loadFinished(bool)'))
     connect(@page.page, SIGNAL('linkClicked(QUrl)'),
             self, SLOT('load(QUrl)'))
     # Start browsing some webpage
     @page.url = Qt::Url.new("http://dot.kde.org/")
   end
   # This method will be called once the user clicks on a link.
   # We just load the defined URL-address and let the
   # webbrowser-page display the content.
   def load(url)
     puts "Loading #{url.toString}"
     @page.url = url
   end
   # This method will be called once loading a page finished.
   def loadFinished(success)
     puts "page loaded #{@page.page.currentFrame.url.toString}"
   end
   # This method will be called each time a constraint changed. the
   # for us most interesting constraints are;
   # * LocationConstraint if the location of the applet changed
   # * ScreenConstraint if the screen on which the applet is located
   #   on changed
   # * SizeConstraint if the size of the applet changed
   # * ImmutableConstraint if the applet got locked/unlocked
   def constraintsEvent(constraints)
     if constraints.to_i & Plasma::SizeConstraint.to_i
       # if the size of the Applet changed, then resize also the
       # webbrowser.
       @page.resize(size())
     end
   end
 end

end

That was already all the code needed to implement our own webbrowser Applet using the Ruby language. The in this sample used webbrowser does provide additional functionality to use optional a full powered webbrowser or adopt it to your needings.

Install and test the Applet

To install the Applet the CMakeLists.txt is used. It basically does copy the both files above to the right locations. Translated to command-line arguments it would look like;

sudo cp plasma-ruby-applet-web.desktop `kde4-config --install services` sudo mkdir `kde4-config --install data`/plasma_ruby_web_applet/ sudo cp web_applet.rb `kde4-config --install data`/plasma_ruby_web_applet/

what installs the both files to the global installation directory to make hem available for all users on your sysem. If you like to have them accessible only from within one user, then just copy those both files to the users $KDEHOME (the command "kde4-config --localprefix" should provide you a hint where that may be).

To take a look at your applet or test it during development, you can;

kbuildsycoca4 plasmoidviewer plasma-ruby-web-applet

where the kbuildsycoca4 does rebuild the desktop-cache to update changes done to the desktop file. The plasmoidviewer is a tool that allows you to start and view your applet outside of plasma.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal