summaryrefslogtreecommitdiff
path: root/SPECIFICATION
diff options
context:
space:
mode:
authorMike Hearn <mike@navi.cx>2004-07-06 21:26:03 +0000
committerMike Hearn <mike@navi.cx>2004-07-06 21:26:03 +0000
commitfa61f33b9886908a66320a264fe137edfa59efee (patch)
treed1149dc7b6a3d12e4c2d8843a07c881bc9207dbc /SPECIFICATION
parentbd9b91a53dc909562911375ce83e8a0311b65970 (diff)
downloadlibnotify-fa61f33b9886908a66320a264fe137edfa59efee.tar.gz
note about knotify
Diffstat (limited to 'SPECIFICATION')
-rw-r--r--SPECIFICATION3
1 files changed, 3 insertions, 0 deletions
diff --git a/SPECIFICATION b/SPECIFICATION
index 45e0233..be305dc 100644
--- a/SPECIFICATION
+++ b/SPECIFICATION
@@ -119,6 +119,9 @@ If a client requires a response from a passive popup, it should be
coded such that a non-focus-stealing message box can be used instead
and the notification server is only used when available.
+FIXME: is this enough? is it even worth trying to be compatible with
+KNotify given how different these systems are? Might just be easier to
+implement this protocol in KNotify itself as a separate thing.
MARKUP