<Alain> No...
Steven: Sorry about last week :-(
items from nested binds)
https://www.w3.org/2018/10/24-forms-minutes.html#item06
Steven: Done.
https://www.w3.org/2018/10/24-forms-minutes.html#item05
Steven: Also done.
https://lists.w3.org/Archives/Public/public-xformsusers/2018Oct/0035
Steven: Should @initial be a
nodeset?
... and do we just insert them under the root element of the
instance in the embedded form.
Erik: Who controls what?
... the embedded form needs to be ready to receive data
... it is now under control of the embedding form.
Steven: We currently just put the
data in the first instance of the embedded form.
... I don't see any loss of generality in doing that
Erik: I could see how you might
want control over it like with submission
... I don't know exactly how to do that
Steven: My original proposal was
to use submission in and out of the embedded form
... and if we wanted to do something like it, I would want to
use that as a template
Erik: We have something similar in mirroring instances between components.
Steven: So that if it changes in one place, it update in the other?
Erik: Yes
Steven: That is powerful, and very easy to use.
<ebruchez> https://doc.orbeon.com/xforms/xbl/advanced-topics/extensions#xxbl-mirror-attribute
Erik: In the component, there is only one instance that has this behaviour.
Steven: I personally like the idea of mirroring more than copying to and fro as it now is.
Alain: XSLTForms currently uses
subforms, with mirroring.
... without copying
Steven: So mirroring would suit you as well?
Alain: Yes
Steven: Shall I try speccing it?
Alain: I was thinking about
nodesets vs sequences.
... It might be nice to mix.
... I have no solution to propose though.
<scribe> ACTION: To propose text for using mirroring for <control/>
<trackbot> Error finding 'To'. You can review and register nicknames at <https://www.w3.org/2005/06/tracker/xforms/users>.
<scribe> ACTION: Steven to propose text for using mirroring for <control/>
<trackbot> Created ACTION-2206 - Propose text for using mirroring for <control/> [on Steven Pemberton - due 2018-11-14].
Steven: Then only one of my questions remains for now - Is there a better name than <signal/> for dispatching events to and from
an embedded XForms?
Steven: So to communicate with events, we have two options a new name, or new machinery to <dispatch/>
Erik: I prefer to use <dispatch/>
<scribe> ACTION: Steven to merge <signal/> into <dispatch/>
<trackbot> Created ACTION-2207 - Merge <signal/> into <dispatch/> [on Steven Pemberton - due 2018-11-14].
https://lists.w3.org/Archives/Public/public-xformsusers/2018Oct/0004
Steven: [summarises link above]
Erik: I'm not enthusiastic about
appearance="{...}"
... @appearance isn't dynamic in our implementation (though
that's our problem)
... working similar to dialog would be attractive
... we have @hide on dialog
... maybe possible for group
... using MIPs is OK too; but we have to define how it
works
... or we could use similar to switch/case, with two
mechanisms
Steven: Actually @hide is different.
Erik: Oh yes.
... We have a section component that does something
similar.
Philip: I've used your sections in the past. I think events is the obvious one.
Steven: OK, This has given me food for thought. I shall continue with the action
identification
https://lists.w3.org/Archives/Public/public-xformsusers/2018Aug/0029
Erik: No progress.
https://lists.w3.org/Archives/Public/public-xformsusers/2018Sep/0013
Erik: No progress
Steven: No progress on the other three agenda items either. More next week.
[None]
[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/in out/in our/ Succeeded: s/;/:/ Succeeded: s/THis/This/ Present: Alain Erik Philip Steven No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Nov/0002 Found Date: 07 Nov 2018 People with action items: steven to 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]