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: | Permit to delete/modify GUARDED BLOCKS when no .FORM file is associated to the source. | ||
---|---|---|---|
Product: | java | Reporter: | vbrabant <vbrabant> |
Component: | Editor | Assignee: | Dusan Balek <dbalek> |
Status: | NEW --- | ||
Severity: | blocker | CC: | dpavlica, mroskanin, tpavek |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Other | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
vbrabant
2002-11-13 10:11:33 UTC
Form editor could provide a feature like: throw away the .form file, remove all guarded blocks from .java file. But if there's no .form file, then there is no clue that the .java file was originally generated by form editor - form editor is not invoked for that file, the file is handled as normal java code. In such case, java module should provide a way to cancel protection in guarded blocks (with appropriate warning). What's the current status ?? It's pending. Right now both java module and form editor modules are under heavy rewrite due to the new projects system integration. I am afraid that we aren't able to implement this feature in 4.0 release time frame. Sorry. Don't be afraid. I understand that you are busy with the new project. Thanks for the feedback Any news ? Will you have time to introduce it in NB3.6 ? Java module does not know who created the guarded block. If the form file does not exist, the file is not handled by FormDataObject, but rather by the standard JavaDataObject. JavaDataObject has no clue that some guarded-blocks in the file are form-specific and could theoretically be removed. There might as well be other modules that create these guarded blocks and these guarded blocks are perfectly valid (e.g. beans module creates such guarded blocks in bean info class). So, to resolve this issue we either need to build some kind of new guarded blocks API that would allow Java module to get more info about whether the guarded block is still valid or not, or we could provide a generic "remove all guarded blocks" action on a file. The second option would of course be much simpler. This will need to be communicated accross several teams. |