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:||Adapt Component Palette to projects|
|Product:||guibuilder||Reporter:||Tomas Pavek <tpavek>|
|Issue Type:||TASK||Exception Reporter:|
|Bug Depends on:||27180, 27182|
Description Tomas Pavek 2002-09-10 16:52:21 UTC
This issue has two parts: - installing beans, - using beans. For installing beans, the new classpath API must be used in some cases (where FileObject.getPackageName was used). Also it's not clear whether or how global JARs for beans can be used further. For using beans, the main problem is in that .instance files (and InstanceDataObject) will be no longer usable. Some alternative needs to be developed. See issue 27123 for details.
Comment 1 Jan Jancura 2003-03-27 15:48:54 UTC
Can you update keyword for planning, please?
Comment 2 Tomas Pavek 2003-04-15 17:17:52 UTC
We plan to keep the palette global, so not having project-specific content. Beans installed from JAR should remember the JAR file and it should be added to project resources automatically when the bean is used (in a form of given project). Beans added to palette from project explorer directly should remember the project they belong to and a warning should be shown if tried to be used in another project. To implement this, we need: - a new way of storing palette items (custom file type instead of .instance, keeping the JAR and project reference somehow), - being able to scan and modify resources of a project (to be able to add a JAR file).
Comment 3 Tomas Pavek 2003-11-26 15:35:03 UTC
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped.