This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 56501 - Provide a workset view
Summary: Provide a workset view
Status: RESOLVED DUPLICATE of bug 50683
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Petr Hrebejk
Depends on:
Reported: 2005-03-16 02:40 UTC by paulhuang
Modified: 2005-05-10 17:13 UTC (History)
2 users (show)

See Also:
Exception Reporter:

PDF File to illustration the workset idea. (92.48 KB, application/pdf)
2005-05-10 03:09 UTC, paulhuang

Note You need to log in before you can comment on or make changes to this bug.
Description paulhuang 2005-03-16 02:40:37 UTC
I found there is a potential feature we may grab from Eclipse.

Generally speaking, when we deal with a Java project, it may consist of several
subprojects. For example, we may have a Java project A, consists of subprojects
A1, A2, A3, and another Java project B, consists of subprojects B1, B2 and B3.
If we create and opened all these subproject, the navigator may appear tangly
and confusing. I understand we can currently choose to close some projects for a
better view, I still would like to recommend creating a workset view. 

With the idea of workset, you can easily arrange the relevant subprojects into
one category, i.e. a named workset. Take the above case for example, we can
arrange projects A1, A2 and A3 into workset A, and B1, B2 and B3 into workset B.
By selecting the different workset, we can then easily switch to different
projects view while keeping all the projects open. 

Developers can create a workset, edit a workset and delete a workset to arrange
the way we view all the opened subprojects in a quite flexible way. 

Personally speaking, I really like this feature from Eclipse. So, if it's good,
why not take this feature and have it in netbean.
Comment 1 David Simonek 2005-05-09 16:37:09 UTC
I have to say I don't understand how navigator may appear confusing in relation
with number and/or hierarchy complexness of opened projects. When working on
netbeans, I have about 100 opened projects/subprojects and Navigator is still
the same, easy to use.

Speaking about projects, I could understand that their grouping in bigger sets
would improve working with big number of projects. But how navigator fits into
this and what use cases are we trying to solve? 
Comment 2 paulhuang 2005-05-10 03:08:07 UTC
Please see the attached pdf for a illustration of my workset idea. Thanks!
Comment 3 paulhuang 2005-05-10 03:09:05 UTC
Created attachment 22055 [details]
PDF File to illustration the workset idea.
Comment 4 Jan Chalupa 2005-05-10 06:32:25 UTC
paulhuang: Thanks for the nice feature description.

The proposed feature doesn't concern Navigator. It's more about Projects View
configuration. Re-assigning to projects/ui.

However, there are no plans to implement this feature in a foreseeable future.
Comment 5 Milos Kleint 2005-05-10 07:01:05 UTC
i believe the "open required projects" features that's part of opening a project
is more powerful. Maybe allowing to open some of the required projects only can
be added. That way you get the projects that you need, dynamically for any given
project. Once you don't need it, close it. For future reference, it is still in
the Open Recent Project list. 
About switching 2 worksets. What is the problem in having all projects open?
When I need all of them, I have them available, when I don't need some for the
moment, I just close them.

I personally don't see much added value in the workspace feature apart from
making current eclipse users happy.

Just my 2 cents.
Comment 6 Jesse Glick 2005-05-10 17:13:30 UTC

*** This issue has been marked as a duplicate of 50683 ***