#
#
# patch "README.driver"
#  from [6fa9383bfdab921320e2eaa876389c3b5bc81dd5]
#    to [d8f2697860d8b0b256b86d5e8a50f036e615de79]
#
============================================================
--- README.driver	6fa9383bfdab921320e2eaa876389c3b5bc81dd5
+++ README.driver	d8f2697860d8b0b256b86d5e8a50f036e615de79
@@ -18,7 +18,7 @@ where
                 on (use "-" to denote that you want to call a dialog without a
                 database / workspace affinity, f.e. the preferences dialog)
 
-    <function>  is the name of the function you like to call (see below)
+    <function>  is the name of the function you like to call
 
     <args>      are optional arguments to this function
 
@@ -34,19 +34,27 @@ valid):
     $ guitone exec ~/workspace showPreferences
 
 
-Function Reference
-==================
+Available Dialogs
+=================
 
-TODO, please check the sources, particularily
+If you call
 
-    src/view/dialogs/(Database|Workspace|)DialogManager.h
+    $ guitone exec
 
-for a list of callable public slots in the meantime.
+you'll receive a basic help message with all implemented methods and their
+arguments. For now there is no further documentation available.
 
 
 Known Bugs
 ==========
 
-* Please note that there is currently no way of getting data from these calls in
-  a defined way. If you need such a thing, drop me a mail and I'm sure we find
-  a solution.
+The dialog system might signal certain data back to the caller, f.e. the ID
+of a committed revision or the path of a checked out workspace. These
+information are logged as informative messages into the output, f.e.
+
+21:54:01.807: info: src/GuitoneDriver.cpp:signalWithOneStringArgument:309: signalled, value: /Users/tommyd/foo
+
+Currently there is no way to find out which signal actually dropped this
+value, which is actually a Qt nuisance. I hope I can fix this in later
+revisions.
+