Hi
I'm creating a new Jewel Component to make Wizards easily.
The wizard allows you to setup various WizardPages and you can navigate
from page to page with optional data validation. I think is getting pretty
cool :)
But, while creating the corresponding example, I found a bug in MXML with
constants. In the following example:
<j:beads>
<js:ContainerDataBinding/>
</j:beads>
<j:Wizard id="wizard">
<j:WizardPage id="firstPage">
<j:step>
<j:WizardStep name="second_page"
nextStep="second_page"
initialPage="true"/>
</j:step>
</j:WizardPage>
<j:WizardPage id="secondPage">
<j:step>
<j:WizardStep name="{MyModel.SECOND}"
previousStep="{MyModel.FIRST}"
nextStep="{MyModel.THIRD}"/>
</j:step>
</j:WizardPage>
</j:Wizard>
Each WizardPage has WizardStep that is a simple class that holds the data
used by the component to know what's the previous and next page, and more,
so here we have only normal getters and setters.
Now the bug: The first step don't use binding while the second binds
constants to the member properties of the class.
I'm finding that at run time using constants with binding Royale fails to
retrieve the data, but if I set normal values, the component is capable to
access the data and works fine.
I'll filled this issue
https://github.com/apache/royale-asjs/issues/337
Thanks
Carlos
--
Carlos Rovira
http://about.me/carlosrovira
