On Thu, 11 Jun 2009 10:37:56 -0500
"Edward K. Ream" <[email protected]> wrote:

> On Thu, Jun 11, 2009 at 8:51 AM, Kent Tenney <[email protected]>
> wrote:
> 
> >
> > with my configuration, double clicking a node icon means several
> > things:
> 
> 
> Yes, this is a messy problem.  Imo, the essence of the problem is that
> clicks are pretty low-resolution critters.
> 
> If possible, I'd rather people use commands (and corresponding
> keystrokes). There are a *lot* more possible command names than click
> types :-)

Pasting a msg. with some relevance below, i.e. that cmd_* functions in
plugins now show up as command line commands as well as menu items in
the plugins menu.

But I agree we need a way of managing a short list of possible actions
on a node.  It would be nice if the user could easily manage this list
and the list could be popped up from the keyboard as well as from a
right-click.

BTW, I'm going to be off line for a week after today.

Cheers -Terry

From: Terry Brown <[email protected]>
Subject: act-on-node commands
Date: Mon, 2 Mar 2009 09:49:47 -0600

I just pushed a change to leo/plugins/plugins_menu.py such that cmd_
functions are created as mini-buffer commands as well as menu commands
in the plugin menu.

In plugins, functions (module level) starting with 'cmd_', like
'cmd_DoSomething' appear as menu items in the plugins menu under the
plugin's name with names like "Do Something".  This is not new.

Now these same commands are accessible as mini-buffer commands.  If the
plugin was called "active_path.py" or "ActivePath.py" the command for
the 'cmd_DoSomething' function would be "active-path-do-something".

cmd_ functions are called with c as their only parameter.

Active path defines:

active-path-act-on-node      
active-path-load-recursive      
active-path-purge-vanished-files-here      
active-path-purge-vanished-files-recursive      
active-path-set-node-to-absolute-path      
active-path-show-current-path      
active-path-update-recursive      

(tab completion makes these practical)

Leo already has a repeat complex (i.e. last minibuffer) command
command, ctrl-P, so this goes a long way to the plugins publishing
commands and letting the user bind their control of choice to the
command approach I've been advocating.

The user could issue active-path-act-on-node once and then it's kind of
bound to ctrl-P until they do something else.

To fully realize this approach there needs to be an easy mechanism for
the user to bind any key stroke or qualified mouse click to a command.

Cheers -Terry





> However, I do understand that clicking is somewhat easier for newbies.
> 
> Edward
> 
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "leo-editor" group. To post to this group, send email to
> [email protected] To unsubscribe from this group, send
> email to [email protected] For more options,
> visit this group at http://groups.google.com/group/leo-editor?hl=en
> -~----------~----~----~----~------~----~------~--~---
> 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to