Seems the Trolls made it, qt-project.org is online 😉 Grats.
At the desktop summit, many contributors got a ExoPC from Intel, but the software on it was quite a disappointment. Meanwhile, there is an official release of Plasma Active that fills the gap. So I sat down and installed it on the ExoPC. It really works quite nice and smooth. Applications like Amarok and a browser make it usable to hear music and do some quick internet surfing. I documented the steps in order to get everything up and running.
Running Plasma Active One from the USB Stick (LIVE version)
To get a quick impression, you can download the file plasma-active-one.iso from open-slx.com. Then, plug in a USB stick to your computer and run the comand
sudo dd if=plasma-active-one.iso of=/dev/<DEVICE> bs=1M
where <DEVICE> corresponds to the USB stick (in my case, this is sdc). When finished, plug the USB stick into the upper USB port of your ExoPC and press the power on button. Make sure to tap “BBS” immediately and choose the USB stick as boot device. After this, choose the first entry to start the live version of Plasma Active.
Note: As of 2011-10-15, a installation with this live version is not possible (even though some documentation at some point or the splash screen suggest otherwise).
Installing Plasma Active on the Hard Disk
In order to get Plasma Active on your hard disk, you first have to install openSUSE 11.4. To this end,
- download the 4.7 GB DVD image of openSUSE 11.4 (32 bit), and copy it on the USB stick (in my case <DEVICE> = sdc):
sudo dd if=openSUSE-11.4-DVD-i586.iso of=/dev/<DEVICE> bs=1M
- plug the USB stick into the upper USB port of your ExoPC and press the power on button
- make sure to tap “BBS” immediately and choose the USB stick as boot device
- after this, choose “Installation” to start the install process (you need an external keyboard on the lower USB port)
- follow the installation routine, choose the KDE desktop, do the partition setup, create a new user account and finally start the installation
- copying files takes some time. After this, the system finally boots to proceed with the automatic configuration.
- Finally, the system arrives in KDE. (From now on, the USB stick is not needed anymore.)
The touch screen does not work out of the box. Hence, I restarted X from the console with /etc/init.d/xdm restart. After that, the external mouse and keyboard worked (ignore the fact that you might be greeted by 6 crashed akonadi windows).
Once you have the internet up and running, proceed with 1.5 Installation on Balsam Professional or openSUSE. This updates your kernel to properly support the touchpad and replaces the default Plasma Desktop with Plasma Active.
Kudos to the Plasma Active team and all involved contributors and supporters!
PS: Although a text editor is probably not of much use on a tablet PC, KWrite is available 🙂
Finally some sustainable announcements about the future of Qt and its open governance project:
I hope this will be well received and we will see yet another increase in contributions to our Qt/KDE ecosystem 😉
Thanks for all the effort to all people who made this possible!
Some days ago, Dominik implemented a line modification system in the KatePart.
For all who don’t know what that means at all (like me before the DS 2011), here some screenshots.
Now, lets write some lines:
First I thought: Why to hell do I need such a feature? But after using it some days now, I think it is really VERY useful.
Yesterday I worked in parallel on code that generates integer linear programs as CPLEX files and read the output files (which are > 100000 lines) to find regressions.
I had to manually tweak the ILP files a bit to reveal the reason of my issues and it was just cool to exactly know even after save, which lines in the ILP I touched.
Normally I would have written some comments like \changed… above my modified lines in the output files, but yeah, KatePart does track such stuff now automatically 😉
Even for the much less big source files, it was nice to see:
Oh, I just tweaked that few C++ lines and it did remove the issue, maybe I should look at the lines below/above of that lines, too, for more possible problems?
Therefor: Thanks to Dominik for this nifty feature, I hope others appreciate it, too!
If you want this feature now: Use the guide at kate-editor.org’s Get It!.