Re: [Issue 34089] New - build target customizer should update data in instantiate()

Hello,

I have a question regarding the report quoted at the end of the e-mail.
Consider a customizer, that aggregates content from more modules, or 
from unrelated parts of a module. For example, there's some core part, 
which allows the user to choose a compiler's implementation. Then 
there's an implementation-specific part, whcih customizes settings 
recognized specifically by the selected impl.

Is there some general pattern, how to make the option values, which 
could be  altered in the core part of the Wizard/Customizer, available 
to the impl-specific part for reading and integration ?

Otherwise, since the impl-specific part can only use APIs, it would read 
the values that may be obsolete in the current interaction's context.

It would be quite awful to expose the UI in API, or create an additional 
data model, when the options are persisted using ContextSettings anyway.

Thanks for suggestions.
-Svata

[email protected] wrote:
> http://www.netbeans.org/issues/show_bug.cgi?id=34089
> 
>                   Summary: build target customizer should update data in
>                            instantiate()
>                 Component: java
>                   Version: 4.0 dev
>                  Platform: PC
>                       URL:
>                OS/Version: Windows 2000
>                    Status: NEW
>         Status Whiteboard:
>                  Keywords:
>                Resolution:
>                Issue type: DEFECT
>                  Priority: P3
>              Subcomponent: code
>                AssignedTo: [email protected]
>                ReportedBy: [email protected]
> 
> 
> CompilerOutput.CustomizerPanles.instantiate() does
> not update the data -- it is updated right away in
> panels. This does not comply with the
> documentation in projects-ide that says that the
> data should be written back in instantiate() (and
> not sooner). The reason is that to support
> Ok/Cancel in customizers.
> 
>