On Fri, 27 Feb 2009 20:54:31 +0200 "Ville M. Vainio" <[email protected]> wrote:
> A context-sensitive action (active_path) > should always take precedence over a plugin applicable to all nodes > (open_with). But very often active_path's context will be essentially the whole file. You're working in directory X, you have @path X at the root of the tree, active_path thinks it has something to offer for every node in the tree. And TL wants to use open_with specifically withing an active_path context. > > If active_path and open_with both published commands to do what they > > do, TL could bind them to whatever he wanted, open_with on > > double-click and active_path on alt-click or ctrl-space, or > > whatever. > > Nothing is preveting from still doing it. act-on-node won't prevent > anything (unless that's the sole interface a plugin provides). True, of course. > > This also sidesteps the problem that TL wants increased granularity > > in active_path's view of nodes it understands. I.e. a "do what you > > do to this node, *unless* it's a file node" action, as well as it's > > existing "do what you do to this node" action. > > Providing this kind of granularity is what act-on-node easily > provides. I do think act-on-node is a very bad fit for open-with > plugin, event though I still disagree about active_path ;-) I don't see how act-on-node helps with the granularity. Normal use of active_path is to act on both directory and file nodes. TL wants to target directories only. If active_path published a command to do what it does that could be easily bound at will to whatever the user found convenient, the granularity comes for free based on which binding the user activates. I can't see how act-on-node would deal with this, or with the open_with / active_path conflict in general. 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 -~----------~----~----~----~------~----~------~--~---
