<div class="gmail_quote">2011/7/6 Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 06 Jul 2011 15:32 +0200, "András Murányi" <<a href="mailto:muranyia@gmail.com" target="_blank">muranyia@gmail.com</a>><br>
wrote:<br>
> 2011/7/3 Hans-Christoph Steiner <<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>><br>
><br>
> ><br>
> > On Jul 3, 2011, at 10:04 AM, András Murányi wrote:<br>
> ><br>
> > On Sat, Jul 2, 2011 at 20:41, Hans-Christoph Steiner <<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>>wrote:<br>
> ><br>
> >><br>
> >> I just finished a big, long-overdue reorg of the<br>
> >> <a href="http://puredata.info/docs/**developer" target="_blank">http://puredata.info/docs/**developer</a><<a href="http://puredata.info/docs/developer" target="_blank">http://puredata.info/docs/developer</a>>section of the website.<br>
> >><br>
> >> * Its now a "wiki folder" so it acts like a regular wiki, not like a<br>
> >> weird plone mix of things. It also allows email subscripts to wiki pages.<br>
> >><br>
> >> * I purged old pages and redirected them to the new versions<br>
> >><br>
> >> * I cleaned up the formatting on the front page<br>
> >><br>
> >> * I updated references to CVS, etc.<br>
> >><br>
> >> * I purged a couple very out-of-date things<br>
> >><br>
> >> Let me know what you think, and please contribute where you can! :-D<br>
> >><br>
> >> .hc<br>
> >><br>
> >><br>
> > IMHO the whole GUI Plugins stuff could go under Developer.<br>
> ><br>
> ><br>
> > One goal for me is to make it easy enough for all Pd users to write their<br>
> > own GUI plugins. Honestly, I think we can make GUI plugins replace the idea<br>
> > of preferences. A simple set of preferences is very easy to understand.<br>
> > But many people find a simple set limiting, so you see many programs<br>
> > implementing huge preferences systems that mystify most users (think<br>
> > Photoshop, MS Office, OpenOffice, etc.) I think with a well designed<br>
> > scripting/plugin system, it would work better than preferences.<br>
> ><br>
> > .hc<br>
> ><br>
><br>
> Understood. However, I think plugins can never replace preferences as<br>
> they<br>
> are two different things. Plugins need to save their data somewhere too,<br>
> and<br>
> that somewhere is the preferences. If the file format of preferences was<br>
> something programmatic (ie. not "loadlib9: moonlib" but "variable<br>
> loadlib9<br>
> 'moonlib'" or something like that) there would be more change for a<br>
> convergence, but at the same time the format would be less easy to<br>
> parse/write/etc. So at the end, preferences are data, and plugins are<br>
> programs, and that's how it's good.<br>
> But, I understand and agree that you want to bring plugins closer to the<br>
> users and that that's why plugin docs won't go under developer docs.<br>
><br>
> Andras<br>
<br>
In the context of a programming environment, I don't see a lot of reason<br>
to have a separate preferences system. Things like configuring the<br>
audio and MIDI interface are usually best handled in the patch, and that<br>
should be as easy as possible. IOhannes has made big progress there<br>
with the 'mediasettings' library. Things like loading libraries should<br>
definitely be done in the patch and not globally. Just look at python,<br>
ruby, java, C++, C, etc. etc. etc for examples there.<br>
<br>
What I'd like to see is a standard Pd patch that is loaded in the place<br>
of preferences. Then you could configure your Pd setup using a Pd<br>
patch. Any Pd user is going to know how to make a patch, so if you can<br>
configure Pd with a Pd patch, then you don't need to learn any new<br>
preferences file format or system.<br>
<font color="#888888"><br>
hc<br>
</font></blockquote></div><br>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.<br>
<br>Andras<br>