You say you want a revolution Well, you know We all want to change the world You tell me that it’s evolution Well, you know We all want to change the world ~ The Beatles (John Lennon)
I don’t know whether it is revolution, or evolution, but my favourite ideas that the Plasma team thought of a long time ago are finally getting to the users.
It is quite nice to see the positive experiences with the activities system in Plasma 4.9 all around the web. And that was just the tip of the iceberg. There are a few nice things coming to the following release.
The top feature for me is going to be the Share-Like-Connect applet, and the document scoring based on the usage. Lately, I’ve been on a patching spree to increase the number of applications that support activities and the number has increased substantially. Currently, these are the supported applications:
Dolphin
Gwenview
Kate and KWrite
Okular
Words, Stage and the rest of the Calligra family (except for Kexi which will be patched soon)
GVim
I plan to add a few applications to this list before the hard feature freeze slaps me in the face.
Thankfully, I’m not alone in this endeavour. (Edit: added the link for the following text) Tomaz Canabrava’s army of students are going through KDE’s extragear and doing the same thing I’m doing in integral parts of KDE SC. This really offloads a lot of work off my shoulders so big kudos to them!
I haven’t been much involved with this release apart from under the hood stuff that Active and desktop versions share, and the new website design. So, when testing the new image, I experienced the thrill the regular users do. It is a good feeling :)
From the “Soon to be in master” files, comes a screenshot depicting two new QML data components from the org.kde.activities.models package - ActivityModel and ResourceModel
Both are available as standard C++ and QML models. The ActivityModel does just what the name says - lists activities, while ResourceModel is more fun - it lists the resources opened by a specific application, or those tied to a specific activity, … and it can order by the score, recentness …
Published
in the Prog C++ section,
on 12 September 2012
Just something I wanted to share. Today, I caught myself using two different naming conventions in the same code.
One is the camel-case style like Qt uses, and the other is the underscore style that STL and boost use.
It turned out that I use camel-case for everything except for when writing generic stuff like algorithms (to follow things like std::for_each, std::find_if) or special helper template classes.
For example kamd::util::for_each_assoc, model_insert (class that does RAII equivalent of beginInsertRows/endInsertRows).
Strangely enough, it feels natural. More natural than having names like qLowerBound, qBinaryFind…