<br><br><div class="gmail_quote">2011/7/3 Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at">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;">
<div style="word-wrap:break-word"><div><div></div><div class="h5"><br><div><div>On Jul 3, 2011, at 10:04 AM, András Murányi wrote:</div><br><blockquote type="cite"><div class="gmail_quote">On Sat, Jul 2, 2011 at 20:41, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> I just finished a big, long-overdue reorg of the <a href="http://puredata.info/docs/developer" target="_blank">http://puredata.info/docs/<u></u>developer</a> section of the website.<br>
<br> * Its now a "wiki folder" so it acts like a regular wiki, not like a 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></blockquote></div><br>IMHO the whole GUI Plugins stuff could go under Developer.<br></blockquote><div><br></div></div></div></div><div>One goal for me is to make it easy enough for all Pd users to write their own GUI plugins. Honestly, I think we can make GUI plugins replace the idea of preferences. A simple set of preferences is very easy to understand. But many people find a simple set limiting, so you see many programs implementing huge preferences systems that mystify most users (think Photoshop, MS Office, OpenOffice, etc.) I think with a well designed scripting/plugin system, it would work better than preferences.</div>
<div class="im"><div><br></div><div>.hc</div><div> <span style="border-collapse:separate;border-spacing:0px 0px;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word">
</div></span></div></div></div></blockquote><div style="word-wrap: break-word;"> <br>Understood. However, I think plugins can never replace preferences as they are two different things. Plugins need to save their data somewhere too, and that somewhere is the preferences. If the file format of preferences was something programmatic (ie. not "loadlib9: moonlib" but "variable loadlib9 'moonlib'" or something like that) there would be more change for a convergence, but at the same time the format would be less easy to parse/write/etc. So at the end, preferences are data, and plugins are programs, and that's how it's good.<br>
But, I understand and agree that you want to bring plugins closer to the users and that that's why plugin docs won't go under developer docs.<br><br>Andras<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;"><div class="im"><div><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"></span></div>
</div></div></blockquote></div>