On Tue, 2011-03-01 at 14:13 +0100, Stefano D'Angelo wrote:
If you exclude IE entirely it gets even better. I hear maybe the very
latest release is just unawful enough that maybe you don't have to do
this, but I couldn't care less.
> >> > Just want the UI on the same machine? Do the same in your browser.
Like I said, I am doing the web thing for controllers, for which it is
> At least not in the long run. Think spatialization,
I've no doubt there's things that the browser isn't good for. They're
also usually things that involve a lot of data and you wouldn't do
remotely anyway. Use a native UI.
As for my personal goals, that's all a bunch of "nerd clicking and
staring at a screen" crap that is specifically what I am trying to avoid
> > As one example, I want to have a machine controlling the audio rig, have
Your mind pushed it too far as soon as browser specific anything got
> > If you want to do some sort of experimental fancy 3D plugin UIs rendered
Yep. I'm all for GL UIs.
> /me: GUI decorator plugin #2 - give it a bunch of metadata (and maybe
In any case where it's actually feasible for the host, or a library, to
generate the UI, rather than having to write specific UI code, that's
very definitely the way to do.
Along those lines, I need to spread the port groups extension... you can
automagically make pretty good UIs as long as you can actually group
Linux-audio-dev mailing list