Re: [Xsltforms-support] server-based select loading

[COUTHURES A. <ala...@ag...>]

Hi André,

XForms instances are basically used to store input values entered by the 
user but can also be used to dynamically construct and update controls 
such as xf:select1 or others. Instances can be initialized internally or 
externally and submissions permit to replace data into them. This can 
appear on every possible event so a sub-control can be populated 
dynamically.

Defining different models allows to limit refresh operations. I'm also 
considering the always read only constraint for performance.

Mixing HTML controls with XForms controls is possible with XSLTForms but 
not recommended because it requires complex use of Javascript.

Do you have other questions?

-Alain

Le 23/02/2011 16:38, ac a écrit :
> Hi Alain,
>
> This seems like a trivial question, but looking around, I have not 
> found an answer yet, so I am turning to you.
>
> Along with a main model, some XSLTForms have to display a selector 
> (e.g. xf:select1) where the options are typically provided by a 
> server, typically on return from a previous form submission.  What is 
> the best practice for managing this?  Should the options be part of 
> the model and some script in the form loads them to the selector?  can 
> the pre-loaded selector be part of the model? is there a better way of 
> doing this?  In this case, although it seems preferable, there is no 
> requirement for the selector to be xForm, as it could be html, other 
> than it needs to be transmitted and received together with the (main) 
> XSLTForms model.  The number and exact nature of the selector options 
> do vary according to context, previous selections, and submitted model 
> content.  Also there is typically more than one selector involved, 
> along with other guizmos like checkboxes etc.
>
> Thank you.
>
> Regards,
> Andre
>
>
>