added some 'fixme's (VB)

docs/menustuff.txt

@@ -8,6 +8,11 @@ Reading these files it becomes easy to understand the menus.
 I (Joris) have given the file you are reading a new purpose:
 client-supplied menus.
 
+fixme: some of this stuff is described better in
+       ./docs/lcdproc-dev/language.docbook so this file should
+       probably be removed after extracting the information that is
+       not anywhere else; see also ./docs/netstuff.txt (Volker)
+
 
 INTERNAL SERVER DATA
 
@@ -66,10 +71,14 @@ checkbox	A checkbox. The client is notified whenever the state is
 slider		A checkbox. The client is notified whenever the slider is
 		moved.
 
+fixme: missing description of numeric, alpha, ip, ..., see
+       ./docs/lcdproc-dev/language.docbook (Volker)
+
 Note that I have changed the 'function' menu type to 'action' here. The name
 'function' was only appropriate internally, because a function was called.
 For clients we only know an action will be performed.
 
+fixme: missing reference to lcdexec (Volker)
 
 
 RETURNED DATA
@@ -118,6 +127,9 @@ When it is set at 40%.
 
 
 
+fixme: missing description of menuscreen_goto for session control (Volker)
+
+
 --
 Complete rewrite, Joris Robijn, 20011015
 

docs/netstuff.txt

@@ -1,6 +1,10 @@
 LCDproc client/server protocol, V0.2
 ---------------------------------------------
 
+fixme: most of this stuff is described better in
+       ./docs/lcdproc-dev/language.docbook so this file should
+       probably be removed after extracting the information that is
+       not anywhere else; see also ./docs/menustuff.txt (Volker)
 
 QUICKSTART
 ----------
@@ -229,12 +233,6 @@ key #id
 	Sends a keypress to the client.
 
 
-
-
---- Not implemented yet ---
-The functions below are planned but not completed.
-
-
 client->server functions
 -------------------------
 client_add_key #id
@@ -298,11 +296,8 @@ driver_del #id? (or type)
 
 server->client functions
 -------------------------
-menu #menu #item #action
+menuevent #menu #item #action
 	Tells the client that a menu item was selected/used/etc...
-	The action can be "click", "up", or "down".  The client should
-	handle this according to what type of menu item has been
-	activated, and should probably send the server a new item
-	definition if the item was a checkbox or slider.
-
-
+	The client should handle this according to what type of menu
+	item has been activated, and should probably send the server a
+	new item definition if the item was a checkbox or slider.