Milian Wolff mail at
Mon Feb 15 19:51:41 UTC 2010

Esben Mose Hansen, 15.02.2010:
> On Monday 15 February 2010 19:29:12 Niko Sams wrote:
> > So here my question to all:
> > Who uses workingsets?
> Not I. Nor have I seen any in "my" admittedly small development group use
> them. They are cool, but it's too hard to keep track of them and keep them
> up to date as the files to include naturally changes.

As I said during the sprint: I don't want them to be removed, instead we 
should make them usable. What they lack right now (in this order):

- working set switcher that does not require the mouse to be used. Since they 
don't have names that identify them (yet and if they have at one point, it 
will always be optional), I imagine this switcher more like one of the KWin 
tab switchers: Show the workingset popups next to each other and cycle through 
them to see the items opened in them. But it's important to be able to see the 
contents of more than one set.

- a fast way to create a new set or close the current one - again without 
having to use the mouse

- a fast way to open the set for a given file, for example I tend to use 
workingsets for the plugins in KDevelop: Each one of those is (most of the 
time) confined to it's plugin folder. When I use quickopen to switch to another 
plugin I'd like to have it open the workingset for that one (if I have one 
open for it). Of course it cannot be the default action, since someone might 
want to open a file into the currently opened workingset.

- introduce more of the polish from the workingset mockup

Milian Wolff
mail at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the KDevelop-devel mailing list