So I guess what it really takes is a host that provides a good CLI-UI. The trouble is, I guess, designing such an UI. I'm not blind, but I would use a good keyboard driven host, and I think many others would do the same. The UI would need to be keyboard driven, but I really don't know how the input would work and which feedback in which form the host should provide. Which kind of UI is best for blind users? Does ncurses get in the way somehow or does it work well? Is a command driven interface better (you give a command, you get a response and give another command)? Since lv2 is mostly about audio so far we might not need a lot of text feedback, but it could still be handy for some things and somehow the user needs to know what he can do, which is the main reason for menus IMHO, and I don't know the CLI alternative. Regards, Philipp Excerpts from Jeremy Salwen's message of 2011-01-18 19:15:49 +0100:

Hello! There is an interface for the Hexter DSSI plugin, which uses readline. It works OK, accepting commands to change the programs, which is all I asked for and tat's really just fine with me. But Massy is right, the Bristol CLI is verynice, when it comes to changing several parameters. The pure curses interface of that would suffice. The cursor moves along correctly, so the braille display can follow. And the ":" mode offers a commandline again. But I suppose only one of them would be enough, unless someone would take the effort to write a small UI-lib for that set of features. It would be helpful and not require any layout design. Kindly yours 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

On Tue, Jan 18, 2011 at 01:15:49PM -0500, Jeremy Salwen wrote: Excellent@ I'm very glad to hear this. Right, and even then, a key/value pair passed to a GUI would do just as well. Cheers, S.M.