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.
When I right-click on a package node. In the NEW item, it propose a standard list of templates like folder, package, java class, java main class, ... IMHO, the distinction between a java class and a java main class is not necessary. I propose the following: Just have a java class (you suppress the java main class) BUT on the first step of the wizard, where you have to give it a name, add a check box creation of main method. If user check it and click directly on finish, the class with a main method will be directly created. It will permit to propose by default a java interface in stead of a java main class. Vincent
Assigning to HIEs to decide.
What's the opinion of UI Team ?
this has merit but the bigger question is not just the distinction of what to do with these two templates but how to handle the class wizard. for the moment we are considering removing the class wizard until it can be fixed up -should that be the way things go we should keep the two templates around. once the wizard has be redesigned we can look at what templates actually make sense.
I am not sure to clearly understand what you mean. Do you mean that you want to suppress the current class wizard ? How will we be able to create new class then, without any wizard ? What is wrong with the current one ?
sorry, i wasn't clear. the part of the wizard i'm talking about is the extended portion of the class wizard that presents steps for setting up inheritance, fields, etc. from the step 'Basic class definition' on to the end.
Any news ??? No idea if it's accepted, rejected. Please give me any feedback.
for the time being the main class template is sticking around. the changes to the classwizard for now focus on getting rid of the complex and superfluous extra steps of setting up the class through a wizard.
Extra steps was already removed according to UI spec http://ui.netbeans.org/docs/hi/promoB/javaWizard.html
So, please reject, close or ... the issue. But don't let it as new.
leaving this as a new enhancement will help us keep track of it for later changes/ improvements to the new wizard.
Closing as won't fix. Adding a checkbox to the wizard is against the direction of changes that were made to the nature of the wizard so far.
*** Issue 48511 has been marked as a duplicate of this issue. ***
OK, I found a newer duplicate of this. I think UI engineers should evaluate it again. Reopening. Jano, could you please look at it (or whoever from the UI team is responsible for the new class wizard)?
Already fixed.
Reorganization of java component