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.
I've started using the Localization class included with 5.5, and found a possible enhancement that would make life much easier for users of VMD: Allow resource names to be entered in titles/texts for form items, commands etc. That way VMD would get hints to auto-generate calls to getMessage and there would be nothing to hand code for this except of course the language files. E.g. a syntax like <licenseincorrect> would generate e.g. alertIncorrectLicenseKey.setString(LocalizationSupport.getMessage ("licenseincorrect")); I noticed that language files must use locales like "en", "sv" and not the full locale like "en_US" as some phones only report the short form. At least it's needed the way the localization class is written today. Could be easily changed though.
Designer 1 has been removed. Therefore reassigning to Designer 2 module. Probably this issue will be resolved in the future.
Very likely it will not be implemented in NB 6.0.
Too bad. It makes the combination of VMD and localization not work very well. Of course all the strings could be exchanged in run-time, but this would have made it simpler and more consistent. Thanks anyway for the overall very good work on NetBeans.
Sorry that missing feature. We just do not have a time for it.
there is workaround - use the user code option and add there your code LocalizationSupport.getMessage ("licenseincorrect")). I created blog entry for that - http://blogs.sun.com/lukas/entry/tip_user_code_in_component HTH
Good tip. Thanks.