Subject: Re: [linux-audio-dev] plugin questions
From: Andy Lo A Foe (andy_AT_alsa-project.org)
Date: ma loka 11 1999 - 09:29:57 EDT
On Mon, 11 Oct 1999, Kai Vehmanen wrote:
> > world. my entire thinking has been that plugins are responsible for
> > their own GUI. a note, however, if we do end up going down this
>
> Well, I couldn't have asked for a better quote. ;) This has been
> bothering me all along and have been just waiting for the right
> moment. As we are talking about open-source plugins, plugins don't
> have to "look like" plugins...:
We are at point in AlsaPlayer development where parameters for the various
plugins (input, output, scopes) need to be created/preserved :-)
One of the ideas that have been floating around the mailing is to let the
plugins return a LIST of parameters they have. A parameter can be for
example a string, float, int, color, etc. A parameter should also have
optional constraints tied to it (int, floats can have ranges). This will
allow the application to build its own User Interface -> flexiblity.
(I realize of course that not every plugin will be able to communicate its
parameters easily this way, room should be left for plugin specfic widgets
for example)
What do you think?
> Hmm, why don't we just use a typedef that is required to be
> a floating-point type. 32bit machines can use floats while
> 64bit machines (and precision-freaks) can use doubles or even
> long doubles...?
Is it that simple? Changing the type might also change the min/max values,
or require another algorithm for better accuracy!?
Andy
-- AlsaPlayer, http://www.alsa-project.org/~andy/
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:27:13 EST