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.
Created attachment 133013 [details] Shows the expected state Please allow to type/paste a fully qualified name as class name in the "New Java Class"-wizard page. Currently you have to type the classname first then some gui widgets below you can choose/type the package name.
Created attachment 133064 [details] Proposed patch - draft @Netbeans-Devs: I like to propose the following patch to solve this RFE. The patch allows the user to input a FQN as classname in the new class/enum/interface wizard page, which speeds up creating such types. The package name of the FQN will be placed also in the package name widget and the package name widget will be disabled, when a FQN is given. When the user reverts its FQN the packagename widget is also reset and the widget gets enabled. The setting of the package name is a little bit difficult, because there is already an listener attached to the widget/to its document. So i had to "hack" this to work using isUpdating flag. Please review and help me to improve the quality of this patch.
Created attachment 133104 [details] Proposed patch - simplified
(In reply to comment #1) > The setting of the package name is a little bit difficult, because there is > already an listener attached to the widget/to its document. So i had to "hack" > this to work using isUpdating flag. > The new patch removes this hacky workaround. Please review. Thank you.
@Tomas: Feel free to add a tooltip or a small label at the bottom of the textfield to make the feature more obvious.
Fixed jet-main 769ef8d4f64a
Integrated into 'main-golden', will be available in build *201304272301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/2395c40ca6b6 User: Tomas Zezula <tzezula@netbeans.org> Log: #227877: New Java Class allow FQN of class
*** Bug 124059 has been marked as a duplicate of this bug. ***