https://lists.w3.org/Archives/Public/public-xformsusers/2020Mar/0000
Steven: Thanks for the comment
Erik
... So you think that <copy/> should be allowed
everywhere that <value/> is?
Erik: Yes.
... in fact I have it running already
Steven: Should there be a rule that if one item has a copy, that all of them have?
Erik: I did consider that. select
and select1 are different. select1 is easier.
... the bound node is cleared with select1, but select you have
tokenisation in the value
... as you have <copy/> things are different, since you
are looking at a sequence of nodes.
... if you have <copy/> and <value/> then you have
to treat the <value/> in the same ways as a
<copy/>
... value returns a string
... so what do you do with <select/> in that case?
... how do you do that?
... complicated, and so we shouldn't
Steven: I'm happy with keeping
those two worlds apart.
... you asked about attributes, but I think we should handle
those with <value/> but not <copy/>
Erik: I mean not attribute
values, but whole attributes being selected.
... I don't think the text actually prohibits attributes being
set.
... for select1, there's nothing that requires one element. you
could insert a number of nodes.
... I don't think we need such a restriction, since
<insert/> does what we need.
... It's different for <select/> it becomes hard if
something returning two elements gets deselected.
Steven: Did you see my red green blue example?
Erik: It might be doable.
... if there's overlap, then if something selected in any item,
it should not be removed.
... it may not be as hard as I thought
... It's worth thinking about, as long as we handle the overlap
case.
Steven: Alain, how does this all sound to you?
Alain: I'm wondering about the overlap case.
Erik: I think if we restrict
select to elements, I think we can allow it
... we could even open it to other types of nodes. Only text
nodes would be a problem, because you can't have them
adjacent.
<scribe> ACTION: Steven to draft new text for <copy/>
<trackbot> Created ACTION-2275 - Draft new text for <copy/> [on Steven Pemberton - due 2020-03-11].
[No link]
Steven: Anyone able to compile my new server on a Mac or PC?
Erik: I have a Mac.
Alain: I can try it with Windows.
Steven: Thanks!
https://lists.w3.org/Archives/Public/public-xformsusers/2020Feb/0019
https://lists.w3.org/Archives/Public/public-xformsusers/2020Feb/0020
https://lists.w3.org/Archives/Public/public-xformsusers/2019Jun/0014
https://lists.w3.org/Archives/Public/public-xformsusers/2019Oct/0012
https://lists.w3.org/Archives/Public/public-xformsusers/2019Oct/0008
Steven: No progress this week.
[None]
[ADJOURNED]
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/a rul/a rule/ Succeeded: s/bot/not/ WARNING: No "Present: ... " found! You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy <amy> Present+ No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2020Mar/0002 Found Date: 04 Mar 2020 People with action items: 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]