Meeting minutes
Spec editors
https://
Steven: I reordered the editors.
ACTION-2309: Research xpath3 function definitions (Erik)
https://
[We noted we will come back to this later]
Steven: Next week on the agenda
ACTION-2315: Report on event handling in web components (Erik)
https://
Erik: I'm looking at it, but I need to actually write some examples.
ACTION-2312: Devise text for submission using @value (Steven)
https://
(Also covers ACTION-2317: Include submit-serialize in submission using
@value
and ACTION-2318: Add new submission text to spec)
Steven: Done.
… please check the text.
ACTION-2314: Compose text that matches the <control/> discussion for
mirroring (Steven)
https://
Steven: Continues.
ACTION-2313: Research the alternatives for 'dirty' data, and produce
code in all of them for comparison (Steven)
https://
(Was: Detecting/Ignoring unsaved data
https://
Steven: Continues
Timescale Plans
https://
Focusing today on State change events
https://
Steven: [Discusses issue at the end of the link]
Erik: My problem is what is a value.
… the control can decide itself what a value is.
… eg output
… in the model we have a bind pointing to a node, but not a value; it is not an input or output.
… what is the notion of a value in a bind?
Erik: So do we say a bind only has a value if it points to a node without children?
<Alain> https://
Steven: Do you have a proposal for another way to do it?
Alain: I was thinking about DOM mutation events
… when something is changed, it activates an event
Erik: We do have an event called xxforms-value-changed
… nothing to do with binds, but you can listen to instances.
… it is synchronous,
… with refresh, there is really a very specific point that we dispatch events
… changes are not really synchronous
<ebruchez> https://
Steven: I just need to assert in the model that I want events for a value changing, and not need a fake hidden control.
Erik: We could add a value attribute on binds, to indicate that we are listening to value changes on that.
<ebruchez> <xf:bind ref="" value="concat('foo-', .)">
Alain: Isn't that calculate?
Erik: No, it doesn't assign a value to the node
… it would be a property, like readonly, indicating that it generates value-changed in the model.
… and the other events if needed.
Alain: A boolean?
Erik: Two choices, either a string, or a sequence
… and the question is does it have other uses?
Steven: Another possibility is a null control in the model, that only is there to allow you to listen for events.
<ebruchez> https://
Erik: In our implementation we have custom MIPS
… tracking custom properties
Steven: Boolean?
Erik: We convert to a string.
Alain: XSLTForms has this as well.
… a string in DOM3
<ebruchez> my:value="."
Erik: So we could have a custom property
Alain: I would like to mention a usecase
… having value changed associated to a @calculate
Erik: You could even do calculate="." to achieve the effect
Steven: Let's sit on it a week, and come to a conclusion next week on which we like best.
AOB
Steven: Let's do submission echo next week.
[ADJOURN]