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.
Whats wrong: 1) ToolbarPool & Toolbar are based directly on Data System. (Thats why this UI component is part of DataSystems API) Thats bad they should use some specific model, like other Swing components. They should follow MVC. 2) Toolbar implemetation is splitted to two modules - openide&core. I have never seen such *@%$@# thing - UI component is in one module and its Layout is in another one. 3) All implementation is unnecessarily complicated. 4) ToolbarPool is not reusable. There are direct calls from ToolbarLayout to ToopbarPool.getDeafult () for example. There are many other smaller problems. This part of IDE should be rewritten.
AFAIK this is duplicate, I entered such task long time ago. No resources, sorry.
*** Issue 62033 has been marked as a duplicate of this issue. ***
*** Issue 25396 has been marked as a duplicate of this issue. ***
*** Issue 42146 has been marked as a duplicate of this issue. ***
fixed 4f828389f2be
Integrated into 'main-golden', will be available in build *200811290201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/4f828389f2be User: S. Aubrecht <saubrecht@netbeans.org> Log: #59242 - toolbar rewrite
Just curious: how was it fixed? Where all the four listed points addressed? Is it now possible to use ToolbarPool for toolbars other than the default one?