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.

Bug 92987 - Dynamically create i18n-ed palette categories
Summary: Dynamically create i18n-ed palette categories
Alias: None
Product: platform
Classification: Unclassified
Component: Palette (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Stanislav Aubrecht
Keywords: I18N
Depends on:
Blocks: 90211 100267
  Show dependency tree
Reported: 2007-01-22 18:27 UTC by _ edwingo
Modified: 2008-12-22 11:31 UTC (History)
4 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description _ edwingo 2007-01-22 18:27:33 UTC
Visual Web Pack (VWP) has special "complib" component library files that a user
can import into the IDE. The complib file has a set of components that are
organized into categories. Both the components and categories are i18n-ed. The
current API seems to only support i18n of components but not categories. As I
understand it, categories are created dynamically by creating folder FileObjects
but I don't see an easy way of i18n-ing the names of the folders. If there is an
easy way, please provide code for a code sample.

To see what I mean, in VWP, Tools->Component Library Manager->Import and browse
a complib file. See for a
link to a complib file. See for installing
Comment 1 _ edwingo 2007-01-22 18:33:29 UTC
One detail I left out was to first create a WVP project. Create a new "Visual
Web Application" and navigate to Page1.jsp. After importing the complib file,
you must add the component library to your project. Goto the Projects Window and
invoke the context menu on the "Component Libraries" node to add an imported
component library to your project. Then the components should appear in the
palette when the view is set to "design" on Page1.jsp.
Comment 2 Ken Frank 2007-04-17 16:10:59 UTC
a few questions to let us prepare for i18n testing, since m9 new and noteworthy
mentions this will be part of it

- bug is still in new state - will it be fixed for m9 release ?

- what does it mean about i18n'd of categories from a user scenario ?

- is the complib mentioned below sufficient still for using for testing this ?
Comment 3 Stanislav Aubrecht 2007-12-05 11:39:39 UTC
i'm not sure i understand what this issue is about.
if the user creates a new category using palette's ui then there's no way to specify internationalized name. but it
doesn't make sense in this case as the palette category won't be shared with other nb users.
if a module installs new categories into palette then it can take advantage of the default i18n mechanism in file
systems (attribute "localizingBundle")
Comment 4 Ken Frank 2008-01-15 18:11:46 UTC
could filer clarify about questions asked and also
if this is still valid now that nb6 has visualweb as part of it ?