You are using an obsolete web browser, or you have the page styles (CSS) disabled. You'll be able to access this site, but only a visually simplified version.

Tokamak 4: Lancelot Mobile

Lancelot (the menu) was not really designed to run on mobile devices (although it could be used on such devices as a full screen application quite well), but the Lancelot Part applet proved to be a rather good fit.

I wasn’t involved in any mobile-related developments at Tokamak 4 (I had too much to work on krunner and activities) but I found some time to test the KDE/Plasma enabled Jax 10 devices.

Placing a Lancelot Part inside the newspaper activity that showed favourite applications and a search box was a breeze and it worked quite well. Marco did a really good job of adapting the plasma-netbook edition to mobile (touch screen) devices so the Parts applet required no changes at all to fit in the new environment.

Here is an obligatory blurred screenshot:

I’m planning to make a screencast about using Lancelot in Plasma Netbook, but I’m not finding the time. I hope I’ll be able to make it soon.

Cheerio!

Tokamak 4: Plasma is too fancy

If anybody tells you that KDE SC 4 is too fancy and not configurable enough, just show them this:



A product of a temporary idle mind – ASCII theme for Plasma

edit: It’s is creating a wallpaper to fit this…

Tokamak 4: Activities

This one will be short, I don’t really have the will for writing – it is half past midnight here.

The activities infrastructure is mostly finished – now only polishing is left to be done.

The new organization goes like this:

The core activity-related features are placed into a kded module which doesn’t depend on anything but Qt and the core kde libraries. The class for writing the clients of this service (any program that wants to be able to react to activity changes etc.) will be in kdelibs. The API is minimal and very easy to use – it took me only a couple of minutes to patch KWrite to be able to use activities.

The second part is the revamped Nepomuk Activities service (I already blogged about it – the changes made at T4 were mainly related to make it fit the new arhitecture). If it is running, the above class passes all the info to it. Running the service enables the access to extra meta-data regarding documents and activities.

The third, and last part is the manager class which will be in kdebase/workspace (most probably) because it is only intended to be used by kwin and plasma. Normal programs shouldn’t use it.

The next step is the UI – kwin and plasma

Cheerio.