https://lists.w3.org/Archives/Public/public-xformsusers/2019May/0002
Steven: We are planning an event
in Amsterdam in October, XForms jubilee will be a focus
... Both Alain and I will be at Markup UK
... I'm giving a tutorial
Alain: I'm giving a paper on XQuery and XForms
https://lists.w3.org/Archives/Public/public-xformsusers/2019Apr/0052
Closing if no comments
https://lists.w3.org/Archives/Public/public-xformsusers/2019Apr/0053
[Closing if no comments.
https://lists.w3.org/Archives/Public/public-xformsusers/2019Apr/0036
[Closing if no comments]
Steven: All 3 duly closed
https://lists.w3.org/Archives/Public/public-xformsusers/2019May/0004
Steven: I've done a revision; next week we can discuss.
https://lists.w3.org/Archives/Public/public-xformsusers/2019Apr/0046
Erik: "MIP" is the wrong
term.
... We have no way of updating the MIPs from the view
... One requirement is the ability to make a control
non-visible/relevant from the control itself.
... Alain mentioned the trick to do it.
... In general I agree with the proposal, at least up to a
point.
Steven: We have already moved alert into the model, this seems to be doing the same thing in the other direction.
Erik: We have to decide which
behaviours we need.
... Relevance and readonly are two clear cases.
... The notion of having the data non-relevant could be matched
with visibility, against disabled.
... In HTML, readonly and disabled are two distinct things.
Steven: We have that too
surely.
... We use the term disabled for a control, and for the CSS,
and the event
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#form-control-non-relevance-conditions
Erik: There are issues
anyway.
... We use enabled and disabled to reflect relevance
Steven: Originally at least we said that that was a styling issue.
Erik: There are two different
intentions. In our implementation we use readonly for
that.
... it could become a bigger topic
... we have some decisions to make
Steven: How do we go
further?
... Next steps?
Erik: One simple option,
relevance and readonly in the model and in the view. It doesn;t
effect the model, and has the same effect. THat is the simple
version
... Processing model is that nothing fancy is going on
... Just on the view
... Other option, use the opportunity to add another way to
handle the three representations of the control.
... Not entirely clear in my head yet though.
... What does Alain think?
Alain: Not sure.
... Is it easier as HTML or as in the model?
... For me it would be easier as in the model. Not sure about
it for others.
Erik: Are you questioning whether to do this at all?
Alain: No, it is needed. There is a trick for relevance, but not for readonly. It would be good to have.
Steven: We need a more
fleshed-out proposal.
... I have a lot of unfinished actions, so I don;t want to own
it.
<scribe> ACTION: Erik to think more about properties on controls.
<trackbot> Created ACTION-2255 - Think more about properties on controls. [on Erik Bruchez - due 2019-05-15].
[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/</,/ Present: Alain Erik Philip Steven No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2019May/0005 Found Date: 08 May 2019 People with action items: erik 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]