s/sis/si/

XForms from XSDs?

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0051.html

Steven: Can we help this guy?

Philip: I've been in a similar situation.

Steven: I've seen it done; Cordys had such a system, where you could drop an XSD, and it produced a first version of a form, with a binding to everything
... and you could then drag controls around, or delete them.

https://stackoverflow.com/questions/18616008/xsd-to-xforms-and-xforms-to-xsd-conversion

Steven: So there is that link, which has some pointers, you could try those three suggestions.

Dispatch with delay="0"

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0049.html

Steven: We need Alain to answer the question
... so I'll put this on hold until he returns.

Events after xforms-disabled

https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0000

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0030

Steven: The problem I was trying to solve was that the disabled event is dispatched after the control is disabled.
... So maybe the solution is just to warn people of that, and say that listeners must be outside the control itself.

Erik: What is our exact wording about disabled handlers? Let me look...

<ebruchez> 5.3.5 The relevant Property

<ebruchez> "event handlers for events targeted to a non-relevant control are disabled"

<ebruchez> "When a control becomes relevant, the action handlers that listen for events on the control must be re-enabled"

<ebruchez> 8.3.3 Relevance

<scribe> ACTION: Steven to replace all "listeners" to "handlers" [recorded in http://www.w3.org/2017/06/07-forms-minutes.html#action01]

<trackbot> Created ACTION-2128 - Replace all "listeners" to "handlers" [on Steven Pemberton - due 2017-06-14].

Steven: Does our wording reflect reality?

Erik: XML Events is meant to be a declarative spec for DOM Events, so what happens in DOM events should drive this
... so we don't really need to disable such handlers.

Steven: So you are saying don't disable handlers, because after the control is disabled, events are not sent?

Erik: Yes, that was a suggestion.
... If we remove that wording, I don't see a problem.
... I don't see the motivation for that text
... you could make a case for a handler nested in a control being disabled.

Steven: Sounds convincing.

<scribe> ACTION: Steven to draft text for handler disabling [recorded in http://www.w3.org/2017/06/07-forms-minutes.html#action02]

<trackbot> Created ACTION-2129 - Draft text for handler disabling [on Steven Pemberton - due 2017-06-14].

AOB

[None]

[ADJOURN]

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

FAILED: s/sis/si/
Succeeded: s/aia/ai/
Succeeded: s/Oewn/Owen/
Succeeded: s/IF/If/
Present: Erik Philip Steven OwenAmbur
Regrets: Alain
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0001
Found Date: 07 Jun 2017
Guessing minutes URL: http://www.w3.org/2017/06/07-forms-minutes.html
People with action items: steven