Note that I only talked about WINDOW
working sets, not working sets in general. Those I also like and use.
Dawid Pakuła <zulus@xxxxxxxxx> To:
User Interface Architecture
Working Group <ui-best-practices-working-group@xxxxxxxxxxx> Date:
20.09.2016 16:40 Subject:
[ide-dev] Working sets (WAS: Re: Java IDEs comparison) Sent by:
Please no. This is one of main feature
that keeps me away from IDEA in general: 1. Nested projects are useless when you
want keep one project in more than one parent. It also force you to maintain
structure outside eclipse, and cannot be used to filter resource based
views. 2. Switching workspace is too slow for
fast switch (open/refresh/build), and not allow to show all without additional
Maybe rather than remove working set
feature, rethink how it they are maintained, for example lot’s of toolkit’s
create own working set types, PHP, JDT, Mylyn, so: 1. each working set wizard works different. 2. they are not shared between views.
Out of the box most views use the WWS by default, which allows to quickly
switch the working set for all views in a window. In previous releases
there were toolbar buttons that made it easy to tweak the WWS. Those are
now hidden by default, but can be made visible again via Window > Perspective
> Customize Perspective...
As I said before, I'm also not using WWSs and I doubt many people do. So,
might be time to retire them if no one objects here.
I have to admit, I'm also curious. My usage of working sets is exactly
like yours. I'd suggest we do some code archeology and try to figure out
what use-case window working sets (and working sets in general) were intended
to support. If the main use-case we care about is the adding-structure
to the package-explorer use-case that you and I seem to use them for then
we could probably brainstorm a much more efficient UI that addresses that
On Tue, Sep 13, 2016 at 12:52 PM Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
wrote: I’ll echo Bruno’s question. What is a “Window Working Set”? I really
have no idea how it’s different than regular Working Sets.
Frankly, I just use Working Sets to add some hierarchy to the projects
I have open in my workspace (I have over 400 at the moment) and really
only use it in the Project/Package Explorer and to scope Searches. They’re
not very easy to set up though if that’s all you wanted.
First entry in working set configuration window . In JDT schoold views
(JSDT, DLTK, ...) there is always shortcut on view menu (before standard
I personally use it together with mylyn: 1. Select Window Working Set in Resource and Type selection dialog + in
any exlporer 2. From Task List, create Mylyn Working set with some projects 3. Activate mylyn working in Task List.
As the result, all views with “Window Working Set” activated will be
On 9 September 2016 at 14:16, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote: >The user story that Working Sets
aims to address, isn't it better served with different workspaces and/or
I agree regarding Window Working Sets - I never use them. But in all my
workspaces I use working sets, to e.g. easily switch to or search in documentation,
which is a working set in my workspaces.
On 7 September 2016 at 18:08, Dawid Pakuła <zulus@xxxxxxxxx>
wrote: My 5 cent: consistency, consistency and again consistency...
3. Working sets, one of most powerfull thing in eclipse isn’t widely supported
across projects, examples: 3.1. “Window Working Set” entry sometimes isn’t available in fast view
menu (Platform views), sometimes is (JDT school based views) 3.2. Working sets types not always available between views, for example
still is not possible to import existing project into mylyn working set
The user story that Working Sets aims to address, isn't it better served
with different workspaces and/or nested projects?