<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 10, 2011, at 2:55 PM, András Murányi wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Tue, May 10, 2011 at 12:19, IOhannes m zmoelnig <span dir="ltr"><<a href="mailto:zmoelnig@iem.at">zmoelnig@iem.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "> <div class="im">-----BEGIN PGP SIGNED MESSAGE-----<br> Hash: SHA1<br> <br> </div><div class="im">On 2011-05-08 18:40, Hans-Christoph Steiner wrote:<br> ><br> > Also, I think Pd-extended should include a number of plugins by default,<br> > like perhaps your completion plugin. So that would mean that the plugin<br> > reports would be shown by default.<br> <br> </div>though it's a bit annoying that the user cannot chose to _not_ use a<br> certain plugin. (moving the foo-plugins folder into a "disabled/" folder<br> is probably a not such a good idea either, as in this case this would be<br> a global operation that effects all users on the machine)<br> <br> (right, there is the plugins-plugin which might solve this; i don't know<br> about it's persistency though)<br> </blockquote><div> <br>If I'm getting right what you mean by persistence, plugins-plugin uses the "move to /disabled" method too. Actually, I don't really sympathise with that method, and I was trying to advocate something else (also because you may not have write access to every folder) and I'll be happy to update the plugin as soon as a cleaner method is agreed on.<br> <br>Andras<br></div></div></blockquote></div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="font-size: 12px; "><div><span class="Apple-style-span" style="font-size: medium;"><br></span></div><div><span class="Apple-style-span" style="font-size: medium;">I think its also something that needs to be addressed, but I'm not sure there is a clear idea of how it should be done. I agree there should be some kind of -noprefs/-nostdlib type flag that disables the loading of plugins, perhaps just -noplugins?</span></div><div><span class="Apple-style-span" style="font-size: medium;"><br></span></div><div><span class="Apple-style-span" style="font-size: medium;">The plugins-plugin might be able to override the current plugins loading logic by being loaded first, then breaking out of the loop that loads the rest. That'd be a big hack, but could be an easy way to test out different ideas of handling the loading of plugins.</span></div><div><span class="Apple-style-span" style="font-size: medium;"><br></span></div><div><span class="Apple-style-span" style="font-size: medium;">.hc</span></div><div><span class="Apple-style-span" style="font-size: medium;"><br class="Apple-interchange-newline"></span>----------------------------------------------------------------------------<br></div></span><div><br></div><div>"A cellphone to me is just an opportunity to be irritated wherever you are." - Linus Torvalds</div></span> </div><br></body></html>