denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] Custom menus


From: Richard Shann
Subject: Re: [Denemo-devel] Custom menus
Date: Fri, 13 Jun 2008 19:42:59 +0100

On Fri, 2008-06-13 at 20:20 +0200, Jean-René Reinhard wrote:
> On Fri, Jun 13, 2008 at 02:07:37PM +0100, Richard Shann wrote:
> > 
> > On Fri, 2008-06-13 at 09:24 +0100, Richard Shann wrote:
> > > An xml file with entries (remotely) like this would do:
> > ...
> > > This file would be written whenever the keymaprc was written, so the two
> > > would always be in step. 
> > well, of course, that raises the question, could they be the same file?
> > That is, we could extend the concept of a keybindings respository to a
> > repository of actions, both built-in and custom, together with the
> > keybindings that invoke them. The repository describes built-in actions
> > just by a reference to their name, while the custom ones are described
> > in detail, with the extra fields I mentioned.
> > Richard
> > 
> 
> I really do not think this is necessarry. For implementing a new action, you
> have to write a callback. 
As U have shown, you don't have to write a separate callback for every
action - all manner of LilyPond inserts can be added by a single
callback that just needs to know what the LilyPond is that is to be
inserted, plus what types of parameters the user may need to provide.


> This is clearly something that belongs to the source
> code.
Those hundreds, if not thousands of callbacks will, I predict never get
written unless end users can create them, quickly and easily, when they
need them, and then contribute them back to the Denemo community.
Creating one would require an understanding of LilyPond, but using one
may well not. The example I gave was a guitar fingering - the user would
not need to know anything about LilyPond to use such a menu item.
Richard


>  Since you have to provide this callback when defining this action, you can
> as well describe all the info of an action in the source. What is the point of
> putting all this in a config file? I don't think it is any use to the 
> end-user.
> 
> Jean-René
> 
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]