1 Nov
2009
1 Nov
'09
12:22 p.m.
On Sun, 2009-11-01 at 08:34 -0600, Gabriel M. Beddingfield wrote:
On Sun, 1 Nov 2009, Paul Davis wrote:
Don't forget LV2-Premium-Turbo-2000-Professional-Edition
i meant to use a name. LV2-E<N> would simply mean LV2 core + {some
defined set of extensions}. plugin and host authors could then talk
about using "LV2-E<N>".
the E<N> part merely designates a particular set of extensions, which
might be 2 extensions, or 100.
So... something like this?
LV2-EBasic := LV2 core + URI Map + MIDI Event
LV2-EPlus := LV2-EBasic + External UI
LV2-EExtreme := LV2-EPlus + dynparam + Progress
LV2-EVideo := LV2-EBasic + SMTP + Transport BTW: Some of the extension API's seem more like
plumbing. Resources for
communicating between plugins. Things that have little relevence to the
end user. For example, the URI Map seems like it's just a utility for an
extension or a plugin -- but the host doesn't necc. need to add support
for it. Is this right?
The host must support it (if host and plugin don't need to agree on it,
doesn't really make sense to be an extension anyway). The extension
defines a way for hosts to provide a URI<->int mapping facility to
plugins. It's generically very useful, and I would suspect that
many/most future extensions will depend on it.
-dr