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.
Summary: | Keep "closed" projects visible in the IDE while using "folder-of-projects" group | ||
---|---|---|---|
Product: | projects | Reporter: | kawazu428 <kawazu428> |
Component: | Generic Projects UI | Assignee: | Milos Kleint <mkleint> |
Status: | CLOSED WONTFIX | ||
Severity: | blocker | CC: | djungowski, pjiricka |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 175264 |
Description
kawazu428
2009-04-29 07:28:25 UTC
It appears quite often that when we work on a project in a project group, we need to get some code from another project in an other project group. This can't be done in NB without switching project group which is clearly a problem of productivity and is not handy. In fact, the "working set" feature in eclipse is what I'd like in NB. A "working set" is a virtual directory that store some projects, but we can see several working sets at once. semantics of closing/opening projects is different from eclipse. Even a closed project is often known to the IDE and used when reached via some APIs. The possible performance/memory improvement could turn out to be marginal especially if the project is depended upon by an open project. for copying something out of a closed projects, Favourites view can be used or the project in question can be opened. No switching of groups is necessary (that's a costly operation quite often) recently closed projects can be quickly reopened through Recent projects main menu item. closing as wontfix, there's no plan in implementing different open/closed semantics nor a concept of workingset *** Bug 164154 has been marked as a duplicate of this bug. *** Accepted, thanks for clarifying. :) |