----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: Jonathan Wilkes jancsika@yahoo.com Cc: "pd-dev@iem.at" pd-dev@iem.at Sent: Thursday, March 28, 2013 4:50 PM Subject: Re: [PD-dev] Gui plugins management (Was: I have 3 broken installs)
On 03/28/2013 01:46 PM, Jonathan Wilkes wrote:
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: pd-dev@iem.at Cc: Sent: Thursday, March 28, 2013 4:26 PM Subject: Re: [PD-dev] Gui plugins management (Was: I have 3 broken
installs)
[...]
How about we start with adding only the required mechanism so that
people
can make all sorts of plugin management plugins. Then revisit the rest later once we have a good idea of how it should be done. Making the
plugin
loader ignore a folder called DISABLED/ would make it possible to do
what
you describe in a regular plugin.
.hc
Do you want to require plugins to live in one specific "startup"
directory that
has user permissions to read/write/exec? If so, then I think the
"startup/disabled"
directory idea is adequate.
On the other hand, if you want Pd to search the standard paths for plugins then the "startup/disabled" idea is incompatible with that, no?
Permission problems
abide, plus when you want to re-enable a plugin how does Pd know which
directory
it previously lived in?
As I see it now, DISABLED/ would be ignored in all search paths. And when a plugin is disabled, it would be moved into the local DISABLED/ folder.
That method will fail when the user running Pd doesn't have permission to move those files.
-Jonathan