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 161191 - project specific bean-category in palette
Summary: project specific bean-category in palette
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Zezula
Depends on:
Reported: 2009-03-25 20:22 UTC by pbucken
Modified: 2009-09-25 16:52 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description pbucken 2009-03-25 20:22:53 UTC
Hi folks,

Since i am using netbeans for several projects ( some new developement and several projects in maintance ) for years now
i would suggest this enhancement to the handling of project-specific beans:

there should be a folder in every project tree that contains all the beans that belong to the gui of that particular
project. This folder should reside inside the filesystem in the same directory where the sources are stored, so all the
beans of that project would be archived together with source- and config-files by tar-ing the top-folder of the project. 

When such a project is opened the project-specific category of beans should automatically be added to the palette-

When more than one project is opened then there it would be possible to transfer beans from project "A" to project "B"
by copy and paste, if a bean from "A" should be used in "B" as well.

As of now this data is stored somewhere in the directory ~/.netbeans/x.y and has the following disadvantages:

- all beans belong to a specific version of netbeans. When you have migrate one of your projects to a different PC (
perhaps running a different version of netbeans ) you have to locate and migrate this too.

- all categories of all your projects show up in the palette manager when netbeans is started, also the panels (=beans)
of project "A" have nothing to do with the panel-beans in project "B". This wastes storage and slows down the startup
Comment 1 Vojtech Sigler 2009-09-24 12:13:57 UTC
Reassigning to java for evaluation.
Comment 2 Tomas Zezula 2009-09-24 14:16:05 UTC
Rather form editor related, adding Tomas to cc.
Comment 3 Tomas Pavek 2009-09-25 16:52:38 UTC
We already have issue 119011 which mentions this too, and seen this idea mentioned several times. Yes, it would be 

Some time ago we made the palette sensitive to the project of currently selected GUI form, so this could be doable 
(with some help from javase project).