The KDevelop forum was the first to join. Here you can receive help for using the powerful KDevelop IDE, as well as help the developers, for example by sharing your screenshots.

The Kexi developers have been very active in the new Kexi forum, asking for user’s wishes and sorting out problems in the General Help subforum.

Soon Dolphin, the default KDE file manager, also got its own Dolphin forum. Before topics about Dolphin would be shattered around in the Other KDE Software and Workspace forums. We realized that the new Dolphin forum didn’t really fit in any of our existing categories, so the System & Utilities category was created.

Marble is the first application from the KDE Educational Project to join the forums, visit the Marble forum to take a look. Don’t forget hat you still can ask questions about the other KDE EDU applications in the Games & Education parent forum.

KDE Workspace Vision is a special kind of forum where users can discuss what they would like to see in their future workspace, see Dario’s post for more information. It differs from Brainstorm as you’re allowed to post and discuss complete visions, while only single concrete ideas are accepted in Brainstorm.

Finally, we have our newest addition, the Konsole forum. Like Dolphin, topics about Konsole used to be posted to different places in the forum. Now most of them have been moved to their new home.

Meanwhile, the KWin developers implemented a feature in KWin to get useful information for users to post when asking for support. It’s really great to see developers care about helping their users. Martin also proposed a GSoC idea about supporting users directly from the desktop (with a plasmoid), using forum.kde.org. Unfortunately it’s too late to apply, but who knows, maybe someone already did? If it’s not taken and you’re interested in given it a try, you should definitely contact Martin or one of the forum admins (forum-admin@kde.org).

To close up – if you’re a user of any of those applications, the forums provide an easy way to connect with the community and receive expert help from other users and developers. If you’re a developer and want your own forum for your application, you’re just a few click away!

In this post I’ll talk about why you, a developer or contributor, should consider to create a forum at the KDE Community Forums for your KDE application or project.

Some of the advantages of forum.kde.org

Most users seem to prefer forums over mailing lists. Let’s just leave it at that and not get into a debate why one or the other is better. Instead, the focus will be on the KDE Community Forums and why you should get a forum there instead of, say, starting your own:

• Everything KDE-related in one place, users don’t need to register at multiple forums.
• As if that wasn’t enough, forum.kde.org supports login using KDE identity. One KDE account to rule them all!
• The board, which runs on phpBB, has many useful features such as guided posting, marking topics as solved, tagging system, advanced search powered by Sphinx etc. Oh, and did I mention that it looks great?
• We have a very dedicated team consisting of friendly and knowledgeable persons who maintain the forums, help users, moderate posts, make sure the board version is up-to-date and much more.
• Spam is a real problem for many forums. We have a sophisticated system to deal with spambots, even those who try to disguise themselves as normal users, and an active team that cleans the forum from spam regularly.
• It’s easy to reach the forum team in case you have any problems or questions (or if you just want to talk to us ).

To summarize, joining forum.kde.org means less job for you and more benefits for your users.

Convinced already? Take a look at our community page for information about how to request a new forum. I’ll repeat this information below, but first, I want to share some success stories.

Successful forums

KDE Community Forums already has several forums where developers are actively participating in the discussions and helping users. Some examples that come to mind include Eigen, KMyMoney, KWin, Skrooge and Tellico. There are two forums I want to mention in particular.

Krita

The Krita forum is a perfect example of an active community. I believe the Krita developers are a big part of the success – they regularly visit the forum, ask for user feedback, let artists contribute in the form of e.g splash screens and are just responsive and friendly in general.

There was one feature the Krita guys wanted that the forum didn’t provide out-of-box, a gallery for users to share their artwork. Sure enough, a phpBB mod was soon written by our awesome staff to display thumbnails for topics.

Krita gallery

I highly recommend that you take a look, there are a lot of impressive work in the gallery, all created with Krita.

