[14:26] <djsiegel1> seb128: ok, cool
[14:26] <djsiegel1> seb128: actually I need to do other work lol
[14:26] <seb128> djsiegel1, cycling through active dialogs would work too yes
[14:27] <seb128> djsiegel1, no hurry for that discussion
[14:27] <seb128> I just don't want that to slip through for cycles though
[14:27] <djsiegel1> seb128: no there is a hurry because it came up in user testing
[14:27] <seb128> because you guys are going to be adding lot of noise soon
[14:27] <seb128> you want to remove lot of icons
[14:27] <djsiegel1> right
[14:27] <seb128> like copies, cd recording, etc
[14:28] <djsiegel1> and you want a way to say "I am done interacting with this service"
[14:28] <djsiegel1> "background it"
[14:28] <seb128> it means on a desktop with 2 active dialogs + 1 cd recording + empathy + rhythmbox you would have a 5 tasks cycle for 2 active tasks
[14:28] <seb128> yes
[14:28] <djsiegel1> seb128: why not use workspaces?
[14:28] <djsiegel1> I put the "unimportant windows" in a separate space
[14:29] <seb128> I've 8 of those ;-)
[14:29] <djsiegel1> seb128: so, why doesn't that work for you
[14:29] <djsiegel1> just too hard to manage?
[14:29] <seb128> well let's say I like to have those infos handy and be able to get them on screen without switching context
[14:29] <seb128> changing workspace is an switching context for me
[14:30] <seb128> I tend to organize my workspaces by activities
[14:30] <seb128> but anyway I think most non geek users don't use workspace
[14:30] <seb128> so we ought to do something about the tasks handle on one workspace case for those
[14:30] <seb128> handle -> handling
[16:57] <proppy> Hi, didn't know there was an #ayatana channel :)