One thing thats needs to be in the requirements: metadata
whatever metadata GMPI soupports it needs to be possible to read it
whithout going to too mcuh effort - wether its internal (ie embedded in
the plugin) or external (in another file) doesnt really matter as long as
its simple to read.
Thing
On Tue, Oct 21, 2003 at 11:23:22 -0700, Tim Hockin wrote:
> > * it *must not* force any particular choice of toolkit or language upon
> > the implementer of either the host or the plugin
>
> The API will be C. GUI has not been discussed much..
Except that it will be a distinct object, not inte
On Tue, Oct 21, 2003 at 06:51:16PM +0200, Joern Nettingsmeier wrote:
> * it should be elegant, or even beautiful
> * it should be fun to program with
Can't exactly put that in a requirements doc, though I think it is on my
mind :)
> * it *must* be easy to support in host applications
This is me
On Tue, Oct 21, 2003 at 05:17:24PM +0400, "horsh" wrote:
> 1) jack-transport-like and
> 2) LADCCA-like functionality?
Those are not requirements, they're wishlist items. What are the
requirements?
Break it down to a set of statements that say something like "GMPI must
provide..." or "GMPI shou
Tim Hockin wrote:
One of my tasks as part of GMPI is to provide a draft of the requirements
doc. I turn tp you all. If you have requirements that you think should be
in GMPI - please let me know. These have to be requirements. Not
handwaving though explosions, and not wishful dreaming. Things
Well it's just requirements?
Then what about :
1) jack-transport-like and
2) LADCCA-like functionality?
the requirement resolution could sound as:
"GMPI does not need such functionality",
but if it souns as "GMPI _does_ need..."
then it would be very welcome.
horsh
8<==
One of my tasks as part of GMPI is to provide a draft of the requirements
doc. I turn tp you all. If you have requirements that you think should be
in GMPI - please let me know. These have to be requirements. Not
handwaving though explosions, and not wishful dreaming. Things that are
required
