Re: [Denemo-devel] Command generation mechanism

[Éloi Rivard]

Well I have something in mind but I am not sure at which level it is compatible with denemo.

The idea would basically be:

 - Each command has a set of tags (or categories)

 - Commands can be grouped, and belong to several groups. Groups can contain some other groups of commands.

 - Each group of commands can be displayed as a menu, a toolbox, a toolbar etc.

There could be some default groups. So you can keep the current menus and their hierarchy with some tags like : navigation, view etc.

It would be nice to let the user compose his tools (menus, toolbox etc.), and allow them to quickly create a group of commands from a tag (ex. a toolbox with all the commands tagged with "piano").

In the mockups I sent some months ago, tags could also be used to filter commands, when user is searching for a specific command.

What do you think of this approach ?

2013/5/6 Richard Shann <address@hidden>

On Mon, 2013-05-06 at 11:45 +0200, Éloi Rivard wrote:
>         > 3 - Adds a new "category" argument to register_command()
>
>         what would the type of this argument be?
>
>
> The category list ?

yes - a list of strings? ...
I think it will be worthwhile to discuss the possibilities for this
list. Should it be just a list where each item is on the same level of
importance as any other?

I am thinking that at present, there is information about a command
stored in the command label, the tooltip and the labels of the menu
ancestors. This only patchily exploited for two reasons

1) the menus would become bloated if, for example, every menu had a
Delete command for deleting the things at that menu level (e.g. delete a
fingering on a note, delete a marking on a note of which fingering is a
specific case).
2) the top level of the menu is not a single menu (Score) containing
Movements as a submenu, containing Staffs as a submenu and so on. (And
in addition, Notes/Rests has been split from Chords, though they are on
the same level and other irregularities like that at the top level).


So at present there is a certain amount of hierarchy which helps finding
the right command - you look under score to find things affecting the
entire score, under measures to find things affecting the current
measure and so on. We could lose this if we replaced the present
situation with a search that just matched tags and came up with a list
of commands - it wouldn't be obvious which commands applied to the whole
score and which to a single note just from the label. And, contrariwise,
we could do much better than the current situation since we could have
more (virtual) menu hierarchies - for example commands for piano music,
or commands for deleting things ...

Perhaps what we could have is two sorts of things, say "Categories" and
"Keywords", the first being absolute binary, each command is either in
or not-in each category, the second, keywords would make a search rank a
command higher by the number of matching keywords.

I am thinking out loud here - this topic must be well researched, I seem
to remember doing something in the field myself twenty years ago or so -
but I hope these ramblings might spark off something practical that we
could do that would allow people to find out how to do things without
reading a lot of text (which I don't mind doing, but most users never
do).

Perhaps you have something very definite in mind here that will work
very well?

Richard

--
Éloi Rivard - address@hidden
       
« On perd plus à être indécis qu'à se tromper. »