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 156453 - TopComponents that can enable/disable their properties
Summary: TopComponents that can enable/disable their properties
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: issues@platform
URL:
Keywords:
: 156452 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-08 06:19 UTC by venkatramakkineni
Modified: 2012-08-15 23:38 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description venkatramakkineni 2009-01-08 06:19:38 UTC
Each TopComponent should be able to set its own properties.

Editor.TopComponent.Closing.Enabled=false
Splitter.Respect.MinimumSize.Enabled=false
TopComponent.DragAndDrop.Enabled=false
TopComponent.Maximization.Enabled=false
TopComponent.Resizing.Enabled=false
TopComponent.Sliding.Enabled=false
TopComponent.Undocking.Enabled=false
View.TopComponent.Closing.Enabled=false

Chances are an application will have windows with some of the windows with all the properties enabled and some with a
few enabled.Even if the majority of the applications will not use it. Lack of this feature only makes the API rigid as
opposed to flexible.

From my under standing the window system is centralized. i.e. the properties of all windows are being set by reading one
Bundle.properties file located in branding module. A better approach would be to read the bundle.properties file from
each topcomponent's module.

Although this will assume that the same properties will be enabled for all the topcomponents in the same module, it is
better flexibility than what we have now. Users might group the topcomponents with similar properties or they can create
a class with specific properties by extending TopComponent  and create instances of the class where ever they need.
Comment 1 Lukas Hasik 2009-01-08 08:22:23 UTC
*** Issue 156452 has been marked as a duplicate of this issue. ***