SwitcherTableItemsee a javadoc. Question (arch-overall): Describe the overall architecture. Answer: The Swing components in this package were carefully designed to be consistent with standard Swing components in their function, usage and ui registration mechanisms. Question (arch-usecases): Describe the main use cases of the new API. Who will use it under what circumstances? What kind of code would typically need to be written to use the module? Answer: Primary use cases are in the NetBeans window system, as top level containers in the main window; future use cases include providing a consistent UI for tabs in the property sheet, the component inspector and the output window, but this probably will not happen for 4.0. Question (arch-time): What are the time estimates of the work? Answer: NetBeans 4.0 feature freeze Question (arch-quality): How will the quality of your code be tested and how are future regressions going to be prevented? Answer: Unit tests for the assorted data models involved are included. Question (arch-where): Where one can find sources for your module? WARNING: Question with id="arch-where" has not been answered!
The default answer to this question is:
These modules are required in project.xml:
java.io.Filedirectly? 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: No. Question (resources-read): Does your module read any resources from layers? For what purpose? Answer: No. Question (resources-mask): Does your module mask/hide/override any resources provided by other modules in their layers? Answer: No. Question (resources-preferences): Does your module uses preferences via Preferences API? Does your module use NbPreferences or or regular JDK Preferences ? Does it read, write or both ? Does it share preferences with other modules ? If so, then why ? WARNING: Question with id="resources-preferences" has not been answered!
org.openide.util.Lookupor any similar technology to find any components to communicate with? Which ones? Answer: No. Question (lookup-register): Do you register anything into lookup for other code to find? Answer: No. Question (lookup-remove): Do you remove entries of other modules from lookup? Answer: No.
System.getProperty) property? On a similar note, is there something interesting that you pass to
java.util.logging.Logger? Or do you observe what others log? Answer: nb.tabs.suppressCloseButton -
The system property
can be used to hide close buttons by default.
The system property
can be used to switch to stretching tab layout as implemented
in NetBeans version 7.0 and older.
instanceof, work with
java.lang.Class, etc.)? Answer: The displayed tabs are contained in a data model provided by the client. The "user object" of each element in the model may be a Component instance, or something else (in which case the client code must supply a ComponentConverter instance to find the correct component when an element is selected). The default implementation tests if the user object is a Component (which it always should be currently for NetBeans window system - a system of lazy loading of opened components based on ID's may be implemented in the future), and if it is not, returns null. Question (exec-threading): What threading models, if any, does your module adhere to? How the project behaves with respect to threading? Answer: All access must be on the AWT thread; this is enforced with assertions in some cases. Question (security-policy): Does your functionality require modifications to the standard policy file? Answer: No. Question (security-grant): Does your code grant additional rights to some other code? Answer: No.
java.awt.datatransfer.Transferable? Answer: None.