Re: Possible modifications to interface

Hi Patrick,

I have not seen any responses to your message.  So, here are my
(limited) thoughts...

On Tue, Nov 4, 2008 at 2:06 AM, Patrick Shirkey
<[email protected]> wrote:
>
> I am revisiting Jamin for the first time in a while and have some
> thoughts for discussion.
>
> 1: What do people think of making jamin into a daemon and splitting the
> interface code off so that the daemon could be run in the background and
> the interface could be used only when needed.

My initial reaction is that a mastering tool like Jamin is mainly a
hands-on interactive session.  Running it in the background as a
daemon seems pointless for its primary intended use.  Other uses may
appear over time, of course.

As a matter of program architecture, I like the idea of separating the
real-time audio processing from the user interface, which could
sometimes run on a separate machine.

Changing our existing code base to fit that model would be quite a lot
of work, I believe.  More than I want to take on right now.  I'd
consider that a good candidate for a Jamin 2.0 release if someone
wants to do that some day.

The existing code seems useful and stable.  I consider that a success.
 Some day it will need to evolve, but there does not seem to be much
demand for that at the moment.

> 2: With the bypass toggles we could resize the interface to make it
> smaller if certain parts are not being used. This could be an option in
> the preferences.

Probably so.  I don't know the UI code well enough to know what that
would involve.

Regards,
-- 
 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=/