Re: UI Principle 3: Recognition over recall

On Tue, Dec 17, 2013 at 2:25 AM, Matt Wilkie wrote: > when I'm using the mouse, which I do a lot, I want to keep using the > mouse. When I'm using the keyboard, which I also do a lot, I want to keep > using the keyboard. > I haven't paid much attention to mouse-related issues because Qt widgets

Re: UI Principle 3: Recognition over recall

On Wed, Dec 11, 2013 at 7:27 AM, Chris George wrote: > An example of inconsistency is the current context menu that pops up on > r-clicking a node. No shortcuts and the 'move' plugin doesn't provide any > either for its large number of options which forces me to use the mouse. ? I'm confused. I

Re: UI Principle 3: Recognition over recall

On Thu, Dec 12, 2013 at 8:24 PM, Chris George wrote: (Most GUI apps restrict Alt-Key combinations to support the menu items. > It's always legitimate to consider the key bindings that should be in effect by default (that is, for newbies). I doubt, though, that such things are preventing people

Re: UI Principle 3: Recognition over recall

(Shirt-F10) is a UI convention that works in *most* applications that worry about things like conventions. The only reason I use the keyboard so much, as compared to people who started using computers after Windows took over, was that I learned to write using Wordperfect 5. There are many prog

Re: UI Principle 3: Recognition over recall

On Wed, 11 Dec 2013 07:27:51 -0800 (PST) Chris George wrote: > IMHO, everything that can be done with the mouse should be accessible to > the keyboard and vice versa. One thing I noticed immediately about Leo is > that the context menu on nodes and body text is not accessible via keyboard The

Re: UI Principle 3: Recognition over recall

On Wed, Dec 11, 2013 at 9:31 AM, Jacob Peck wrote: > This whole thread has made me think that we need a 'Leo UI/UX guidelines > for writing plugins' section in the docs. > Doesn't the world already have several guidelines? > Plugins are written in a fundamentally different way than the core

Re: UI Principle 3: Recognition over recall

On Wed, Dec 11, 2013 at 9:27 AM, Chris George wrote: > IMHO, everything that can be done with the mouse should be accessible to > the keyboard and vice versa. > I agree. > Every menu item in the UI, no matter how accessed, should have a keyboard > shortcut. > Not a shortcut: there are too ma

Re: UI Principle 3: Recognition over recall

This whole thread has made me think that we need a 'Leo UI/UX guidelines for writing plugins' section in the docs. Plugins are written in a fundamentally different way than the core -- rather devil-may-care, as they're not vital. As far as I know, I'm the only one who uses my nodewatch.py plu

Re: UI Principle 3: Recognition over recall

IMHO, everything that can be done with the mouse should be accessible to the keyboard and vice versa. One thing I noticed immediately about Leo is that the context menu on nodes and body text is not accessible via keyboard (Shift-F10). The context menu entries themselves do not have visible sho

Re: UI Principle 3: Recognition over recall

On Wed, Dec 11, 2013 at 7:47 AM, Jacob Peck wrote: > I intend to write an acme-mode plugin at some point here > ...It will also provide keyboard-only ways of doing things -- I'm aiming > to capture the features of acme, not the 'mouse is king' spirit. > Excellent. I'll look forward to it. EKR

Re: UI Principle 3: Recognition over recall

On 12/11/2013 7:16 AM, Edward K. Ream wrote: On Tue, Dec 10, 2013 at 12:44 PM, adrians > wrote: I guess it wasn't clear from my previous post that Xiki is basically Acme. The thing is that it both of these use the mouse to achieve quite a bit of their functi

Re: UI Principle 3: Recognition over recall

On Tue, Dec 10, 2013 at 12:44 PM, adrians wrote: > I guess it wasn't clear from my previous post that Xiki is basically Acme. > The thing is that it both of these use the mouse to achieve quite a bit of > their functionality, and, from another thread, I see that Edward is against > mouse use. I'm

Re: UI Principle 3: Recognition over recall

On 12/10/2013 1:30 PM, adrians wrote: Since you've brought up Acme, I'd recommend looking at Xiki to see if any of it's (and Acme's) ideas can be borrowed for Leo. The screencasts are worth watching. -- Adrian Thanks for this! You've given me another toy to play

Re: UI Principle 3: Recognition over recall

I guess it wasn't clear from my previous post that Xiki is basically Acme. The thing is that it both of these use the mouse to achieve quite a bit of their functionality, and, from another thread, I see that Edward is against mouse use. I'm with Jacob on this, Edward - please don't ignore the us

Re: UI Principle 3: Recognition over recall

Since you've brought up Acme, I'd recommend looking at Xiki to see if any of it's (and Acme's) ideas can be borrowed for Leo. The screencasts are worth watching. -- Adrian On Tuesday, December 10, 2013 10:46:09 AM UTC-5, Jacob Peck wrote: > > On 12/10/2013 10:38 AM,

Re: UI Principle 3: Recognition over recall

On Tue, Dec 10, 2013 at 9:46 AM, Jacob Peck wrote: On 12/10/2013 10:38 AM, Edward K. Ream wrote: > >> In effect, each Leo headline is like a command line! The way around this >> are buttons that create the appropriate headline. >> > A very important concept to grasp, for sure. To further drive t

Re: UI Principle 3: Recognition over recall

On 12/10/2013 10:38 AM, Edward K. Ream wrote: In effect, each Leo headline is like a command line! The way around this are buttons that create the appropriate headline. A very important concept to grasp, for sure. To further drive this home, I recommend playing around with the ACME editor, and

UI Principle 3: Recognition over recall

Comments on http://youtu.be/xYiiD-p2q80 at 16:32 QQQ A widely used heuristic for evaluating user interfaces: the relative ease with which we can *recognize* things rather than *recall* them...We recognize shapes and faces at extremely fast speeds. QQQ This may be Leo's most important strength.