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.
Each opened form needs to know in which project it has been opened. This information must be passed to it somehow when opening. The project context is needed for accessing classpath (for beans loaded with form) and for invoking compilation on the form.
Can you update keyword for planning, please?
Re-evaluating... We need to do an initial integration of form module with projects so the form editor is capable to work somehow and more work can be started (incl. investigation and testing some approaches). In the first phase, we could still use non-API classes from java module (JavaDataLoader, JavaDataObject, JavaEditor), being dependent on java module implementation version. From the functional point of view, it must be possible just to open form, edit it (using standard Swing components), save, compile and execute. No user beans and installing to pallete need to work (classloader for user beans and managing pallete are separate issues). If times permits, we should try to find a way how to use just official java module APIs, get rid of unwanted dependencies (JavaDataObject, JavaEditor, etc). It is still not clear at this moment if/how it is doable.
I develop a module responsible for internationalizing forms. The module requires following form module features: - FormPropertyEditorManager - FormAwareEditor - FormDataObject (or public MIME type, and way how to load form model into memory) - FormProperty - RADConnectionDesignValue - RADComponent - FormDesignValue - not yet known dependencies
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped.