understandable linux tips, tricks and tutorials
6 Comments
  1. Patience grasshopper. Now they have the infrastructure in pretty good shape, the sky is the limit for what is coming. The KDE team can only do so much at a time, but one thing is for sure is that, new features and capabilities will be pouring in due time.

    Concerning how Activities could be useful, imagine a company employee working on multiple projects. Each project has its own documents, applications, schedules, etc. and also share documents with other projects. Ultimately, the way I imagine it, s/he could create an activity for each project to management and quick access any data of any of them.

    A desktop Activity could be sort of a dashboard to access that information. Now wouldn’t that be an organizer and time saver?

  2. What I cannot understand is why wallpapers are tied so tightly to the desktop activities. I would love to have the ability to have a different wallpaper on each desktop, while having the same widgets displayed on each of those desktops. As it is now, I have to run a copy of the widgets I want to use on each desktop multiple times, equal to the number of desktops I am using. To me, this is an extreme waste of resources, to have to run the same widget multiple times, where it should be an easy task to separate the wallpaper from the desktop activity, allowing me to have different wallpapers while maintaining the same widgets across all desktops.

    • You bring up a pretty good question. I am not a developer and haven’t dug deep into desktop Activities yet. But I suggest you pose this question directly to Aaron Seigo, I am sure he would be happy to answer it for you by outlining the mechanics how Activities work. Also I noticed that he does read posts related to KDE and might answer it before you know it.

      Having said that, I believe what you describe as duplication of icons to associate with each desktop might not be their at all. The association of a widget to each desktop might just be links to the same widget object which makes it unnecessary to duplicate the object.

  3. Not a huge fan of Nepomuk or Akonadi, which I find to be the two weakest links in KDE these days.

    I would rather see KDE 4.6 focus on fixing bugs and optimizing the desktop speed. KDE needs that more than anything right now.

    It’s a fantastic desktop, which unfortunately has a lot of obvious bugs that have gone unfixed across several versions.

    • Nepomuk or Akonadi are still in heavy development. That is why in recent releases were made optional for those who are interested can test them and report problems.

      In regards to bugs and features, the KDE team has been doing a good job in balancing between bug fixing and new feature release. But you are right, there are bugs that haven’t be fixed for a long time. But if you look at the reasons, I don’t believe it was intentional or bad judgment. I believe it was the nature of those bugs and what they depend on that needs to be fixed first, and the time need it to get them fixed. Release 4.5 & 4.5.1 were mainly focused on bug fixing, but there is only so much time and resources to get to all bugs reported.


  4. Yaro Kasear:

    Not a huge fan of Nepomuk or Akonadi, which I find to be the two weakest links in KDE these days.
    I would rather see KDE 4.6 focus on fixing bugs and optimizing the desktop speed. KDE needs that more than anything right now.
    It’s a fantastic desktop, which unfortunately has a lot of obvious bugs that have gone unfixed across several versions.

    I haven’t tested Nepomux for quite a while because of it slowing down my system in the past but I would really like to test Akonadi. However I do agree with you concerning the next version of KDE 4. The should focus on gripes instead of new features. At 4.5 I had expected a lot more stability (see Dolphin and I don’t care what is the cause) and speed. KDE 4.5 still starts up a lot slower than it’s predecessor 3.5.
    It’s a wonderful desktop but it’s full time now to make it (almost) bugfree.

Leave a Reply

Site last updated October 20, 2012 @ 12:53 pm; This content last updated September 3, 2010 @ 5:28 pm