On Wed, Jul 06, 2011 at 01:43:33PM -0400, Hans-Christoph Steiner wrote: > > OK, sounds good. But let's just remember the use case when we want pd to > > remember which plugins to load and which not. As plugins load before any > > patch, and they couldn't really be enabled/disabled per patch, their > > preferences will have to be stored somewhere else. We agreed before that > > the > > "/disabled" folders method is no good, and that we (probably me) will > > code > > up a logic which stores this in preferences (via ::pd_guiprefs). I'm > > interested in further brainstorming but right now I feel that good old > > preferences is something we'll have to live with for a longer time. We'll > > have to make a distinction between global stuff (plugins, global prefs) > > and > > those things which are better handled per patch, from inside patches. > > Yes, I agree. For things that affect the editor and not the patch > itself, then preferences makes more sense. > > .hc
Having a list of plugins would be probably the best cross-platform solution. However, it may be a good idea to have plugin sets, if one needs to start-up in kiosk mode or something else at times :) Perhaps the file with plugin list should supplied as an argument. Cheers, -- Ilya _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list