Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

I'm getting a strange effect:

If I run an XForm in an iframe, it's not getting the xforms-ready event.
If I run it in a tab of its own, it does.

This is happening over several forms, so I think it is a general effect,  
and not dependent on the form.

Here is an example.

In an iframe:

0 -> Dispatching event xforms-model-construct on <xforms-model id="M"/>
4 -> Calculate res
0 -> Calculate res
1 -> Calculate res
0 -> Calculate res
2 -> Calculate pass no
0 -> Calculate pass no
0 -> Calculate pass no
1 -> Calculate pass no
0 -> Calculate pass FAIL
2 -> Dispatching event xforms-model-construct-done on <xforms-model  
id="M"/>
1 -> Dispatching event xforms-model-construct on <xforms-model  
id="xsltforms_model_config"/>
1 -> Dispatching event xforms-model-construct-done on <xforms-model  
id="xsltforms_model_config"/>
5 -> Dispatching event xforms-enabled on <xforms-output/>
1 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
1 -> Dispatching event xforms-enabled on <xforms-output/>

That's all that happens.


In a tab:

1 -> Dispatching event go on <xforms-model id="M"/>
0 -> effectiveTarget:true
0 -> Captured event go on <XFORMS-MODEL id="M"/>
1 -> Setvalue test = 2020-04-03T23:15:15+02:00
1 -> Setvalue @req = 2020-04-03T23:15:15+02:00
0 -> Setvalue @index = 2
0 -> Dispatching event xforms-recalculate on <xforms-model id="M"/>
0 -> Calculate res 2020-04-03T23:15:15+02:00
0 -> Calculate res
0 -> Calculate res
0 -> Calculate res
1 -> Calculate pass yes
0 -> Calculate pass no
0 -> Calculate pass no
0 -> Calculate pass no
0 -> Calculate pass FAIL
0 -> Dispatching event xforms-revalidate on <xforms-model id="M"/>
1 -> Dispatching event xforms-refresh on <xforms-model id="M"/>
1 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-optional on <xforms-output/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-readonly on <xforms-output/>
0 -> Dispatching event xforms-valid on <xforms-output/>
0 -> Dispatching event xforms-value-changed on <xforms-output/>
1 -> Dispatching event xforms-disabled on <xforms-output class="wrong"/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
1 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-ready on <xforms-model  
id="xsltforms_model_config"/>

Steven


On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
<ala...@ag...> wrote:

> Hello,
>
> Please find a new release for XSLTForms at  
> www.agencexml.com/1.5beta/xsltforms.zip
>
> It has not yet been fully tested because a lot of changes have been made  
> and you are welcome to locate remaining issues with your own forms.
>
> The XSLT part has been reduced to minimal for better performance.  
> Instead of parsing the XPath expressions and transforming all the XForms  
> >elements into HTML elements, it basically just transposes the non-HTML  
> elements into sort-of custom elements: xforms:* elements become  
> xforms->* elements with xf-* and ev-* attributes.
>
> Have a look with your favorite browser debugger! Actually, authors could  
> even prefer to directly write/generate forms with this new notation and  
> forget >about the XSLT step. You can compare two sources for the same  
> form: hello.xml and hello.htm
>
> XSLTForms Javascript classes constructors are obtaining their properties  
> directly from xf-* attributes and XPath parsing is then performed.
>
> No ids are automatically added as previously.
>
> Extra xf-* attributes and extra xforms-* elements are used to embed  
> effective HTML rendering elements, for example, xforms-body or  
> xforms-repeat->item while, before, span or div elements where used.
>
> XSLTForms classes for xforms:select and xforms:itemset had to be  
> partially rewritten.
>
> SVG support has been basically tested too.
>
> CSS styling is not anymore based on xforms-* classes but on custom  
> element names and attribute selectors. For example, the extra xf-bound  
> >attribute, when present, says that the XForms control is bound to a  
> node, eventually a not relevant one, and the extra xf-notrelevant  
> attribute can, >then, be checked...
>
> Thank you for your contribution!
>
> --Alain