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.
The new java class wizard should allow specifying a base class and/or interface(s). import statements should be added accordingly. Here's what the class wizard should have: 1. Edit box for specifying the FQ base class name. 2. Next to it a [...] button for bringing up a list of classes from which you can pick a base class. You should be able to filter out classes using wildcards. 3. A List of interfaces to implement. where you can add interfaces to be implemented. The class wizard then creates the necessary method stubs, also, so that the class compiiles after creation.
Looks like a request for enhancement rather then a defect.
Why cannot you use the editor for these purposes? IMO code completion + Tools/Override Methods or Tools/Synchronize is what you need to achieve your usecase. We want to keep the wizard simple as much as possible and do not double the editor functionality. This was the main reason why we simplefied it in NB 3.6.
Yes, I believe I can. That's because I was looking under the Edit menu and did not find those functions. I believe these functions belong to the Edit menu. IMHO, any function that directly modifies the file open in the editor belongs to the edit menu. Functions that do not modify the file in the editor should be moved to a differnt menu. For example. The "Find" and "Go to xxx" menu items belong in the "View" or a "Search" menu. I believe i should open a new enhancement issue for this. To be frank, I have never warmed up to Netbeans until the 4.0 beta. I have been a JBuilder/Eclipse user all along. The mount filesystem paradigm turned me off. Besides project management wasn't great in 3.x releases.
TO: <<QUOTE>> Why cannot you use the editor for these purposes? IMO code completion + Tools/Override Methods or Tools/Synchronize is what you need to achieve your usecase. We want to keep the wizard simple as much as possible and do not double the editor functionality. This was the main reason why we simplefied it in NB 3.6. <<END>> This thought is stupied. For wizard simple, why not you delete the "assign package name & project" step? I think assign base class/interfaces is VERY important in a REAL project. Why not assign it at creating time instead of edit it after creation? User can press "FINISH" at any step(before traverse all the steps of the wizard), isn't simple enough?
Honza is responsible for it.
moizd: Tools/XXX actions were replaced with editor hints. So hopefully it is enough simple and intuitive nowadays. Closing this as WONTFIX. waynezhang: I am wondering how you would change the project inside the editor. In order to change the package you would have to use the refactoring. Moreover these two items can be determined from the node on which you invoke New File action. Contrary to the possible base class you would have to write in all cases. So why to maintain additional code for the wizard when users may do the same in the editor. Other users could consider important adding fields, methods, ...