Really we have two different proposals here
Proposal 1: Magic Action
* Add "inline-reply" capability
* When "inline-reply" supported
* Add the magic ("inline-reply", "Type a reply...") action
* User submits reply
* Application gets ActionInvoked(id, "inline-reply::the-entered-text")
Proposal 2: Hint
* Add "inline-reply" capability
* Add org.freedesktop.Notification.Reply(id, message)
* Regardless of "inline-reply" support
* Add the "inline-reply": "Type a reply..." hint
* User submits reply
* Application gets Reply(id, "the-entered-text")
Must admit I'm starting to favour the hint
Or we do a combination:
* Add "inline-reply" capability
* Add "inline-reply" action
* Regardless of "inline-reply" support
* Add the "inline-reply": "Type a reply..." hint
* Then when replied, app gets ActionInvoked(id, "inline-reply::the
entered text")
* If server doesn't supoprt, it will be a regular button for it and
the app gets ActionInvoked(id, "inline-reply")
I still want a relationship between an action and the reply feature. You
can have e.g. "Mute", "Remind", "Reply" (and only the latter will open a
reply field).
_______________________________________________
xdg mailing list
xdg@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/xdg
_______________________________________________
xdg mailing list
xdg@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/xdg
