Webcomic №10
Alone Again (Naturally) ♬
Alone Again (Naturally) by Gilbert O’Sullivan on Youtube and on Spotify.
Alone Again (Naturally) ♬
Alone Again (Naturally) by Gilbert O’Sullivan on Youtube and on Spotify.
The instable position isn’t obvious for the outside observer. No progress possible.
People, who are careless on their way up, are likely going to build barriers, they cannot overcome.
I’m a supporter of mail encryption since I started using free software.
At least, I sign all my own mails, with the exception of mails to people,
who don’t know what an *.asc file is and might not open my mail for this reason.
By the way, my public gpg key fingerprint is:
F6A9 332D AA28 625E 59A8 F758 7BF6 0F4A 861B C3A3
I’m also involved in the CAcert project. If you want to get “assurced”, don’t hesitate to contact me, if you are in Berlin.
There is just one problem. If you want to sign all your mails, you have to type your hopefully long passphrase at least once[^1] for every single mail. If you get some encrypted mails from your friends, you have to type your passphrase for viewing mails, too. That’s not so nice. So were the gpg-agent invented, which task is to cache your passphrase for a given time, but it didn’t work for me - until today.
I followed the tutorial from the opensuse SDB with
no success. Please note, that you might need to change the
pinetry-qt
to pinetry-qt4
.
The solution, which works for me, was to copy the mentioned
line to ~/.zprofile
instead of .xinitrc
, as I am using the
awesome zsh.
Earlier this year I started writing a KDE application using the Ruby programming language. Coming from the web development, I am no expert at all in C++. So I decided to give KDE development a try using the Ruby bindings for KDE 4 called korundum4.
It wasn’t as easy as expected. Unfortunatly the korundum4 project didn’t got very popular by now, so I found a lot of bugs on the way. Now, three months later, all the bugfixes are included in the last stable KDE. The idea, of just copying the project folder and starting the app without the need of any further setup1, becomes finally true.
I started a kind of clone of the well known Qt-based Youtube player Minitube. When starting the development, I had in mind to support Vimeo and maybe some other online video platforms, too. The app should integrate itself better into the KDE workspace, and lately I had the idea of turning it into a mobile app, too. It was possible to get a much cleaner and shorter code, not only because of the nice KDE KIO classes, but also by using Ruby.
Ok, to be fair, I have to admit, this is only possible using a recent Linux OS2 with korundum4 and Ruby 1.9.x preinstalled.
To give Kubeplayer a try, you just have to checkout the repository, and start the application.
git clone git://git.kde.org/kubeplayer
ruby kubeplayer/kubeplayer
That’s it. You can also install kubeplayer using CMake. Installation works like you would it expect it from a CMake based C++ application.
If you get an error related to json
, you are probably using an Ruby
version prior to 1.9.x. In this case you have to install rubygems via you distribution
package manager. Then you can use Ruby’s own package manager to install the
missing dependency.
gem install json
Not everything is done by now. Youtube works in the most a lot
of cases. The GUI needs a lot of small improvements. I even thought about a
maemo/meego port, paid for an N900 on
eBay, but unfortunately got duped :(
. So the mobile development has to wait.
After all, the project is still quite young, the code is very short, nice and clear. If you ever felt like trying to develop for/with KDE, the barrier is now quite low.
git clone git://git.kde.org/kubeplayer
Take a look at the code base. There are not many files at all. Summed up, there are less then 1000 lines of code (including rare comments). For an already functional multimedia application, this is really few.
kubeplayer
├── CMakeLists.txt
├── kubeplayer
├── lib
│ ├── CMakeLists.txt
│ ├── kubeplayer.desktop
│ ├── kubeplayer.rb
│ ├── List.rb
│ ├── MainWindow.rb
│ ├── provider
│ │ └── youtube
│ │ └── Youtube.rb
│ └── Video.rb
├── main.rb
└── README.rdoc
How does the future of Kubeplayer look like? I have already a lof of ideas, what could be done. Maybe you have also many, but different ones. What about:
So what do you think, can Kubeplayer do for you? What can you do for Kubeplayer?
Kind regards,
Robert