News-readers like trn and slrn are also good at this.
On Wed, Apr 20, 2011 at 10:42:23PM +0200, Julien Claassen wrote:
> * Parameters are searchable (the tree-structure is searchable for node-data)
> * Encourage programmers to use consistent long and short commands for the shell part
A main key (could be enter) would operate on whatever is selected: a
class would be expanded or collapsed depending on its previous state,
while an object would be brought up for editing. We'd have to come up
with an extensive set of editing keys to manipulate objects, and another
set of keys to manipulate classes (e.g collapse all, collapse up two
levels, jump to next class). However, in my mind, a lot of the
navigation tedium would be rendered needless by the search function.
> * What about real menus (as in file, view, edit,...)?
I don't care much for menus: they waste my time. I think the command
interface is there to handle one-shot functions like these. (see below)
> * Can one assume, that OSC is always the easiest/fastest choice and hardcode it?
OSC is by its very nature Open, i.e there are no real definition of what
it is. Besides, there are some OSC libraries out there. A library such
as the one we are pondering should basically be there to make it
extremely useful to create front-ends for applications, some of which
might already have been in existence for a long time. I think it should
most likely limit itself to managing "objects" (like parameters) and
"actions" (load, save, reset, etc.).
> * Would the commandline mainly just echo the fullscreen tree-structure?
> This would make some thing a little longer perhaps, but very
Linux-audio-user mailing list