2007-03-11

Dolphin browses archives

Today I took some time and added new functionality to a great new KDE's file manager - Dolphin. In KDE4 Dolphin will be the main file manager and in KDE3 it is the main file manager only if you setup KDE like I did (change "inode/directory" in KControl->Components->FileAssignments to point to Dolphin as a preferred application).

Well, I have lots of files packed up in the archives and I'd like it to stay that way. Konqueror always could browse through those archives, but dolphin doesn't have that functionality. That is - it didn't have until today. Today I made a patch for both new KDE4 dolphin and backport for the "old" KDE 3.5.6. You can find the KDE4 dolphin's patch in KDE Bugzilla or in KDE Subversion since it has already been integrated into the new Dolphin.

Unfortunately, Dolphin's version 0.8.2 is the last version for KDE 3 and it is going to stay that way. So, if you want to use new functionality, you will have to take my patch from Gentoo's bugzilla. While there, you can also download the ebuild and merge it into your system (if you are using Gentoo). If you are not using Gentoo, then just apply the patch to the source and after the usual configure, make, make install, you will be able to use that patch.

Well, that's all for today. I'm off to watch the brand new South Park episode 01 form serial 11.

Here are some screenshots of Dolphin in action:



Dolphin svn on KDE 4 with new feature and wrong icons (transition to Oxygen)


Free Image Hosting at www.ImageShack.us

Dolphin 0.8.2 on kde 3.5.6 with new feature

2007-03-06

External dockwidgets

Today I found this interesting post. Barış Metin managed to make a external dockwidget using Qt4 and KDE4. He even used Qt4's QTimeLine to animate the hide event. I liked what he did a lot and made the show event animated as well.

Here's the new source.

Click to play video
Click to play video

2006-12-16

OOMTK Kernel

A while ago I started to make a new microkernel. It's name is OOMTK which stands for "Object-oriented multi-tasking kernel", an old name I used for some small userspace kernel back in 1994. It is being hosted in Taiwan (OpenSVN repository) and you can take a look at is't trac website at the following address: https://opensvn.csie.org/traccgi/oomtk/.

My idea is to make a very small and basic microkernel that will handle context switching, memory allocation and message passing. Everything else should be in separate servers. To make things worse, no application will be able to access the hardware directly. Instead, it will have to go through HAL (hardware abstraction layer) interface to get to hardware. The HAL will implement some basic methods, such as port i/o. The HAL will have to be ring0, but it will be a separate process from the kernel itself, so that it cannot generate an error that would block the kernel. There will also exist a process that will be responsible of reloading the servers if they crash (and if they registered to be reloadable).

Currently, it is very far from usable. Here's the current screenshot (just a bootable kernel with paging and descriptors set up):

2005-08-13

FBackup


I have just started to make a new backup utility. At the moment it only creates a sha manifest of files (including the exclusion rules) and states which files were changed since the last version of the sha manifest. That can and will be used to create incremental backups which are easily readable by anyone (files will be stored the same way they were on the disk). That could be very useful for backing up music or something like that. You don't want your music to be in some unreadable format on the CD/DVD :) And using this fbackup the only thing you would have except your music is a small xml file containing the SHAs of the music files and their disk locations.


The repository can be found here. You can clone the repository like this:


hg clone http://tesla.rcub.bg.ac.yu/~brcha/hg/FBackup.hg

2005-07-14

SOAP->DCOP Multithread

There is a new version of SOAP2DCOP bridge. It is multithread (based on Qt's QThread) and it is intended to be ran as a program service. At the beginning of the application the server thread is started and at the end it is killed. You should then export dcop calls to soap, but that should be fairly simple based on my example. If anybody needs DCOP over the net, feel free to take it from my repo. The module itself can be found here, but you should use mercurial to clone the repository:

hg clone http://tesla.rcub.bg.ac.yu/~brcha/hg/Opstina.hg

And last, but not least, you should first download your copy of mercurial version control system from here.