<div class="gmail_quote">On Fri, Jun 1, 2012 at 9:31 PM, yvan volochine <span dir="ltr"><<a href="mailto:yvan.pd@gmail.com" target="_blank">yvan.pd@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 06/01/2012 09:28 PM, yvan volochine wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
but really, instead of YA-Gui-Plugin that manages all other Gui-Plugins,<br>
why not add an option in pd menu that lists and (en|dis)able plugins at<br>
user's will? (which would be part of the core of pd of course)<br>
now that pd ships with plugins ability, it would make much more sense<br>
IMHO..<br>
</blockquote>
<br></div>
and of course one should use pd_guiprefs to handle that..<div class="HOEnZb"><div class="h5"><br>
<br>
y<br><br></div></div></blockquote><div><br>Thanks for the comments. Then it seems this functionality should go into main pd-x GUI. I will try to work it out - I'll just have to make the dialog window prettier because such an ugly window that was acceptable for the plugin cannot go into main pd :o)<br>
<br>What do you think about changing the pd_guiprefs interface in way like this:<br> (current -> proposed:)<br> domain (always "pd-extended") -> could be hardwired to "pd-extended"<br> key (name of the owner module, eg. "recentfiles") -> domain<br>
(currently doesn't exist) -> key (so that you can target a single line in a config file)<br> value (the content of the whole file) -> value (the value of a single key)<br>This change would make pd_guiprefs compatible with the .pdextended file as well. Of course, then recentfiles.conf will look something like this:<br>
recentfile1: /path/to/recentfile.pd<br> recentfile2: /path/to/another.pd<br> (etc.)<br><br>András<br>
</div></div>