[PD-dev] Gui plugins management (Was: I have 3 broken installs)

[Hans-Christoph Steiner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/27/2013 01:27 PM, IOhannes m zmoelnig wrote:
> On 2013-03-27 21:12, Hans-Christoph Steiner wrote:
> 
>> I think that a -noplugins flag is a no brainer, that should be 
>> included.  I'm still on the fence about adding the ability to disable
>> plugins via the interface.  The model so far for installing and
>> disabling externals, plugins, etc. is putting them in the 
>> user-installed folder or moving them out of that folder.  Its very 
>> simple and easy to maintain.
> 
> definitely not.
> 
> i find myself cursing everytime i want to use/not use a given
> gui-plugin.
> 
> moving files around is _not_ a way to configure your system. at least i
> know of no system that is configured like that; not that there *are* some
> system settings that work like that (`find /etc -type d -name "*.d") but
> those are not for user-preferences that might change today *and*
> tomorrow.
> 
> also, there might be a reason why Pd-extended switched from loading all
> libraries by default to a scheme, where the user has to explicitely
> enable a given feature. taking your gui-plugins argument to PdX, we could
> have simply told the users to just move all the objects/externals they
> don't want to use to a save place (and turn off the "couldn't find"
> errors)
> 
>> I have no objections for adding the possibility to allow plugin 
>> management in a plugin, but I'm not sure about including it by 
>> default.
> 
> it's simply not possible to unload a given plugin with a plugin that is
> loaded afterwards. (at least not until all the gui-plugins implement an
> unloading mechanism).
> 
> if we have the opportunity to get a built-in gui-plugins management 
> instead of the  "last-files" i'm all for it (as the latter can be easily
> implemented as a plugin, unlike the former)

The plugin-management plugin can just move the plugin files itself to
disable them, so we could just make the system plugin loader ignore a folder
called DISABLED/ inside each path.  Then people can make plugin-management
plugins using that mechanism, and customize the rest however they see fit.
This would also be easy to understand for people who are just moving files
around manually.

.hc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBCAAGBQJRU1lyAAoJEJ8P5Yc3S76BJxMP/iPnbWYHCcCwTCpWk8q/99UA
Uk0gUQJB4IJGnRNCCsSLRqRjapbLaM91foPd0dmiJXLsxBMnqwXn1VjlrBIP3IR6
QqAsXtyBjdluz9+eBa9/dvn9juZqrqdlcD8I8TuJO+K1HMPeKNoQK3mQ3hmN+4yZ
QPO8SwuQYZcOTPyxZgF/ETF0FJ9XkFkmbyQoPwFow/A/rjUbx7mmX5TVPP9P18cE
Tav/D/3ghm1cHgNqYNMPxxdSaxxJ0FSg2Xz08xyaGVozksL3ynqWDBkDIxrTOs3Z
E0FckoaeAcx1a2wd6blHfQSD7U3It99rSP9dth4yxM+T9/YzsOxaKZ/0YtqxEcUW
TNK2AdF6xUl7ULVTTog6DLjQ2MvFHezD6dM92BhawfAasdBkcJCC9HGl0CiNL8n6
YeI6bmtg1eCNx3qQ0lOpBPL78MUxnnp7mM0nLbh+Purr2hHedswHHUOrczcw7YZd
eDd8R2MkRCo5CGLbIec0/t0Nc4zUIfPXVZHt4sFhFwRBga0dYUcbqHC2Amfpbs+b
HS0IqHTJxTn2uc81is5leH/dEv1ZMwz+2UrRu3Jk2f9i0NQCC+q4/i5nXPoE8zg3
RGnNoe6aZWqtWEeReBj8WVKI2haK9xyS9B3LMHi84osnWFw8V1CLZd/v8tnOLZVJ
eQJS/pN0eJ6uYohaJ+Kj
=wRBw
-----END PGP SIGNATURE-----