If you have any special requests for your forum, don’t hesitate to discuss it with the forum team. We can’t promise anything but it’s possible that something can be done.

Amarok

Amarok had an active forum a long time before the official KDE Community Forums was launched. However, the Amarok developers saw the benefits of having everything unified under one roof and decided to migrate their forum to forum.kde.org. This was no easy task, all users had to be moved to the new forum (with possible name collisions) along with the posts. The difference in forum software didn’t exactly help.

But still, it could be done. Our competent staff wrote a conversion script that moved user information, posts etc. from one database to the other and the result can be seen at the current Amarok forum.

So if you already have a forum and want to migrate to forum.kde.org, ask one of the forum administrators.

How to request a new forum

You can find all information on our new community.kde.org page, I’m just repeating it here for your convenience.

If you want a forum for your application or project, there are only three conditions it has to meet:

1. The application or project should be related to KDE
2. There should be enough interest to fill the forum
3. At least one person involved with the application or project must be willing to moderate the forum

Note that your application doesn’t have to be part of the KDE Software Compilation.

The next step is to file a request at http://bugs.kde.org for the “forum.kde.org” product, here’s a link for the lazy. It should contain the following information:

• Name of the new forum and a short description
• User names of the people who are willing to moderate
• (Optional) If you have any special requests

When in doubt, just ask and we’ll work it out together.

I hope to see more developers join the KDE Community Forums and maybe even a few new forums in the near future. If you have any questions, feel free to ask in the comments section below.

Explanation

Keyboard accelerators are letters with an underscore that you see on buttons, labels etc. This feature is very useful for people who prefer to use the keyboard. For example, instead of using your mouse, you can click on OK by pressing Alt+O.

The downside is that it makes applications appear more cluttered. But not anymore. Starting from 4.8 (or did I just not notice this awesome feature until now?), you can configure Oxygen, the default style for KDE applications, to hide keyboard accelerators until you hold down the Alt key, or make them disappear completely.

So how do I do that?

• Open the System Settings module to configure Style
  (System Settings → (Common Appearance and Behavior →) Application Appearance → Style)
• Make sure you’ve selected the widget style “Oxygen“
• Click on Configure…
• Click on Show Advanced Configuration Options
• In the first tab (General), select an option for Keyboard accelerators visibility
  • Show Keyboard Accelerators When Needed (only shown when holding down Alt)
  • Always Hide Keyboard Accelerators
• Click on OK (or press Alt+O if you want to be fancy)

Enjoy your underline-free applications!

The post was accidentally moved, click here to read it »

Sorry about the trouble. ☹

Hello everyone!

