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 current api for palette items for text-based editors enforces the usage of resource bundles for item display name. therefore it isn't possible to create new palette items at runtime upon user's request (e.g. new code snippets)
+1. This would be excellent and is much needed.
+1
Plan to do in 6.0 M7.
Created attachment 37535 [details] proposed implementation
What about creating new palette categories at runtime that are fully i18n-able?
> What about creating new palette categories at runtime that are fully i18n-able? what's the use case for this feature and how is it supposed to work?
Created attachment 37568 [details] proposed implementation - better xml syntax
Example of the inline-description/tooltip tag should contain <![CDATA[...]]> section, otherwise it's content is not valid regarding the DTD 1.1
The case for adding palette items at runtime that are fully i18n-able would be like adding new components into VWP. Wether we have component authoring or a user wants import components, we need to be able to add them at runtime. Edwin, can you please confirm this?
This is in response to "saubrecht Mon Jan 22 14:47:55 +0000 2007" about the use case for creating i18n-ed palette categories dynamically. I think it makes sense to break this out into a separate issue so I have created http://www.netbeans.org/issues/show_bug.cgi?id=92987 to keep track of it.
Standa, please reevaluate.
the api has already been extended to allow dynamically created items, see issue 92962. now it's up to each palette provider to implement their own logic for item creation. closing as fixed.