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.
Implement a TemplateMap feature that encompasses a complete set of code templates. The TemplateMap should be designed to be imported/exported between various user's IDEs. For example, if I take the time to create 20 code templates, I should be able to export all of those templates associated with one TemplateMap for my co-worker to import for quick and easy usage. This is a little different than what appears to be the placeholder for exporting/importing code templates now, as the request is to be able to create and manage individual full TemplateMaps and not be bound by any limitations.
What specific limitations do you mean (of course there are always some limitations)? How should it differ from current Tools -> Options -> Export -> Templates?
Wrong component.
TemplateMaps should represent a user selectable set of language code templates. TemplateMap myFirstTemplateMap includes: Java code template Ruby code template TemplateMap mySecondTemplateMap includes: Java code template Groovy code template TemplateMap myThirdTemplateMap includes: All templates I guess the TemplateMap isn't necessary if the user can individually select what 'language' code templates can be exported in groups. However, being able to mangage TemplateMaps would bring added value to organizing and managing code templates. So, in essence, TemplateMaps would be applied to the IDE that include code templates, not code templates directly. And the user would be able to apply more that one TemplateMap. These are just my thoughts, and this PTR can be REJECTED all together, if the concept of TemplateMaps is deemed unneccesary. -- Robert