|
In your article, made the following comment, 'Note that this does not necessarily need to be an XForms presentation; the output of the third transformation could be any XML-based language such as Adobe Flex, Microsoft XAML, or Open Lazslo though, given the one-to-one correspondance between presentation and model, the XForms model is probably the best'.
Earlier this year I was looking at XSLT transformations of XForms into both Open Lazslo and Flex (MXML) and found that although you can create many of the controls and also plumb your instance data into the model, where both these presentations differ from XForms is in how they achieve the binding of controls to the model. Open Lazslo (v4) supports XPath 1 binding expressions but, at that time, the XPath processor was not namespace aware. So, given the multi-namespaced content I was working with that meant Open Lazslo was a non-starter. I also ran into binding problems with Flex too. Flex is more curly-brace orientated and uses E4X expressions as one option for data binding. I Found that difficult to get to work but I must admit I didn't spend too much time on that particular track. I didn't get around to Sliverlight. Although one must consider using things like Flash (Flex) and Silverlight to expand the reach of ROX you realy cannot go wrong with XForms. As you so rightly said 'the XForms model is probably the best'.
|
Previous Message
