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 35849 - Eliminate .FORM files
Summary: Eliminate .FORM files
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
: 53134 (view as bug list)
Depends on:
Reported: 2003-08-30 06:03 UTC by kanderson
Modified: 2008-04-28 17:12 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description kanderson 2003-08-30 06:03:58 UTC
I would like to advocate eliminating the need for a 
separate .FORM file for GUI forms.  Things would be that 
much simpler with everything in just the .java file.  There 
would be no way for the form defintion to become separated 
from the code and possibly lost altogether (it's rare, but 
I've seen it happen).   Also, the form definition and code 
could never get "out of sync" as a result of checking out 
incompatible files from version control in an attempt to 
revert to a prior version.  

How about just putting the XML form definition in a 
guarded /*...*/ comment at the end of the .java file?
Comment 1 bmf1972 2004-07-09 23:36:44 UTC
Do you think it will be easier to read and develop such a mixed file?
What's the next step? Mix all definition (or metadata) files with the
logic files?
Comment 2 Tomas Pavek 2005-05-13 15:40:53 UTC
*** Issue 53134 has been marked as a duplicate of this issue. ***
Comment 3 Tomas Pavek 2005-05-13 15:47:49 UTC
I've been hearing lots voices and opinions about two-way editing. While the
separation of UI and application logic is fine, it is not nicely doable or
enforceable if the primary way of expressing UI is code. And seeing the code,
people always want to edit it. Would be nice to have a decent standard resource
format with mapping to java code. In the current situation we consider the
two-way editing as worth doing as it provides significant adventages but still
have no concrete plans about it. It is indeed a very complex task...
Comment 4 Tomas Pavek 2005-05-16 16:10:46 UTC
See also issue 26938.