It seems like I got into a hacking frenzy after yesterday’s Ruby plugins for Kate. Today I sat down and took another look at the KRubyPluginFactory to implement KIO slave support.<\/p>\n
So here it is, our very first Ruby Hello World KIO slave:<\/p>\n
# kate: space-indent on; indent-width 2;\r\n\r\nrequire 'korundum4'\r\nrequire 'kio'\r\n\r\nmodule Rubytest\r\n\r\n class Main < KIO::SlaveBase\r\n\r\n def initialize protocol, pool_sock, app_sock\r\n super protocol, pool_sock, app_sock\r\n end\r\n\r\n def get url\r\n mimeType 'text\/plain'\r\n\r\n data Qt::ByteArray.new('Hello World from our first Ruby KIO slave!')\r\n\r\n finished\r\n end\r\n\r\n end\r\n\r\nend<\/pre>\nWe’ll also need a rubytest.protocol file that describes our new protocol:<\/p>\n
[Protocol]\r\nexec=krubypluginfactory\r\ninput=none\r\noutput=filesystem\r\nprotocol=rubytest\r\nreading=true<\/pre>\nTo test it, you just have to type rubytest:\/ into konqi’s addressbar and you should see nice hello world greeting.<\/p>\n
Some more info on the structure of a Ruby kio slave: the Ruby script always has to be named ‘main.rb’ and the SlaveBase derived class always ‘Main’. The module name is the camelized form of the protocol (so a protocol ‘foo_bar’ would map to a module name ‘FooBar’). The script has to reside in <kde prefix>\/share\/apps\/kio_<protocol name>.
\nThe .protocol file itself should be installed to <kde prefix>\/share\/kde4\/services.<\/p>\n