On Sat, Dec 08, 2018 at 10:28:41PM +0000, Tedd Sterr wrote: > A few thoughts (some of which have already been touched on by others)… > > * clicking a button results in a textual message that provides no indication > that it came from a button press as opposed to being typed (I could type > "yes" for some other reason and you'd interpret it as a button press.) I > understand this is to provide a text fallback, but that doesn't mean such > information can't be inculded anyway for cases where it's understood. > > * there's no linkage of the reply with the buttons (if you send two messages > with buttons and I reply with "no", which set of buttons did that come from?) > > * the buttons feel very detached - they're just appended onto the end. that's > not necessarily bad, but wrapping them in an enclosing tag would group them > and allow identification. > > * maybe some business rules regarding how many times buttons can be pressed > (can I press the same button twice? can I press multiple buttons? should all > buttons be disabled after the first press?) > > * I think a few more suggestions for use cases might help people to better > see the utility. > > * this is limited to just buttons - which could be useful - though someone > will soon decide they also need drop-down lists, then someone else will want > checkboxes… > Obviously people will start muttering "shouldn't this just be data forms?" > Maybe it could be generalised into "Inline Data Forms" to provide a > reasonable subset of components suitable for use in chats (data forms's scope > is much wider). [And now it's too big and complex and you just wanted a > simple lightweight solution for buttons!] > > * based on some of the above: > > <message from="[email protected]"> > <body xml:lang="en">Approve? (yes/no)</body> > <buttons xmlns="urn:xmpp:tmp:buttons" id="bd43d059"> > <button style="confirm" value="yes"> > <label xml:lang="en">Yes</label> > <label xml:lang="sv">Ja</label> > </button> > <button style="deny" value="no"> > <label xml:lang="en">No</label> > <label xml:lang="sv">Nej</label> > </button> > <button style="warning" value="danger"> > <label xml:lang="en">Danger!</label> > <label xml:lang="sv">Fara!</label> > </button> > <buttons> > </message> > > <message to="[email protected]"> > <body>yes</body> > <buttons xmlns="urn:xmpp:tmp:buttons" responseto="bd43d059"/> > </message> >
I imagined you'd either put unique values into the `@value` or let that problem be solved by threads. Side-note: I again wish we had a generic in-reply-to thing. -- Kim "Zash" Alvefur
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
