I have found no full way to express work routines with plasmoid. By work routines I mean something like: browse photos in a camera, trasnfer one to an album, them make eyes brown again, change resoution and print that photo.
To some extend i can approach this through "magic folder" and scripting, but it is not fully satisfying.

So, Is there any way to express "work routines" in/with plasma activities/plasmoids?
best regards

No.

IMO, that is the job of the application(s), not for the workspace.

If the workspace was to support defining variable processes, it would need to be a turing-complete programming language done as a UI (so that you don't need to use shell scripts). Which is a bit too much

ivan wrote:If the workspace was to support defining variable processes, it would need to be a turing-complete programming language done as a UI

As I understand it, there was only need for seguencing and defining "named blocks" (for saving screen surface).

> "named blocks" (for saving screen surface).

Didn't quite get this one.

ivan wrote:> "named blocks" (for saving screen surface).

Didn't quite get this one.

Something like grouping putting plasmoids into a pile, so a routinary action occupy less surface (yes, I know, some activities layout do something like this).

mvillarino wrote:Something like grouping putting plasmoids into a pile, so a routinary action occupy less surface (yes, I know, some activities layout do something like this).

quicklaunch and shelf plasmoids accomplish this ("putting plasmoids into a pile")

Now I'm totally confused

I see here two ideas:
1 - defining workflows which applications obey
2 - grouping plasmoids into stacks

1 is what I said that I think it is the job for the application(s)
2 is another story. There are containers like that, but I don't think they are mature enough for day-to-day use - full of bugs - and not pretty to the eyes IMO. As for the quicklaunch and the shelf, they group only launchers (apps, files, and similar), not plasmoids.