On Wed, 4 Jan 2012 00:29:58 -0800 (PST)
HansBKK <[email protected]> wrote:

> On Wednesday, January 4, 2012 10:32:49 AM UTC+7, Terry wrote:
> >
> >
> >  2 make sure the functionality of plugins is exported as commands - a
> >    mix of documentation and wrapper functions
> >
> >  3 (because lists are always longer than you expect :-) I'm not sure
> >    how this relates to single/double click actions.  On the context
> >    menu you pick the item you want - the system doesn't have to guess
> >    which has priority. 
> >
> Yes, I'm specifically shooting for a scenario where the there isn't any 
> guessing involved, the user sets the priority. Think of the context-menu 
> listing being "all currently available actions", and the user having the 
> ability to choose one of them as the left-click action. If they're all 
> listed in one @ setting node, then the higher on the list the higher the 
> priority. Or one setting node per action and use numbers to prioritize?
> 
> The complexity comes from the fact that "node type" can be set by not only 
> @ directives but the protocol spec of a URL, file:// vs http:// etc. The 
> file extension/MIME issue should perhaps just be passed on to the 
> OS/browser. . .

Hmm, for a given node type, you want all the actions that make sense
for that node type in a user ordered list, and then some action (double
click?) causes the one highest on the list to occur?

I don't think we'll get there any time soon, most commands / plug-ins
which provide commands rely on the user to say "this command is
relevant to this node", by explicitly running the command on the node.
So there's no general method for having plugins identify whether the
commands they provide are relevant.  act-on-node sort of addresses
this, but it's not widely used, and many plugins provide multiple
actions, so the user would still have to pick.

 - it would be easy enough to provide a setting which adds command
   bindings as context menu entries, if that helps

 - having Leo "do something sensible" with *url* nodes is a different
   issue, basically Leo will / should just tell the OS to "do something
   sensible" with the URL.

Cheers -Terry

-- 
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