Frederic Vanmol wrote:
How about a compromise? Make a library with GMPI utilities. One of those utilities would then be a plugin manager. A host can choose if it uses this or not.Who said anything about a library? All I've asked for is a standard way to say "load this plugin" or "don't load that plugin" -- a standard DTD or something similar, preferably stored in a well-known place. You guys are proposing solutions that are more complex than the one I proposed. A simple problem requires a simple answer.
- EricHow about a compromise solution, something that enables plugin management without actually requiring it? I realize this is jumping deeper into spec issues, but here goes: give every plugin a bit of meta data that says "I failed to load <when> in app <who>." Any app can query this before loading to be on guard (or not). An app which catches a load failure can populate this (or not).
-- ~ <http://www.dilvie.com/>
---------------------------------------------------------------------- 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
