clean up the spew file a bit

musing.md

@@ -34,54 +34,61 @@ document element(?)
 webview
 lua's standard types
 
-## next steps
+-----
 
-* [done] change define-command so that the parameters are ordered
+a consideration we haven't touched on yet: in emacs, not all buffers
-* display unbound key error
+are files - e.g. the buffer list, or the process list, or the magit
-* ESC to cancel interactive command
+status buffer - there is a well-used affordance for elisp to put
-* autocomplete command name
+semi-persistent interactable content onscreen - do we need such a
-* parameters with non-string values (e.g. buffer)
+thing here or is it ok to say "just call gtk" to command authors
-* show current url when command inactive
+
-* [done] show prompts for parameter
+----
-* multiple buffers
+
-  - create buffer
+when input widget is active for a parameter, show the completions
-  - list buffers (where does the output go?)
+flowbox
-  - find and switch to buffer
+
+while typing, use the typed input to get a completions list.  each
+completion is an acceptable value: convert to a gtk widget by calling
+(to-label value) and add to flowbox.
 
 
-how do we do the buffer list thing?
+if the value is a table
-- generate html, or
+  if :to-label key present, use it as-is
-- use native widgets
+  else Gtk.Label { :label value.value }
+else (assume it's a string)
+  Gtk.Label { :label value }
 
-native widgets seems neater
+on RET, check there is a completion value whose stringification
-- how do we permit commands to insert widgets into the frame?
+matches the input string. Hide the flowbox
-- how do we get rid of them?
 
-we could have an "output overlay" inserted underneath the commander.
+to activate a rendered completion, the callback needs to perform the
-could we use the same thing for completions? we haven't addressed
+same action as RET would on the chosen value
-non-string parameters yet, really
 
-M-x switch-to-buffer
+is there a role for TAB?
- Buffer mai_
 
- +------+  +---------+
+- in the shell it activates completion or  shows options: we don't need that if we're updating them automatically
- | main |  | mailing |
+
- +------+  +---------+
+- we could use it to cycle through the available completions: switch
+focus from entry to step through the completions then RET activates
 
 
 -----
 
-so there are two things going on here
+# TODO
 
-1) how to implement switch-to-buffer with appropriate autocomplete
+* [done] show loading progress
-on the buffer name - perhaps involving showing buffer thumbnails etc
+* [done] show url when the commander is inactive
+* [done] visit-location url defaults to current
 
-2) in emacs, not all buffers are files - e.g. the buffer list, or the
+* custom rendering for completions (e.g. buffer thumbnails)
-process list, or the magit status buffer - there is a well-used
+* buffer name is often going to be useless. find buffers
-affordance for elisp to put semi-persistent interactable content
+ by url/title
-onscreen - do we need such a thing here or is it ok to say "just call
+   still need some 1:1 mapping between the buffer object and
-gtk" to command authors
+   a text-representable form of same
-
+* click in commander widget activates visit-location
-are these the same problem or are they separate problems? do we have
+* display unbound key error
-the second problem?  What I will do is address the first one and
+* ESC to cancel interactive command
-see if it's generalisable once I've done it.
+* autocomplete command name
+* multiple buffers
+  - create buffer
+  - list buffers (do we need this if we have thumbnails?)