KDE Plasma Activities – A change in workflow?

With virtual desktops you have many alternatives – you can use the Pager widget, desktop effects, keyboard shortcuts, switch desktop on screen edges etc. But what about activities? I counted the methods that I know and ended up with 7 different ways to switch activities (depending on how you count), all of which I’ll share in this post. Who knows, maybe you’ll find a new favorite?

Hi I'm wondering how Android is managing memory and I can't find precise answer anywhere. Let's assume I have an application with 5 activities on current activity stack (4 are stopped and 1 is resumed), there is no service connected. I press HOME button so that all of my activities are stopped. I start some other memory consuming application and overall device memory is starting to be low.

When I'm at work, I use KDE activities and map them to my projects. I always use the same applications on every project, so I'd like to keep my windows visible when I change the activity. For the moment, what I do is go through every window, right click on the title bar, and check the checkbox that makes the window appear on all activities.

Published at LXer:

Recently, I wrote a post about the KDE 4.5 SC release candidate. In that post, I was a little bit critical about the discoverability of desktop activities. I wasn’t too sure of what the purpose of these were, and there was nothing in the interface for creating these activities that gave the user any hint of what they were.

I'm building a new android app which uses data from a server through different activities.

currently I have 2 activities, the main one connects to the server and creates the singleton object (which is shared for all activities) using the data from the server.

obviously I have an instance of the data held in the singleton class, and get the object from a static method.

I know that this is not th

I'm having trouble passing along state data between different activities.

Hi all, I am relatively new to Fedora and I'm experiencing some extremely annoying window behaviour in my fresh install of F17 x64/ Gnome 3. I have also used Fedora Utils for some basic tweaks, but this behaviour was apparent even just after install.

First, the activities panel/ taskbar is NOT active at all times.

Plasma Active takes a new approach to touchscreen devices and tries to offer more than a set of applications for simple tasks. More than a desktop or even a notebook computer, a touchscreen device is likely to be carried around and used in different contexts, for different purposes.

There's a scenario in my app which it could go activity a->activity b->activity a->activity b...infinitely, and eventually it'll get OOM.

Is anybody aware of a way to make it like the "dont keep activities" behaviour,e.g. the activities will be killed to release memeory but still in history, so it can be recreated as user navigates back?