Hello Lieven1
the tree view is still nice, because it allows for easy one-hand navigation
and looks more interactive. Of course you can do all that on a commandline,
but it requires learning things directlyfrom the start. Where a browseable
tree allows for going along and browse. :-) Besides, commandline commands
might be a bit long, as was pointed out before.
I do like the idea about i and o though.
Automatically generating interfaces from OSC command sets. I'm not sure. I
know, they have what they call paths, but I'm not sure how hirachical they
are. I believe one should be able to query the type of an OSC
parameter/action/command, whatever they are called. So that goes part way to
automating things.
Anyone, who really uses OSC here, knows about that?
Kind regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
