<!-- <questionid="arch-overall"when="init"> Describetheoverallarchitecture. <hint> WhatwillbeAPIfor <ahref="http://openide.netbeans.org/tutorial/api-design.html#design.apiandspi"> clientsandwhatsupportAPI </a>? Whatpartswillbeplugable. Howthepluginswillregistrate.Ifpossiblepleaseprovide simplediagrams. </hint> </question>
-->
<answer id="arch-overall">
Wizard framework will export client <code>WizardManager API</code> for create, control and close an
instance of wizard. Next to <code>WizardManager</code> will be exported SPIs implemented by
wizard providers: data part (<code>StepProvider SPI</code>, <code>Step SPI</code>,
<code>Page SPI</code>) and UI part (<code>WizardUI SPI</code>). Data and UI part
should be independent each other and e.g. two implementation of <code>WizardUI</code>
be replaceable. All SPI are plugable, registred by <code>Registry API</code>.
</answer>
<!-- <questionid="arch-time"when="init"> Whatarethetimeestimatesofthework? <hint> Pleaseexpressyourestimatesofhowlongthedesign,implementation, stabilizationarelikelytolast.Howmanypeoplewillbeneededto implementthisandwhatistheexpectedmilestonetheworkshouldbe ready. </hint> </question>
-->
<answer id="arch-time">
Estimated date of finish design is the end of November 2003, finish of implementation
is estimated in the end of December 2003. Stabilization could take about one month,
guiding SPI providers might take about one or two months. For more detailed time plan
look at <a href="http://openide.netbeans.org/proposals/wizards/plan.html">Preliminary plan</a>,
will updated to be up-to-date.
</answer>
<!-- <questionid="arch-usecases"when="init"> Describethemain<ahref="http://openide.netbeans.org/tutorial/api-design.html#usecase"> usecases</a>ofthenewAPI.Whowilluseitat whatcircumstancesandwhatwillbethetypicalcodetowrite tousethemodule. </question>
-->
<answer id="arch-usecases">
On base of reported enhancements are identified
<a href="http://openide.netbeans.org/proposals/wizards/requirements.html#usecases">
the supported use cases</a>, that cover the planned functionality. The samples
of code will be added ASAP.
</answer>
<!-- <questionid="arch-what"when="init"> Whatisthisprojectgoodfor? <hint> Pleaseprovidehereafewlinesdescribingtheproject, whatproblemitshouldsolve,providelinkstodocumentation, specifications,etc. </hint> </question>
-->
<answer id="arch-what">
<code>Wizard API</code> should be easy and useful framework provides creating
and handling dialogs which leads a user step-to-step through a task.
<code>Wizard API</code> and its framework covers the reported requirements from NetBeans
modules and from 3rd parties. <code>Wizard API</code> should replace current Wizard
framework (<code>WizardDescriptor API</code>) due to its undocumented contracts, missing
features which are asked for long time and also due to hard maintainable code.
</answer>
<!-- <questionid="dep-jrejdk"when="final"> DoyourequiretheJDKoristheJREenough? </question>
-->
<answer id="dep-jrejdk">
No answer
</answer>
<!-- <questionid="dep-nb"when="init"> WhatotherNetBeansprojectsandmodulesdoesthisonedependon? <hint> Ifyouwant,describesuchprojectsasimportedAPIusing the<code><apiname="identification"type="importorexport"category="stable"url="whereisthedescription"/></code> </hint> </question>
-->
<answer id="dep-nb">
It depends on
<api name="RegistryAPI"type="import"url="http://www.netbeans.org/download/dev/javadoc/UnsupportedAPIs/RegistryAPI/index.html" category="devel"/>. <!--The modules won't be forced to depend on this one. Projects framework is assumed depend on it,Templateprovidersshouldregisterownwizard'spagein<code>WizardAPI</code> matchingformat.Thewizard'sclientwillbeguidedtoswitchtothisonefrom deprecated<code>WizardDescriptorAPI</code>.
-->
</answer>
<!-- <questionid="dep-non-nb"when="init"> WhatotherprojectsoutsideNetBeansdoesthisonedependon? <hint> Somenon-NetBeansprojectsarepackagedasNetBeansmodules (see<ahref="http://libs.netbeans.org/">libraries</a>)and itispreferedtousethisapproachwhenmoremodulesmay dependonsuchthird-partylibrary. </hint> </question>
-->
<answer id="dep-non-nb">
It does not depend on any external library.
</answer>
<!-- <questionid="dep-platform"when="init"> Onwhichplatformsdoesyourmodulerun?Doesitruninthesame wayoneach? <hint> IfyourmoduleisusingJNIordealswithspecialdifferencesof OSeslikefilesystems,etc.pleasedescribeherewhattheyare. </hint> </question>
-->
<answer id="dep-platform">
It runs on any platform.
</answer>
<!-- <questionid="perf-scale"when="init"> Whichexternalcriteriainfluencetheperformanceofyour program(sizeoffileineditor,numberoffilesinmenu, insourcedirectory,etc.)andhowwellyourcodescales? <hint> Pleaseincludesomeestimates,thereareothermoredetailed questionstoanswerinlaterphasesofimplementation. </hint> </question>
-->
<answer id="perf-scale">
Performance of wizard window's displaying depends on graphics intensiveness
of <code>WizardUI</code> and UI part of wizard's <code>Page</code>. Won't depend
on number of wizard's steps. Performance of data proccessing depends SPI providers.
</answer>
<!-- <questionid="perf-spi"when="init"> Howtheperformanceofthepluggedincodewillbeenforced? <hint> Ifyouallowforeigncodetobepluggedintoyourownmodule,how doyouenforce,thatitwillbehavecorrectlyandfastandwillnot negativelyinfluencetheperformanceofyourownmodule? </hint> </question>
-->
<answer id="perf-spi">
<code>Wizard API</code> documentation will put a SPI provider up to distribute data processing
to respond methods, will be put up to split UI part (e.g. JPanel) form data part of wizard's page.
</answer>
<!-- <questionid="perf-startup"when="final"> Doesyourmodulerunanycodeonstartup? </question>
-->
<answer id="perf-startup">
No answer
</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.