I’ve gotten a couple of complaints on the amount of daemons that is launched by default by any app built upon the KDE Frameworks, so I investigated one of them a bit.
The knotify daemon currently seems to do two things:
- Keeping some dependencies out of KDE Framework libraries
- Recieve messages from dbus, parse them, encode differently and send them on to other places over dbus
In the past, the knotify daemon was also responsible of showing popup-messages.
So, I did a quick experiment here in Switzerland to try kill off that daemon and merged the code from the daemon into the KNotification part of kdeui.
As a proof of concept it works, and if I can cut out some of the newly introduced dependencies it can end up being really nice. There is much less need for a separate daemon these days where knotify doesn’t actually paint the popups itself, but rather passes them on to a galago-spec implementing part of the workspace (on linux) or to growl for various non-free platforms.
and it starts with f…
While looking at the future of the KDE
Platform Frameworks here in Randa, Switzerland, a lot of interesting things has been found in kdelibs and kdepimlibs
that no one knew what was there for.
On the good side, there is also lots of cool stuff, that of course most people knows about and uses
- A real nice job based api
- Nice library for figuring out when there is holidays and special dates in different countries
- IMAP library
- Compression library
- Hardware access library
And a lot of great larger solutions for solving different real life problems
And lots of other cool stuff
- I really like the KDE plugin framework
- KIO slaves are great
- Kontact master is great
- Aaron is wearing pink
- Plasma Active seems cool
- The chefs are making good food, even though sometimes lacking a bit of meat
And we have currently nice things in the ‘required runtime components for every app built using kdelibs’
- Finger KIO slave
- Floppy KIO slave
- Weird cornercase user tools, some of them broken
Long time no blogging.
Earlier, I wrote a blog post about transporting data to mobile phones. I have since then extracted the Data Matrix code I wrote there into a separate library, prison and added support for QR Code as well. So from KDE’s next feature release, versioned 4.7 arriving around first of august, you have DataMatrix and QRCode support in Klipper.
While on a barcode spree, I also added barcode support to the KDE Addressbooks for easy transfer of contacts. Also using libprison. Also available from 4.7 onwards.
Few minutes ago, libprison 1.0 was tagged and hopefully soon, the KDE Sysadmins will publish my tarball.
And about the weather. Some nice people wrote Debian Weather which in simple ways shows if it is unsafe to upgrade. Quite recently there have been thunderstorms and heavy rain in Debian Unstable. Perl rain.
I have recently added support for Debian Weather in the Plasma Dataengine for weather. Also available from 4.7 onwards.
Last but not least, after spending a couple of hours on trying to understand Q3PtrList and how it was used in KHelpCenter, it is now, as the last component in KDE-Runtime, free of Qt3Support.
All for now. Next up. Platform_11
Hvorfor er det så svært at finde en maler der har tid til at lave noget for mig i København NV?
“Kalenderen fuld ind til december”
3 interesting small things happened in the weekend.
Due to the hard work of mostly Florian Reinhard and George Kiagiadakis, Bluedevil is now available. Bluedevil is a new and improved bluetooth handling thing targetted the KDE Workspaces.
The Debconf people have uploaded the Qt Debconf frontend that I blogged about a while ago, so now it should be available.
Last, but not least, applications now has more accurate data for if they are online or not, by using the ntrack library. This was especially problematic for people having some interfaces defined in /etc/network/interfaces, and other interfaces managed by NetworkManager.
This feature will be committed to upstream KDE whenever Will gets around to do it.
As a added bonus, KDEBindings in Debian has seen a release critical bugfix (python plugins, e.g. plasma widgets, related), and the brokenness of Konsole (libkpty) on the kFreeBSD-arches have been tracked down to a libc issue and a patch has been made.
All of this is expected to be part of next stable Debian release, codename Squeeze.
I guess we all have the challenge of how to easily get a link or a phone number or some other strings of data from the computer to the mobile phone.
With the help of mobile barcodes and klipper, this is now possible in KDE Trunk to do easily. Place some data in clipboard, click on klipper and select Show barcode.
To read it, open the barcode app in your phone (mBarcode on n900 for example) and point it to your monitor.
I wrote another blog post a while back talking about Debconf kde frontend.
I spend some days at akademy looking at it, and then refined it a bit when I got home.
- perlqt is in unstable and soon in testing.
- debconf kde frontend works.
- object oriented perl is weird
hopefully, the debconf people will accept it soon.
I wrote a bit ago a blog post about what debian kde is missing of distribution specific things
Some of the more important things includes:
- A Qt based debian installer
- Tools to manage 3rd party modules and firmware and such
- Debconf frontend that fits in
- Report bug interface
I don’t think it is the most important thing. Wether or not the graphical installer is using gtk or qt is not that important. I would love to see it happen, but it is not something I feel like putting my time in. Others are most welcome.
It will give the advantage of giving the installer the possibility to use the framebuffer directly.
Modules and firmwares and such
Someone is saying that ubuntu has something called jockey that does this exact thing, with a KDE and a Gnome frontend. Unfortunately, it is python, so it is something I will really avoid. I’m hoping that me mentioning it here will make someone into python&debian pick it up and bring it to debian.
It is apparantly some nice magic around discover-data.
Debconf frontend that fits
A lot of work has been put into proper perl-qt bindings and they will hopefully be ready for kde4.5, which is unfortunately a series too late for Squeeze :/. But when that has happened, we just need some perl guy to adapt the old frontend to debconf.
There is already a tool called reportbug-ng that is a qt interface to reporting bugs.
All in all, it looks like we are quite far already. We just need to get the last bits put together. Someone: pickup jockey.
And note that the comment field isn’t a place to report bugs. They will be removed.
So. I was wondering, which nice distro specific tools do exist in debian/gnome or in $other/kde that debian/kde is missing?
We have kalternatives for managing alternatives, we have a update notifier frontend in progress and after google summer of code, hopefully a package management frontend, aptitude-qt. (Made by Piotr).
But what other distribution specific tools are we missing for Debian-KDE ?
A while ago, something happened to the bugs reported against KDE in debian. It is best illustrated like this:
I’ve chosen to name it Eckhart slope. Thanks.
For full graphs, see http://alioth.debian.org/~pusling-guest/pkg-kde-buggraphs/