Meeting minutes
genda: https://
Sorry about the mistake in the subject
ACTION-2309: Research xpath3 function definitions (Erik)
https://
[We noted we will come back to this later]
Erik: Continues
ACTION-2315: Report on event handling in web components (Erik)
https://
Erik: I have no further action, we just need to come back to it.
Erik: Continues
ACTION-2312: Devise text for submission using @value (Steven)
https://
(Also covers ACTION-2317: Include submit-serialize in submission using
@value)
Erik: Fine with me
Alain: Yes
ACTION: Steven add new submission text to spec
<trackbot> Created ACTION-2318 - Add new submission text to spec [on Steven Pemberton - due 2022-02-25].
ACTION-2314: Compose text that matches the <control/> discussion for
mirroring (Steven)
https://
Steven: Continues, we need to come back to it.
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 Repeat with Automatic Controls
https://
Erik's reply:
https://
Erik: When we use the grid component, we have controls you can add and remove and so on.
… there's quite a large set of things you could do
… we have a subset, and get requests for more
… So, what is the minimal set of features we can add? Obviously insert and delete, setting a min and max number of repetitions
Steven: we do have @number on <repeat/>
… although that doesn't address what is being suggested here
Erik: We use a @template to say that this is the chunk of XML to add
… especially needed is the repeat is empty
… it needs this information
… for inserts
… certain interfaces do constrain you in some ways
… not sure if that was because of use cases.
… We also have reordering.
… one possibility would be for it to be open, and leave it at "The user can insert and delete".
… If you specify a template, it could be taken as a sign that you allow automatic insertions and deletions
… the ability to insert and delete and reorder is very useful.
… we also have @appearance for affecting the UI
… could be left to the inmplementor how it is done
… minimum is useful, stops people deleting everything for instabnce
… maximum is a bit less useful.
… We could have @template and @min and @max, and an attribute for allowing explicit insertions and deletions.
Alain: I would not design it this way. @template should be in the model because it is schema constrained, like minoccurs. I would prefer a binding property
… it is associated with the element for repeat
… we need not just triggers but submit
Alain: Specialised styling for triggers
… as well.
… sounds more open as a specification
<ebruchez> template="instance('my-template')"
Erik: I'm not sure about the template in the model
Alain: The template is not due to the repeat, but the schema
Erik: So a new property associated with the data
Alain: Yes
… best to write it directly in a bind
Erik: So what would the syntax look like?
Alain: If XForms were really schema drive, it wouldn't be necessary
… like generating a form from a schema
Steven: How further?
Erik: Try suggesting some design that we could talk about more concretely
Alain: So it would be extending the repeat element?
Steven: Yes, that's the suggestion
Erik: We have grid, but it doesn't have to be that.
Erik: We don't *have* to do it.
Steven: We have the functionality already, just not automatic.
https://
Steven: How about state change events?
AOB
[None]
[ADJOURN]