Thank you for the suggestion. The XForms forms do double-duty as REST-like
XML remote procedure calls, so I can't expect the clients to be able to
support a complete XForms implementation. I have to keep it simple.
The good news is that after beating on it all day long, I've come up with a
little patch to the xsltforms.js file which appears to fix the issue with
double-escaping entities. Before I turn it loose, I need to make sure that
it doesn't break anything else. Stay tuned.
On Tue, May 25, 2010 at 7:57 PM, Stephen Cameron <
Ste...@ut...> wrote:
> Hi Chris,
>
> I'm not sure if this will help, but perhaps another approach to what you
> are trying to achieve is possible.
>
> If you use the xforms <switch> construct you can completely change the
> appearance of the form and also do a submission at the time you move from
> one <case> to another.
>
> I think one of the main ideas in Xforms is that the view adapts to the
> content of the model and the model can change due to user interaction, so
> the idea of dynamically generating a form server side does not make much
> sense in general.
>
> The <switch> was a revelation for me when I discovered it, it pays to read
> up before you start doing anything with Xforms.
>
>
>
> --
> Regards
>
> Stephen Cameron
>
> Data Programmer
> Integrated Marine Observing System (IMOS)
> eMarine Information Infrastructure Project
> University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia
>
> Tel: +61 3 6226 8507
> Fax: +61 3 6226 2997
> Email: ste...@ut...
> URL: http://www.imos.org.au/eMII.html
>
>
|
