XXX no answer for arch-whatQuestion (arch-overall): Describe the overall architecture. Answer:
NetBeansCore - The heart of NetBeans. It contains basic implementation of all necessary interfaces, takes care of the startup sequence and the whole lifecycle of any NetBeans based application.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: No special APIs exported beyond few friend contracts: Question (arch-time): What are the time estimates of the work? Answer:
Done.Question (arch-quality): How will the quality of your code be tested and how are future regressions going to be prevented? Answer:
The sources for the module are in the NetBeans Mercurial repositories.
XXX no answer for dep-nb
The default answer to this question is:
These modules are required in project.xml:
XXX no answer for dep-non-nbQuestion (dep-platform): On which platforms does your module run? Does it run in the same way on each? Answer:
XXX no answer for dep-platformQuestion (dep-jre): Which version of JRE do you need (1.2, 1.3, 1.4, etc.)? Answer:
XXX no answer for dep-jreQuestion (dep-jrejdk): Do you require the JDK or is the JRE enough? Answer:
XXX no answer for dep-jrejdk
XXX no answer for deploy-jarQuestion (deploy-nbm): Can you deploy an NBM via the Update Center? Answer:
XXX no answer for deploy-nbmQuestion (deploy-shared): Do you need to be installed in the shared location only, or in the user directory only, or can your module be installed anywhere? Answer:
XXX no answer for deploy-sharedQuestion (deploy-packages): Are packages of your module made inaccessible by not declaring them public? Answer:
XXX no answer for deploy-packagesQuestion (deploy-dependencies): What do other modules need to do to declare a dependency on this one, in addition to or instead of the normal module dependency declaration (e.g. tokens to require)? Answer:
Yes, fully I18Ned.Question (compat-standards): Does the module implement or define any standards? Is the implementation exact or does it deviate somehow? Answer:
Yes.Question (compat-version): Can your module coexist with earlier and future versions of itself? Can you correctly read all old settings? Will future versions be able to read your current settings? Can you read or politely ignore settings stored by a future version? Answer:
Only one core can be present in running NetBeans based application.Question (compat-deprecation): How the introduction of your project influences functionality provided by previous version of the product? Answer:
XXX no answer for compat-deprecation
XXX no answer for resources-fileQuestion (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:
Keymaps - Keymaps folder contains subfolders for individual keymaps (Emacs, JBuilder, NetBeans). The name of keymap can be localized. Use "SystemFileSystem.localizingBundle" attribute of your folder for this purpose. Individual keymap folder contains shadows to actions. Shortcut is mapped to the name of file. Emacs shortcut format is used, multikeys are separated by space chars ("C-X P" means Ctrl+X followed by P). "currentKeymap" property of "Keymaps" folder contains original (not localized) name of current keymap. Shortcuts - This folder contains registration of shortcuts. Its supported for backward compatibility purpose only. All new shortcuts should be registerred in "Keymaps/NetBeans" folder. Shortcuts installed ins Shortcuts folder will be added to all keymaps, if there is no conflict. It means that if the same shortcut is mapped to different actions in Shortcut folder and current keymap folder (like Keymap/NetBeans), the Shortcuts folder mapping will be ignored.Question (resources-read): Does your module read any resources from layers? For what purpose? Answer:
XXX no answer for resources-readQuestion (resources-mask): Does your module mask/hide/override any resources provided by other modules in their layers? Answer:
XXX no answer for resources-maskQuestion (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 ? Answer:
The core module use NbPreferences for storring properties describe current settings of Network Proxy. org.netbeans.core -
|proxyHttpHost||Host name of HTTP Proxy||Y||Y|
|proxyHttpPort||Port of HTTP Proxy||Y||Y|
|proxyHttpsHost||Host name of HTTPS Proxy||Y||Y|
|proxyHttpsPort||Port of HTTPS Proxy||Y||Y|
|proxySocksHost||Host name of Socks server||Y||Y|
|proxySocksPort||Port of Socks server||Y||Y|
|proxyNonProxyHosts||Ignore host list||Y||Y|
|proxyType||Type of Proxy Setting (DIRECT_CONNECTION, AUTO_DETECT_PROXY, MANUAL_SET_PROXY||Y||Y|
|useProxyAuthentication||Proxy Server requires user authentication||Y||Y|
|proxyAuthenticationUsername||Username for authentication on Proxy Server||Y||Y|
|proxyAuthenticationUsername||Password for authentication on Proxy Server||Y||Y|
Does it share preferences with other modules ? Yes, the Welcome Screen module listens for changes Proxy Settings and reload content when Proxy changes.
org.openide.util.Lookupor any similar technology to find any components to communicate with? Which ones? Answer:
XXX no answer for lookup-lookupQuestion (lookup-register): Do you register anything into lookup for other code to find? Answer:
The core module registers an implementation of
it allows to display in the status line a notification about thrown exception.
It's registered by
XXX no answer for lookup-remove
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:
Enabling assertions (either global -ea or for class org.netbeans.core.NotifyException only) changes the default error notification behavior. When assertions are enabled an error window pops up each time an error is encountered. Otherwise a small icon start flashing in the main status bar and clicking the icon then brings up the error dialog.
trueto workaround the bug #50423 which appears on some linuxes on JDK 1.5. netbeans.close.no.exit - Set this property to
trueif you do want to cleanup the module system, but not call System.exit at the end. Used from
NbModuleSuitefrom nbjunit library. java.net.useSystemProxies - Get this property to determine when use JDK's
java.net.ProxySelectoror core's implementation of
ProxySelector. TimableEventQueue.install - By default NetBeans based applications install their own
EventQueue. One can suppress that since versiong 3.27 of
org.netbeans.coremodule by branding key
false. Question (exec-component): Is execution of your code influenced by any (string) property of any of your components? Answer:
Creates button with given string in bottom left corner of Options Dialog.
Given ActionListener is notified when custom button is pressed.
Allows to redefine default title of Options Dialog.
One can use branding to disable installation of NetBeans own
java.net.Authenticator. Just brand
Some applications may want to proxy connections to
localhost (which by default uses direct connection in NetBeans Platform).
One can change the default by branding
specify something else than
XXX no answer for exec-ant-tasksQuestion (exec-classloader): Does your code create its own class loader(s)? Answer:
XXX no answer for exec-classloaderQuestion (exec-reflection): Does your code use Java Reflection to execute other code? Answer:
This module exports an API that allows the UI Gestures Collector module
to plug and enhance the behaviour of exception dialog by own buttons.
The behaviour is like this: If any of
then such button is going to be inserted to the exception dialog and
can react and change the behaviour of that dialog. Such a button is
going to be a "closing" one - e.g. the dialog will close as soon as
the button is pressed.
context field is accessed from editor module by reflection
The module expects profiler to provide
and interacts with it as described in
XXX no answer for exec-processQuestion (exec-introspection): Does your module use any kind of runtime type information (
instanceof, work with
java.lang.Class, etc.)? Answer:
XXX no answer for exec-introspectionQuestion (exec-threading): What threading models, if any, does your module adhere to? How the project behaves with respect to threading? Answer:
XXX no answer for exec-threadingQuestion (security-policy): Does your functionality require modifications to the standard policy file? Answer:
XXX no answer for security-policyQuestion (security-grant): Does your code grant additional rights to some other code? Answer:
XXX no answer for security-grant
XXX no answer for format-typesQuestion (format-dnd): Which protocols (if any) does your code understand during Drag & Drop? Answer:
XXX no answer for format-dndQuestion (format-clipboard): Which data flavors (if any) does your code read from or insert to the clipboard (by access to clipboard on means calling methods on
XXX no answer for format-clipboard
XXX no answer for perf-startupQuestion (perf-exit): Does your module run any code on exit? Answer:
XXX no answer for perf-exitQuestion (perf-scale): Which external criteria influence the performance of your program (size of file in editor, number of files in menu, in source directory, etc.) and how well your code scales? Answer:
XXX no answer for perf-scaleQuestion (perf-limit): Are there any hard-coded or practical limits in the number or size of elements your code can handle? Answer:
XXX no answer for perf-limitQuestion (perf-mem): How much memory does your component consume? Estimate with a relation to the number of windows, etc. Answer:
XXX no answer for perf-memQuestion (perf-wakeup): Does any piece of your code wake up periodically and do something even when the system is otherwise idle (no user interaction)? Answer:
XXX no answer for perf-wakeupQuestion (perf-progress): Does your module execute any long-running tasks? Answer:
org.netbeans.core.TimeableEventQueue - This module contains a hook to identify long running tasks inside the AWT dispatch thread. It observers the AWT event queue and if a task takes longer than expected, it invokes a sampler that creates a profiling snapshot of the IDE until the task returns back to the event queue. Time limits can be configured via system properties (in milliseconds):
org.netbeans.core.TimeableEventQueue.quantum=xyz- for how long the event queue must be blocked to start the self-sampler (by default 100ms),
org.netbeans.core.TimeableEventQueue.report=xyz- total time of blocked event queue to report a problem (by default 3s),
org.netbeans.core.TimeableEventQueue.waitcursor=xyz- time for which a problem is not reported if mouse wait cursor is in place (by default 15s),
org.netbeans.core.TimeableEventQueue.pause=xyz- time after reporting a problem for which the detection is disabled (by default 15s).
XXX no answer for perf-huge_dialogsQuestion (perf-menus): Does your module use dynamically updated context menus, or context-sensitive actions with complicated and slow enablement logic? Answer:
XXX no answer for perf-menusQuestion (perf-spi): How the performance of the plugged in code will be enforced? Answer:
XXX no answer for perf-spi
Built on December 17 2017. | Portions Copyright 1997-2017 Oracle. All rights reserved.