Hello fellow developers, As you may now, currently on Tizen Common, we are using the "notification" library to send interactive notifications, which will be turned in GUI pop-ups by the notification-display-service daemon of "notification-service" (please see * for a quick summary).
The only problem left was the lack of a standard way to send "answers" back to the originating framework (like : user clicked on button 1, and wrote this text). The current plugins each do it their own way, but it was suggested that we harmonize this. So I pushed a patch/review for a first implementation of this. What do you think of : https://review.tizen.org/gerrit/#/c/30093/ This change is clearly perfectible. What it does is : - add 2 functions (notification_wait_response(), notification_send_response() ) - calling the 1st function will create a temporary socket in /tmp, named after the TID (thread ID) of the originating application ; - calling the 2nd function will answer by sending a stream to this socket; - the TID is seamlessly passed as a bundle element in the notification, NOTIFICATION_RESPONDING field of the database. What do you think of this ? It was suggested that I for example do instead create a new column in the notification database for the TID. Might it break something ? (*) : https://wiki.tizen.org/wiki/UI_Notifications -- Regards, *Manuel BACHMANN Tizen Project VANNES-FR*
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
