On 2007-03-18, Ted Zlatanov <[EMAIL PROTECTED]> wrote: > I think this kind of help should actually live in the scratchpad, it's > exactly the right pop-up model.
As already mentioned, this has the problem that the user has to be able to toggle it on, _and_ also has to toggle it off to do anything. The statusbar would provide a constantly visible help or instruction area. > Also, it should automatically discover the current key bindings for > commands. So if I rebind "delete split" to key X, I want to see X > there. There are no identifiable commands, only arbitrary function calls. (The closest Ion comes to commands, is the context menu...) However, by overriding `defbindings`, it is possible to store this information and the `bdoc` documentation -- which may, however, be too long for a simple statusbar help display. > blank screen = first start (determined by Ion, e.g. by missing ~/.ion3 > directory) Ion already has first start detection, for the welcome xmessage -- that many seem to ignore. > Does this seem like the right way to go, a linear tutorial that > introduces simple concepts one by one? Perhaps, but as already mentioned, in the scratchpad, it has the problem of the user having to constantly toggle it. -- Tuomo
