| SiDi | Hey people | 00:41 |
|---|---|---|
| SiDi | do you think it is worth the pain to have an app allowing to browse through an historical of notifications ? Just a GUI parsing the .cache/notify-osd.log file ? | 00:42 |
| GreySim | I think it would be, yes. | 00:44 |
| GreySim | I know I would use it. Not often, but I would. | 00:45 |
| ccooke | An idle moment of thought brought me this question: Would it ever be useful or interesting to be able to trigger an action when a notification matching certain parameters arrives? | 11:06 |
| ccooke | I mean, in many ways what's actually being *implemented* here is a human-computer event interface :-) | 11:07 |
| SiDi | if an action should be done automatically, the application sending the notification could manage it more accurately | 11:16 |
| SiDi | if the action is meant to be triggered by the user after he read the notification : 1) its not compulsory and we shouldnt disturb him more by adding an action to the notification | 11:16 |
| SiDi | 2) its compulsory and he should have a dialog with a compulsory action instead of a notification | 11:17 |
| ccooke | I'm thinking more user-defined or cross-package things | 11:19 |
| SiDi | ah for user defined, i wish it was there, indeed ^_^ | 11:21 |
| SiDi | but i think it wont happen. Canonical is right when they say notifications should have no actions. It's a bad design, and they dont want to introduce it again, imo | 11:21 |
| ccooke | A couple of random examples being, say: An app that can run a command whenever a certain string appears in an IM message | 11:22 |
| ccooke | Or a fun one: When battery is critical, copy some important files to a backup | 11:23 |
| ccooke | basically, I'm wondering if it's useful for package A to be able to say: Whenever a message matching <stuff> arrives, I want to be triggered so I can do <things>. | 11:24 |
| ccooke | (Oh, and how was UDS?) | 11:28 |
| SiDi | great :) | 12:00 |
| SiDi | ccooke, i think Dbus / DCOP / gconf are more adaptated for this kind of usage | 12:00 |
| SiDi | and having the app sending the message which you want to exploit be aware that package A wants to do this or that helps making sure for the app devs that its a wanted behaviour | 12:01 |
| SiDi | and if they do it the proper IPC way they can throw it more efficiently and not relay on libnotify | 12:01 |
| ccooke | Right | 12:25 |
| ccooke | in which case, are messages repeated onto dbus? | 12:26 |
| === mpt_ is now known as mpt | ||
| === mpt_ is now known as mpt | ||
| === mpt_ is now known as mpt | ||
| === mpt_ is now known as mpt | ||
| === agateau_ is now known as agateau | ||
| === mpt_ is now known as mpt | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!