Re: "Easy-ui" interface code

On Fri, Nov 21, 2008 at 3:18 PM, John Rigg <[email protected]> wrote:

> I'm afraid I have to agree with Ron here. `Dumbing down' the default
> interface might attract users who are not audio engineers, but it
> is certainly not going to increase the number of professional
> recording and mastering facilities using it. I know from talking
> to colleagues in the business that the reason this software hasn't
> been adopted more widely is that it runs on Linux. People aren't
> familiar enough with it yet to risk using it to run their businesses.
> That'll take time. Making the default settings useless for anything
> but home demos isn't going to help.
>
> Paul Davis has addressed the problem of usability by making the SAE
> version of Ardour, simplified for student use, available alongside the
> "full power" standard version. That seems to be a more sensible approach
> than turning what is supposed to be a professional mastering tool into
> what looks at first glance to be a toy.

We could do that.

There could be two commands, both using the same internal real-time
audio components.  The stripped-down one would provide a simpler GUI.
I'd suggest building them both in the same source tree.  If done
right, they could even share a single JACK graph (though that hardly
seems useful).
-- 
 joq

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/