<questionid="dep-non-nb"> Whatothernon-NetBeansprojectsthisonedependson? <hint> Somenon-NetBeansprojectsarepackagedasNetBeansmodules (see<ahref="http://libs.netbeans.org">libraries</a>)and itispreferedtousethisapproachwhenmoremodulesmay dependonsuchthird-partylibrary. </hint> </question>
-->
<answer id="dep-non-nb">
No other dependency.
</answer>
<!-- Question: dep-platform
<questionid="dep-platform"> Onwhichplatformsyourmodulerun?Any?Doesitruninthesame way? <hint> IfyourmoduleisusingJNIordealswithspecialdifferencesof OSeslikefilesystems,etc.pleasedescribeherewhattheyare. </hint> </question>
-->
<answer id="dep-platform">
The module is 100% pure Java and runs on any platform.
</answer>
<questionid="compat-standards"> Doesthemoduleimplementsordefinesanystandards?Isthe implementationexactoritdeviatessomehow? </question>
-->
<answer id="compat-standards">
None defined or implemented.
</answer>
<!-- Question: compat-version
<questionid="compat-version"> Doesyourmoduleproperlycoexistswithearlierandfuture versions?Canyoucorrectlyreadsettings?Willfuture versionsbeabletoreadsettings? <hint> Veryhelpfulforreadingsettingsistostoreversionnumber there,sofutureversionscandecidewhetherhowtoread/convert thesettingsandolderversionscanignorethenewones. </hint> </question>
-->
<answer id="compat-version">
Only one version of the module can be installed at a time.
The settings are shared across different versions, stored
and read by Java serialization and will be read in future as well.
</answer>
<questionid="resources-layer"> Doesyourmoduleprovideownlayer?Doesitcreatesomefilesor foldersonit?Whatitistryingtocommunicatebythatandwithwhich component? <hint> NetBeansallowsautomaticanddeclarativeinstallationofresources bymodulelayers.Moduleregisterfilesintoappropriateplaces andothercomponentsusethatinformationtoperformtheirtask (buildmenu,toolbar,windowlayout,listoftemplates,setof options,etc.). </hint> </question>
-->
<answer id="resources-layer">
Yes, files are created for menus, actions, shortcuts, templates, window system layout,
settings storage - these are all in standard Open
APIs.
</answer>
<questionid="lookup-lookup"> Doesyourmoduleuses<code>org.openide.util.Lookup</code> tofindanycomponentstocommunicateto?Whichones? <hint> Pleasedescribetheinterfacesyouaresearchingfor,where aredefined,whetheryouaresearchingforjustoneormoreofthem, iftheorderisimportant,etc.Alsoclasifythestabilityofsuch APIcontract. </hint> </question>
-->
<answer id="lookup-lookup">
No. But we use our own private implementation of lookup pattern.
We are searching for instances of various services defined in *.spi.* packages.
The contract is described in JavaDoc.
</answer>
<!-- Question: lookup-register
<questionid="lookup-register"> Doyouregisteranythingintothelookupforothertofind? <hint> Doyouregisterusinglayerfileorusing<code>META-INF/services</code>? Whoissupposedtofindyourcomponent? </hint> </question>
-->
<answer id="lookup-register">
We use our private namespace <code>META-INF/debugger</code> for registration.
The contract is described in JavaDoc.
</answer>
<questionid="exec-property"> Isexecutionofyourcodeinfluencedbyanyenvironmentof system(<code>System.getProperty</code>)property? <hint> Ifthereisapropertythatcanchangethebehaviourofyour code,somebodywilllikelyuseit.Youshoulddescribewhatitdoes andthestabilitycategoryofthisAPI.Youmayuse <PRE> <propertyname="id"category="private"> descriptionoftheproperty,whereitisused,whatitinfluence,etc. </property> </PRE> </hint> </question>
-->
<answer id="exec-property"> <!-- Update also debuggerjpda/api/arch.xml/exec-property when changing this -->
<api name="SS_ACTION_STEPOUT" group="property" category="friend"type="export">
When set to Boolean.TRUE, this option is causing step out during smart-stepping
instead of step into. Thus it much faster skips code that is not selected
for debugging, but it may also skip code that should be debugged if it's
called from a source that has debugging disabled.
This is advantageous when the speed is important (e.g. in J2ME).
This property can be set through a map of properties that is passed to
JPDADebugger.attach (), like J2ME_DEBUGGER property.
</api>
<api name="netbeans.debugger.show_hidden_breakpoints" group="systemproperty" category="private"type="export">
This system property is causing the breakpoints view to show also hidden
breakpoints.
</api>
<api name="org.netbeans.modules.debugger.jpda.breakpoints.level" group="systemproperty" category="private"type="export">
Logging level for informational messages about breakpoint
submission and hits. They use Level.FINE and Level.FINER levels and
are printed into the NetBeans message log.
</api>
<api name="netbeans.debugger.start" group="systemproperty" category="private"type="export">
When this system property is set, informational messages about start of
JPDA debugger are printed into standard output (console).
</api>
<api name="netbeans.debugger.jditrace" group="systemproperty" category="private"type="export">
This system property sets the debug mode of the debuggee virtual machine
via <code>VirtualMachine.setDebugTraceMode()</code> method. See the javadoc
of that method for the description and possible values.
</api>
<api name="org.netbeans.modules.debugger.jpda.jdievents.level" group="systemproperty" category="private"type="export">
Logging level for informational messages about received JDI events.
They use Level.FINE level and are printed into the NetBeans message log.
</api>
<api name="org.netbeans.modules.debugger.jpda.step.level" group="systemproperty" category="private"type="export">
Logging level for messages about stepping, including the smart
stepping process are printed into the NetBeans message log.
</api>
<api name="netbeans.debugger.noInvokeMethods" group="systemproperty" category="private"type="export">
When this system property is set, methods invocation in debuggee is disabled.
</api>
<api name="org.netbeans.modules.debugger.jpda.invokeMethod.level" group="systemproperty" category="private"type="export">
Logging level for messages about method invocation.
They use Level.FINE level and are printed into the NetBeans message log.
</api>
<api name="org.netbeans.modules.debugger.jpda.getValue.level" group="systemproperty" category="private"type="export">
Logging level for messages about variables evaluation.
They use Level.FINE level and are printed into the NetBeans message log.
</api>
<api name="netbeans.debugger.viewrefresh" group="systemproperty" category="private"type="export">
When this system property is set, informational messages about the tasks
that refresh debugger views are printed into standard output (console).
The value of that property should contain 'w' for watches view, 'l' for
local variables view, 'c' for call stack view, 's' for classes view and 't' for threads view.
</api>
</answer>
<questionid="exec-reflection"> Doesyourcodeusesjava.lang.reflecttoexecutesomeothercode? <hint> ThisusuallyindicatesamissingorunsufficientAPIintheother partofthesystem.Iftheothersideisnotawareofyourdependency thiscontractcanbeeasilybroken. </hint> </question>
-->
<answer id="exec-reflection">
VirtualMachine.canBeModified(), TypeComponent.genericSignature() and
LocalVariable.genericSignature() are called by reflection, because it's
available on JDK 1.5 and higher only.
</answer>
<answer id="exec-introspection">
debuggercore does not use introspection.
The cases when an object is tested on various types are quite common, but not documented.
</answer>
<questionid="perf-limit"> Arethereanylimitsinnumber/sizeofelementsyourcode canhandle? </question>
-->
<answer id="perf-limit">
No explicit limits. Technically, the available memory size is the limit...
</answer>
<questionid="perf-menus"> Doesyourmoduleusedynamicallychangingcontextmenusor contextsensitiveactionswithcomplicatedlogicforenable/disable? </question>
-->
<answer id="perf-menus">
No. Context menu are rather stable once created. Enabling logic is simple.
</answer>
<!-- Question: perf-spi <questionid="perf-spi"when="init"> Howtheperformanceofthepluggedincodewillbeenforced? <hint> Ifyouallowforeigncodetobepluggedintoyourownmodule,how doyouenforce,thatitwillbehavecorrectlyandfastandwillnot negativelyinfluencetheperformanceofyourownmodule? </hint> </question>
-->
<answer id="perf-spi">
We are not able to enforce performance of plugged in code.
</answer>
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.