[PD-dev] Plugins preferences (Was Re: [PD] Plugins Plugin error)

András Murányi muranyia at gmail.com
Fri Jun 1 14:55:24 CEST 2012


Hey Guys,

I need some advice here.
I figured that this method won't work - one cannot control which plugins to
load *from a plugin* because some plugins may have already loaded at the
time. The only method that works without modifications to the pd GUI is the
"disabled" folders method.
At the same time, I see that pd_guiprefs.tcl is more prepared for managing
the recent files list than for other uses. When trying to add functionality
for the plugins list, the best way seemed to be to expand the init_aqua,
init_win, init_x11 functions and to create a new write_enabledplugins
functions plus a read_enabledplugins in this case. This is because the
"domain" has to be defined again for each new use - which seems superfluous
to me because it will always be "pd-extended". (The behaviour I expected
originally was this: "domain" used for something meaningful like
"recentfiles" or "enabledplugins" and "key" identifying really a single
key. At the moment, a key holds the content of a whole config file.)

So i'm asking for your kind advice on
A.) how plugin selection could be performed without a modification to the
GUI code, or shall the functionality be added to load_startup_plugins
(pd-gui.tcl:674)?
B.) should we evolve the way pd_guiprefs.tcl works in any direction?

Thanks,

András


On Fri, Jun 1, 2012 at 2:09 AM, András Murányi <muranyia at gmail.com> wrote:

>
>
> On Fri, May 18, 2012 at 4:55 PM, João Pais <jmmmpais at googlemail.com>wrote:
>
>>  Thanks for the report!
>>> I've uploaded a quick bugfix to adapt to the new menu structure: there is
>>> no Media->Preferences (or Apple->Preferences) any more, so the plugin
>>> will
>>> appear in Media (or Apple).
>>>
>>> Please note that this version still uses the deprecated method of
>>> disabling
>>> plugins by putting them in subdirectories called "disabled". This means
>>> that new subdirectories called "disabled" will be created where file
>>> permissions are sufficient. It will affect every user on the system.
>>> A new version shall make use of the "::pd_guiprefs" system instead. I'll
>>> try to give it a shot today or in the next days.
>>>
>>
>> so you mean, it pays up to wait for it, then? I'm new to 0.43, and I put
>> the plugins in a folder in my electronic section, away from windows'
>> standard system/user folders.
>>
>> João
>>
>
> Well i guess it doesn't pay up to wait anymore :)
> The pd_guiprefs mechanism is a tiny bit less handy than I expected so this
> will still take some more time for me.
> In the meantime I suggest that you get the oldstyle, but hopefully working
> version at
> http://puredata.info/downloads/plugins-plugin/releases/0.1.20120518 (of
> course if you can live with those extra directories).
>
> András
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20120601/09bd8078/attachment.htm>


More information about the Pd-dev mailing list