Netrunner (http://www.netrunner-os.com) aims to become one of the leading KDE-centric Linux distributions, and to achieve this we need your help! Thanks to the financial support of Blue Systems we have the opportunity to hire one developer experienced in KDE/Qt/C++ programming to improve some areas of KDE software. You’ll be able to work full-time on various KDE-projects, such as

• Improving Kmenu, the panel and other parts of Plasma Desktop
• Fixing various bugs
• Improving/adding functionality

The improvements will be pushed upstream to make them available for all KDE users.

We guarantee monthly payment depending on your skills and experience with regards to KDE.

If you are interested in taking the offer, please send me an email with your CV to:

starbuck[AT]netrunner-os.com

Thanks and “Happy Holiday Season”!

This is a story about how I got what I wanted through toil, sweat and tears (thankfully no blood was spilled; the sweat and tears part might also be slightly exaggerated). All thanks to the nature of Free and Open Source Software.

Like many other times, it all started with a harmless thought: “So many things to do, I think I need a ToDo list”. Before I would keep track of things to do in a Notes widget on my desktop (screenshot), but this felt a bit primitive. It was time to get something better, although still simple, as I only needed the most basic features:

• A clear list of tasks that need to be done and when they must be accomplished
• Easy way of adding new tasks and marking tasks as completed
• Possibility to create tasks that are repeated (e.g. a task that needs to be done once every day)
• Basic priority settings

with the last point being a “nice to have” rather than “must”. With this in mind, I set out on my journey to find a suitable ToDo widget for my desktop.

… And returned empty-handed. Despite the many widgets that are shipped by default, the even larger amount of widgets on KDE-apps (not to mention the vast amount of Dashboard/Web/SuperKaramba/Google Gadget widgets), I couldn’t find one that fulfilled my requirements – a ToDo list that looks good on the desktop and supports the features listed above. Was that too much to ask for?

One of the top candidates was Remember The Milk, a plasmoid written by Andrew Stromme, which is included in kdeplasma-addons and thus often installed by default. I created an account on the Remember The Milk site and played around with the widget for a bit. It supported all the features I asked for and much more – great! The way of adding new tasks was also very nice. For example, I can write “Clean room tomorrow”, and it understands  that I want the task “Clean room” scheduled for tomorrow (actually, it’s much smarter than that).  However, I’m a person who likes minimalism, the KISS principle and clean desktops, and unfortunately Remember The Milk made my desktop feel too cluttered for my tastes (a problem shared by many widgets, by the way).

Remember The Milk plasmoid on my desktop

That could’ve been the end of story, but there’s a reason for the alternative title of this post. For more than a decade I’ve been enjoying Free and Open Source Software (FOSS) as a user. I liked the freedom that the KDE workspaces and applications offered, the freedom to use them and make them work as I wanted, but over time I’ve come to more and more appreciate the philosophy behind FOSS and the great communities around many FOSS projects such as KDE.

I’ve been in a developer’s shoes a few times, but all I’ve done is small changes. Today I put on those shoes again and got to experience what freedom means from a programmer’s perspective.

The Remember The Milk plasmoid is licensed under a FOSS license which, as you probably already know, means that anyone can view and edit the source code. Using the nice web interface at projects.kde.org, I could easily locate the relevant repository and find the Git command to clone it. The first thing I wanted to do was to declutter the widget by removing things I didn’t need. The label that displays the text at the top was the first to go, closely followed by the tab bar and filter bar. Since I didn’t want to spend too much time on this, it was done in a very quick and dirty way – I haven’t removed the code for filtering the tasks even though the filter bar is gone, for example. This method didn’t require much understanding of the code, and anyone with a little C++ knowledge could have easily done it. But yes, it’s not a very elegant solution.

Before compiling the source to see my modifications I had to edit CMakeLists.txt. The file contains instructions to CMake on how to make the project, and I didn’t want to overwrite my current Remember The Milk plasmoid. If you ever find yourself in the same situation, I highly recommend you to take a look at how other widgets (e.g. from KDE-apps.org) do it, as well as checking the Techbase page. It’s not that hard to figure it out after seeing some examples.

The next thing to do was to improve the appearance. This seemed harder, as I’m not used to working with QPainter et al. But the code was written in such as a way that it was easy to find the things I wanted to change, and with some help from API references (especially for Qt and Plasma), I got a result that I was happy with.

Remember The Milk after modifications

There was still one thing that I wasn’t satisfied with, however. To mark a task as complete, you had to enter edit mode by clicking on the task, check the Complete checkbox, and finally click on Update Task. I wanted an easier and faster way. Driven by my recent success, I felt that it was worth to give it a try.

My first idea was to add a button next to each task, but this seemed to require quite much work. Instead I went for an easier solution – middle click on tasks to mark them as complete. It was surprisingly easy to implement since I could copy the code for updating tasks. The hard part was to figure out how to detect which mouse button was clicked, which was easily solved with a Google search. The only problem is that with my current implementation, I had to change the action from “clicked” to “pressed”, meaning that I broke drag and drop in the process. But to me, the new feature is more important.

What really hit me during all this was how much control I had over my workspace – it truly is my workspace. If I can’t configure something to work as I want, I’m always free to modify the source code. Of course, I’ve known that this was possible ever since I was introduced to FOSS, but it’s different to experience it first-hand. Even I can do it.

And so can you! If you’re interested in contributing code to KDE, I have three suggestions:

• If you feel unsure, pick something that doesn’t seem too hard to achieve, for example doing small fixes like what I’ve done with Remember The Milk (although in my case, it’s not supposed to be an improvement; it’s rather an adaption to what I personally want)
• There’s much information on the net, but if you can’t find an answer, don’t be afraid to ask. You can do this via IRC channels, mailing lists, forums etc.
• Most importantly, work on something that you want. Is there a small bug that you find slightly annoying? Try to fix it! A simple application that you miss? You can create it!

I call this new plasmoid Remember The Milk Simple because I’ve stripped out some features, and the intention of the widget is to provide a simple ToDo list for the desktop. I guess you could call it a fork of the original Remember The Milk plasmoid. Before anyone asks, I want to clarify that I’m not intending to release the widget as it is now. The reason is simple – I consider this a hack, and a very ugly one at that. If there is interest I might work a bit more on it but I doubt I’ll find the time.

“But what about all this FOSS stuff you just babbled about”, you might wonder. Fair enough. If you really want this widget or are interested in contributing, e.g. by cleaning up the code, you can check out (or rather, clone) the Git repo for this project:

I understand that this widget is an unfinished project, take me to Gitorious »

To use it you’ll also need the Remember The Milk dataengine which is included in kdeplasma-addons.

That’s the end of my story, I hope it’ll inspire some to roll up their sleeves and start hacking. In the end I got (what I consider) a nice-looking ToDo list on my desktop, which will be an excellent complement to a widget I created called Procrastinate No More. Now I just need to actually start working on some tasks instead of hacking on widgets that remind me to do it.

• Whenever UserBase is mentioned the first time in a new context, call it “UserBase Wiki” or “KDE UserBase Wiki” if the context doesn’t make it clear that it’s KDE-related. The reason for this is that many people have mentioned that they didn’t know what a “userbase” was, and that they weren’t aware that UserBase actually is a wiki anyone can edit.
• Give UserBase its own unique logo.

I had made a rough logo based on the idea “Connect the pieces” and intended to simply replace the KDE icon in the sidebar, but Claus and Anne saw another mockup I had made (for a completely different purpose) and thought it would look good with some text as well. Brilliant idea, strangely enough I hadn’t even thought about it – isn’t it wonderful to work with other people? During the sprint we set on “Share your Knowledge” and asked our logo creator Eugene to make a logo for us. Here’s the result:

Of course you should just head over to UserBase directly and see it in action. If you still see the old KDE logo you might have to refresh your cache, Shift + F5 in most browsers.

Finally, a reminder:

UserBase is a wiki for KDE users, made by KDE users. Registration is no longer necessary to contribute. Share your Knowledge »

Today was another warm and sunny day at Linuxhotel in Essen, where the first KDE WebWorld sprint was held, but the increasing cloudiness and predicted rain in the afternoon meant that it was time to pack and go home. A lot of things have happened during these days, so here’s a summary (because Ingo forced me to do one):

• Evil Toma is evil, but also a great teammate when it comes to Tischfußball.
• Eugene Trounev cooked very tasty meals despite the lack of polar bear meat in Essen.
• Ingo Malchow is a pretty good pilot, but needs to work on the landings a bit. My advice: stay away from house roofs and trees.
• Stuart Jarvis also likes animated GIFs; maybe it’s about time we put some on the kde.org site?
• Matthias Meßmer is (a) pipesmoker.
• Niklas Laxström has a time machine so that he can listen to our future complaints and fix them the day before in his comfortable couch.
• Anne Wilson doesn’t only work on the UserBase Wiki between meals, she probably also does it after going to bed and before waking up.
• Claus Christensen could have been my favorite teacher in high school if only he lived in the same area as I did (hooray for math and physics). Just imagine if you had a teacher who contributed to KDE, wouldn’t that be cool? Based on the data I have teachers seem to be pretty common at WebWorld sprints.

All in all I had a great time, it was very fun to meet everyone and talk about everything (although at some nights it got pretty late). There were still a few topics I wanted to discuss, but time is limited,  we had many other important discussions and overall I think that the sprint has been very productive for the KDE Web Team.

In this post I’ll write about what the KDE UserBase Wiki team has worked on during the first day – and it’s quite much in just one day! The wiki has always had much potential in my opinion, but unfortunately not too many contributors. We want to change that.

• Everyone is a potential contributor. To lower the entry barrier further, we now allow non-registered users to edit pages. This is great news for those who just want to make spontaneous contributions. However, registering has many benefits and is still recommended.
• Everyone can contribute. We have made small changes to the sidebar and the pages for contributors to make it clearer. Hopefully this will make it easier for new contributors to get started.
• Details are important as well. It is awesome to have all these different people gathered here in the same place (and what a wonderful place it is). This has allowed us to quickly fix a bunch of small and some larger issues with UserBase. Those are issues the user shouldn’t experience in the first place so I won’t go into any details, let’s just say that it has improved the user experience of the wiki. There has also been improvements in the translation tools, small tweaks in the style and other nice stuff.

In the evening there were discussions about how to strengthen the UserBase image, and we have some exciting plans. The details will be worked out over the next few days.

Before I end this post, here’s a challenge for you:

Make a contribution to UserBase » It could be an application feature that you think more people should know about, a small tip, an updated screenshot, a typo fix – you get the idea, every contribution counts!

And remember, you don’t even need to be registered anymore, just click on to edit a page. If you feel unsure, the Sandbox can be used to experiment. You can use the Discussion page on the start page (second button from the left) to ask for help or try to ask in the #kde-www channel on freenode.

How many managed to read this far and clear the challenge? If you did, why don’t you write a comment below?

• The possibility to set a keyboard shortcut for each activity, for example Meta+F1 for the first activity, Meta+F2 for the second one etc.

This is actually already possible in 4.6, although it isn’t very straightforward for those of us who aren’t D-Bus wizards. However, since I know that there are other people who want this, I’ll share what I figured out today. After reading this post you’ll be able to set keyboard shortcuts (such as Meta+F1, Meta+F2 etc.) to switch to specific activities.

1. Find the activity id

Each activity has a globally unique identifier (GUID) which is a 32-character hexadecimal string. To get the GUID of the current activity, run the following command:

qdbus org.kde.kactivitymanagerd /ActivityManager CurrentActivity

Make a note of it somewhere. You can also get a list of all activity GUIDs with

qdbus org.kde.kactivitymanagerd /ActivityManager ListActivities

The list is ordered in the same way as the activities in the activity manager.

2. Create keyboard shortcuts

Now you have everything you need to create a keyboard shortcut for an activity.

1. Go to System Settings → Common Appearance and Behavior → Shortcuts and Gestures → Custom Shortcuts.
2. Click on Edit → New → Global Shortcut → D-Bus Command.
3. Enter a name for the shortcut. In the Trigger tab, click on the button that says None and press the shortcut you want to use (e.g. Meta+F1).
4. Click on the Action tab and enter the following:
• Remote application: org.kde.kactivitymanagerd
• Remote object: /ActivityManager
• Function: SetCurrentActivity
• Arguments: The GUID from the first step, e.g. a589200e-1983-4825-8275-50de36c223e5
5. Click on Apply.

Rinse and repeat. If you want the corresponding D-Bus command, for example to use it with another application, it is

qdbus org.kde.kactivitymanagerd /ActivityManager SetCurrentActivity "GUID"

where GUID is the GUID of the activity.

That’s basically it, have fun!