https://lists.w3.org/Archives/Public/public-xformsusers/2018Sep/0029
Steven: Done
https://lists.w3.org/Archives/Public/public-xformsusers/2018Oct/0004
Steven: So I listed 3 possibilities of doing it
Erik: It does look similar to
dialog
... we have those, but no way to query the state of the
dialog
Steven: Is that something we should address for dialog?
Erik: We have case() for switch and index() for repeat; so it would be reasonable to include
Steven: So what do we
prefer?
... Why don't we let it sink in a week, and we can come to a
decision next week.
Erik: Sure
https://lists.w3.org/Archives/Public/public-xformsusers/2018Sep/0014
Erik: No progress
https://lists.w3.org/Archives/Public/public-xformsusers/2018Sep/0013
Erik: Likewise
https://lists.w3.org/Archives/Public/public-xformsusers/2018Jun/0020
Steven: I forgot to give myself an action on this last week, so I will do it now.
<scribe> ACTION: Steven to think about a way of representing state change handlers in the model
<trackbot> Created ACTION-2201 - Think about a way of representing state change handlers in the model [on Steven Pemberton - due 2018-10-10].
https://lists.w3.org/Archives/Public/public-xformsusers/2018Sep/0006
Steven this is about https://lists.w3.org/Archives/Public/public-xformsusers/2018Sep/att-0006/controlv2.xhtml
Steven: Any general comments, and any answers to the questions?
Erik: Not hard to fix - the names
of the actions are a bit puzzling, a bit general.
... we should think about the naming.
... Something more suggestive
... maybe we are too used to the other actions.
... We can communicate between the two with events, that is
good.
... I'm not sure we need the actions to pass data back and
forth.
... Wondering if there is a simpler way to do it, though I
don't have a specific solution right now.
... In general, I think it's good, with a hard boundary between
the embedding and embedded forms.
... It's mostly detail about communication between. It's in
good shape overall.
Philip: I agree about the naming.
Steven: It's really a special case of dispatch; we could try to use that; I just thought since it was a special case, I'd use a different name.
Alain: I think we need a document
element for the subform.
... the subform is an XML document.
Steven: We have the
<control/> element for the contained subform.
... Oh I see what you mean; I'll update the examples.
... Should I add it to the spec, or do we need more
discussion?
Erik: Add it.
<scribe> ACTION: Steven add <control/> to spec
<trackbot> Created ACTION-2202 - Add <control/> to spec [on Steven Pemberton - due 2018-10-10].
https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0051
Steven: No new tests this week, but I will now start adding new tests rather than converting the old ones.
[None]
Erik: I'll be in Europe the next
two weeks.
... I'll let you know if I can't attend.
[ADJOURN]
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/prefer./prefer?/ Succeeded: s/Sire/Sure/ Succeeded: s/sion./sion?/ Succeeded: s/givemyself/give myself/ Present: Alain Erik Owen Philip Steven No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Oct/0005 Found Date: 03 Oct 2018 People with action items: add control steven WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]