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.
Allow create and use template for modes a components via lookup. Now If I have action which is valid in all workspaces (well-known even new, user defined), I can't define and use some (self defined) mode with TopComponets. It leads to duplicate code, I use xml-layer and xml-winsys even classic creating of modes and TopComponents in code (to be able create mode in unknown workspace).
Petr, please specify in greater detail how solution should look like, winsys currently doesn't use lookup nor templates, it will be relatively big piece of work and I need some guidelines, so tell me exactly how should winsys use lookup and templates.
*** Issue 14719 has been marked as a duplicate of this issue. ***
Target milestone -> 3.3.1.
Target milestone -> 3.4
Reassigning to Peter. Peter, please go through and evaluate, thanks.
Reassigning back to me, I would overload you, Peter :-)
Not yet specified how it should work. Lowering priority, we will not do it for 3.4
Assignign to Petr, to provide more details of his idea. (see Dafe's early commnent)
Because Window System v1 will not be supported from now by our team, all old winsys issues (now "core/window system v1" issues) are going to be closed as WONTFIX. Changes in API which emerged both from UI spec and problems with adjusting to the older API are described in the document http://core.netbeans.org/windowsystem/changes.html. It shows also recommends how the client code should be adjusted to the new window system. If you think this issue apply also to the new winsys then change the subcomponent (to "core/window system") and REOPEN it.
issue doesn't apply to new window system - verified