Matthew J. Graham wrote:
- Construct my model with: <vs:coverage> <vs:spatial> <vs:region xsi:type="vs:AllSky"/> <vs:region xsi:type="vs:CircleRegion">...</vs:region> <vbs:region xsi:type="vs:RectangularRegion">...</vs:region> </vs:spatial> </vs:coverage>
- Construct my view with:
<xforms:select1 ref="vs:coverage/vs;spatial/vs:region/@xsi:type"
Matthew, the ref="..." should point to only one node, as the ref="..." is used to point to the element or attribute you want to be used as a "container" for the value selected by the end-user.
Here is my suggestion:
From a UI perspective, the user first selects the region type and clicks on a submit button. Then on another page he enters the additional region-type specific information.
So your model just looks like:
<vs:coverage>
<vs:spatial>
<vs:region xsi:type=""/>
</vs:spatial>
</vs:coverage>And then when the type is selected, with XUpdate in the page flow controller you add the appropriate elements to the instance and hand it over to another page with the controls for those other elements.
Does this make sense?
Alex
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
