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 plugin, so I'm the entire audience for that. I wrote it to
suit *my* needs, which may not be the needs of anyone else who happens
to pick it up. This is bad and wrong!
Plugin writers shouldn't be stifled by said guidelines, but they should
be expected to at least give them a glance.
-->Jake
On 12/11/2013 10:27 AM, 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 (Shift-F10). The context menu entries themselves do not
have visible shortcuts which would add consistency to the UI and aid
newbies. Edward mentioned that a criticism is that it is difficult to
click on headlines. I do not find it so as I do not use the mouse,
except where forced to due to the lack of a context menu shortcut.
Every menu item in the UI, no matter how accessed, should have a
keyboard shortcut. For example when someone asked for a "Paste As
Clone" shortcut, I wondered why. Alt-O-T works fine, as the
conventions have been met by providing standard hotkeys. 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.
Both approaches (keyboard and mouse) have equal value. But it must be
consistent and it must be all inclusive or you end up confusing users.
Chris
On Wednesday, December 11, 2013 4:16:07 AM UTC-8, Edward K. Ream wrote:
On Tue, Dec 10, 2013 at 12:44 PM, adrians <[email protected]
<javascript:>> 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
with Jacob on this, Edward - please don't ignore the users who
like using a mouse. Especially when using the mouse really
makes sense. See the Xiki/Acme to find out why.
A recent discussion emphasized the fact that it would be a bad
idea to *forbid* using the mouse in Leo.
By exactly the same reasoning, it is bad to *require* using the
mouse in any editor. In fact, the situation for Acme is worse.
For many, people, including me, using the mouse is simply not an
option: it would destroy my mouse-hand shoulder. It already has,
in fact.
An editor that *requires* using the mouse should be considered a
danger to public health. This is *not* simply a matter of
personal preference. So, you either show me how to do everything
interesting in Acme with keystrokes, or you write me off the list
of potential Acme users, and you resign yourself to the fact that
I shall never incorporate those features into Leo.
Of course, Leo plugins can use the mouse in any way they like, so
this is not an absolute prohibition of those features.
Edward
--
You received this message because you are subscribed to the Google
Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
