OpenIDE-Module-IDE-Dependencies: IDE/1 > X.XX (it will be defined yet)
as window system is part of openide.
And dependeny on implementation:
OpenIDE-Module-Module-Dependencies: org.netbeans.core.windows > X.XX
. But since the core-windows.jar does not provide any public API
this should be used only in ui-declaration module (like core-ui.jar).
java.io.File
directly?
Answer:
No.
Question (resources-layer):
Does your module provide own layer? Does it create any files or
folders in it? What it is trying to communicate by that and with which
components?
Answer:
Yes. Default window system layout is in module layer. Other modules can define
their own winsys elements (mode, group, component) in their module layer.
Question (resources-read):
Does your module read any resources from layers? For what purpose?
Answer:
Module reads its own configuration from its layer and eventualy from other module layers
if provided. Data have following
folder structure.
Question (resources-mask):
Does your module mask/hide/override any resources provided by other modules in
their layers?
Answer:
No.
org.openide.util.Lookup
to find any components to communicate with? Which ones?
Answer:
Window Manager implementation (from core) registers itself and lookup is used
from API part to get the instance and return as
WindowManager.getDefault ()
and also WindowManager.componentRegistry().
gets the registered instance of TopComponent.Registry
.
Also there are provided implementations of DialogDisplayer.getDefault()
and NodeOperation.getDefault() services.
There is also provided service which implements org.netbeans.core.NbTopManager$WindowSystem
interface, which is used in core for managing start and exit of window system implementation.
Question (lookup-register):
Do you register anything into lookup for other code to find?
Answer:
WindowManager and TopComponent.Registry are registered. Used to find sinleton
instance by singleton accessor.
Question (lookup-remove):
Do you remove entries of other modules from lookup?
Answer:
Yes. It removes implementation of NodeOperation.getDefault()
service provided by openide-explorer module.
System.getProperty
) property?
Answer:
There are some, will put later here.
Yes.
netbeans.winsys.imageSource
netbeans.winsys.dndfade.on
netbeans.winsys.disable_dnd
netbeans.winsys.allow.dock.anywhere
netbeans.winsys.oldtabs
netbeans.winsys.oldtabs.view
netbeans.winsys.oldtabs.editor
netbeans.tab.close.button.enabled
Question (exec-component):
Is execution of your code influenced by any (string) property
of any of your components?
Answer:
Yes. Component can control its persistence and way how they are displayed in container.
PersistenceType
Question (exec-classloader):
Does your code create its own class loader(s)?
Answer:
No.
Question (exec-reflection):
Does your code use Java Reflection to execute other code?
Answer:
No.
Question (exec-privateaccess):
Are you aware of any other parts of the system calling some of
your methods by reflection?
Answer:
No. Now is the window persistence independent from projects.
Question (exec-process):
Do you execute an external process from your module? How do you ensure
that the result is the same on different platforms? Do you parse output?
Do you depend on result code?
Answer:
No.
Question (exec-introspection):
Does your module use any kind of runtime type information (instanceof
,
work with java.lang.Class
, etc.)?
Answer:
No.
java.awt.datatransfer.Transferable
?
Answer:
Module uses the same standard protocol as actions module. In case of Copy-n-Paste
instances of Workspace, Mode and TopComponent are passed to clipboard.
There are defined three kinds of DataFlavor
S for pure internal usage for DnD of TopComponent
S.
They are constructed using MIME Types constructed following way:
DataFlavor.javaJVMLocalObjectMimeType + "; class=org.openide.windows.TopComponent"
for DnD of TopComponent
DataFlavor.javaJVMLocalObjectMimeType + "; class=org.openide.windows.TopComponent$Cloneable"
for DnD of TopComponent.Cloneable
DataFlavor.javaJVMLocalObjectMimeType + "; class=org.netbeans.core.windows.dnd.TopComponentDragSupport$TopComponentArray"
for DnD of TopComponent
arrayTopComponnet
with slow internal responsiveness, e.g. with slow
painting routines, validating, bad UI management etc.TopComponent
implementation, just could be provided performance
test which could indicate some specific TopComponent
instance doesn't fullfil certain performance criteria.
Interface Name | In/Out | Stability | Specified in What Document? |
---|
New configuration data | Under Development | http://core.netbeans.org/windowsystem/changes.html#3.4.2 new configuration data |
Old configuration data | Deprecated | http://core.netbeans.org/windowsystem/changes.html#3.4.6 old configuration data |
Interface Name | In/Out | Stability | Specified in What Document? |
---|
PersistenceType | Exported | Private |
Valid values are "Never", "OnlyOpened". Default is "" (empty string) and means always persistent.
"Never" means that TopComponent is not persistent at all. It lives only during IDE run.
"OnlyOpened" means that TopComponent is serialized only when it is opened. If it is closed
instance is lost.
Default behaviour is that TopComponent is serialized always regardless it is opened or
closed.
It is client property of TopComponent. Usage example: To disable persistence of TopComponent
use putClientProperty("PersistenceType","Never"); in initialization code of TopComponent
eg. in constructor.
|
netbeans.winsys.imageSource | Exported | Private |
Valid values are path to image in NB like "org/netbeans/core/resources/splash.gir".
It puts the specified image into the the emptied documents area.
it is experimental now.
-J-Dnetbeans.winsys.imageSource=org/netbeans/core/resources/splash.gif
|
netbeans.winsys.dndfade.on | Exported | Private |
Valid values are "true" and "false". Default is "false".
If it is "true" it paint faded feedback during DnD of windows. Keep in mind it makes
some performance impact on DnD.
It is experimental now.
-J-Dnetbeans.winsys.fade.on=true
|
netbeans.winsys.disable_dnd | Exported | Private |
Valid values are "true" and "false". Default is "false".
If it is "true" it disables DnD of windows.
-J-Dnetbeans.winsys.disable_dnd=true
|
netbeans.winsys.allow.dock.anywhere | Exported | Private |
Valid values are "true" and "false". Default is "false".
It allows user to move (e.g. using DnD) TopComponent S between editor(document) and view
which is restricte otherwise.
It is experimental now.
-J-Dnetbeans.winsys.allow.dock.anywhere=true
|
netbeans.winsys.oldtabs | Exported | Private |
Valid values are "true" and "false". Default is "false".
If it is "true" it used the old tabs for the compponent containers.
It is experimental now.
-J-Dnetbeans.winsys.oldtabs=true
|
netbeans.winsys.oldtabs.view | Exported | Private |
Valid values are "true" and "false". Default is "false".
If it is "true" it used the old tabs for the compponent containers, but only for view
kind of containers.
It is experimental now.
-J-Dnetbeans.winsys.oldtabs=true
|
netbeans.winsys.oldtabs.editor | Exported | Private |
Valid values are "true" and "false". Default is "false".
If it is "true" it used the old tabs for the compponent containers, but only for editor
kind of containers.
It is experimental now.
-J-Dnetbeans.winsys.oldtabs=true
|
netbeans.tab.close.button.enabled | Exported | Private |
Valid values are "true" and "false". Default is "true".
This switch is relevant only in case old tabs are used.
If it is true tabs in JTabbedPane contain
close button. It is possible to close given tab by clicking on this close button.
It can be set on command line or in ide.cfg. Usage example: To disable close buttons use
-J-Dnetbeans.tab.close.button.enabled=false
|
Interface Name | In/Out | Stability | Specified in What Document? |
---|
windowmanager-properties2_0.dtd | Exported | Under Development | http://www.netbeans.org/dtds/windowmanager-properties2_0.dtd -//NetBeans//DTD Window Manager Properties 2.01//EN |
mode-properties2_0.dtd | Exported | Under Development | http://www.netbeans.org/dtds/mode-properties2_0.dtd -//NetBeans//DTD Mode Properties 2.0//EN |
tc_ref2_0.dtd | Exported | Under Development | http://www.netbeans.org/dtds/tc_ref2_0.dtd -//NetBeans//DTD Top Component in Mode Properties 2.0//EN |
group-properties2_0.dtd | Exported | Under Development | http://www.netbeans.org/dtds/group-properties2_0.dtd -//NetBeans//DTD Group Properties 2.0//EN |
tc_group2_0.dtd | Exported | Under Development | http://www.netbeans.org/dtds/tc_group2_0.dtd -//NetBeans//DTD Top Component in Group Properties 2.0//EN |
sessionsettings-1_0.dtd | Exported | Under Development | http://www.netbeans.org/dtds/sessionsettings-1_0.dtd -//NetBeans//DTD Session settings 1.0//EN |
Built on October 24 2003. | Portions Copyright 1997-2003 Sun Microsystems, Inc. All rights reserved.