This sounds like a good summary to me. I would only add that I think that plugin version should be a mandatory piece of stata/datom/datical/whatever. Marc --- Tim Hockin wrote: > By a vote (as best I can tally) of 5 to 2, option A, or something > similar, > wins the nomination. How's this sound? > > > 8.2 Parameters and saving/restoring state > ----------------------------------------- > > For the purpose of saving and restoring state, the abstraction of stata > (sing. statum) is introduced. A statum is a single atomic unit of > state. > A plugin's state is completely represented by it's stata. When a host > wants to save the state of a plugin (for a preset, for a project file, > etc.), the host can iterate over all the stata exposed by the plugin, > and > retrieve the current values. When restoring state, the host can set the > values of the stata. Stata may be opaque blobs, which are > unintelligible to > the host. Whether or not stata are actually entities in the GMPI system > is > TBD. It may be decided that stata are actually abstracted from > parameters, > with a common (but not mandatory) 1-to-1 mapping, or it may be decided > that > stata and parameters are the same thing. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.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