[gmpi] Re: Reqs draft
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 10 Nov 2003 17:38:39 -0800
On Mon, Nov 10, 2003 at 06:27:20PM -0700, eric wrote:
> I've got two signatures in the last five minutes.. I asked two musicians
> that happened to be online on my im list. Neither of them are pro
> musicians with major studios, but both seem to think the feature might
> be handy:
Might be handy will not cut it. I have a MILLION things that might be
handy, but they just can't go into GMPI, at least not now. Nothing we're
doing preculeds you from writing this as a separate spec.
> >
> >GMPI won't have incompatibilities. That is goal #1.
> >
> Oh, forgive me for assuming that bugs might exist in implementations.
> Perhaps I should ignore my decade of programming experience that
> disagrees with you.
That was a joke, son, a joke. You're far too intense. Realistically, it IS
the goal. Anything that hosts can get wrong, someone will. Let's give them
less things to get wrong.
> >It *IS* easy. The only time the host loads a plugin is when you ask it to.
> >Don't ask it to. Full stop. Probing does not involve loading the plugin.
> >USING the plugin will cause the host to crash. Don't use that plugin.
> >
> Forgive me again. I had no idea that you could predict the future of
> host implementation details. What if a user doesn't want the
> crash-prone plugin to even appear in a list inside the host for
> unsuspecting studio workers to try to load while a client is sitting in
Then he should ask the host to not list it. If the host doesn't provide
that feature, and it is a must-have feature - get a host that DOES provide
that. It's competition.
> Doesn't prior experience with a plugin standard that has already been
> implemented widely count for anything? Should we just ignore the
> problem and see if it magically disapears in GMPI, even if it hasn't
> been addressed head-on?
Define the CORE problem in one sentence.
> >Great. Write it for your host. Publish it. Heck, we can even consider
> >putting the GMPI-Recommended seal of approval on your spec. It's not a
> >requirement for the GMPI core, though. You have to admit this.
> >
> Happily, but it's far more likely to be adopted if it has the letters
> GMPI attached to it. If it doesn't, it's practically worthless unless
> by some miracle it gains some momentum and a few big developers decide
> that supporting it is a good thing to do. It could mean the difference
> between an industry-wide solution that works for all the major hosts, vs
> some little open-source developer's good idea that works in about 3
> fringe hosts. If the latter comes to be, it's not the solution it
> should have been, is it?
Then the problem must not be the problem you make it out to be. Look, I'm
working on a draft of requirements. When the draft is ready, we can bring
it up for a vote or whatever. We're at an impasse. I don't see the
utility, you can't imagine life without it. You're not going to convince me
that it is a must-have feature, and I will not convince you it isn't worth
the effort. You sound like a smart guy, and I don't want to lose smart
people's attention on this project, especially people who like open source.
:). I'm not a dick, really. Well, OK. I can be a dick. I have a vision
too, and to me, this is un-needed complexity and noise. Not many others
have chimed in here, but I will go by the will of the group.
Tim
P.S.
Here's an alternative solution:
Make a windows 'group' for each host. For all the plugins you don't want to
load, take away group rights for that dir.
----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules: Please stay on topic. You are responsible for your own
words. Please respect your fellow subscribers. Please do not
redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
