Id really love to be able to specify (or even hardcode) a custom/user plugin folder that is separate from ‘supplied’ metamodule-plugins folder.
basically, MM would load plugins from both folders.
(custom folder takes preference if there is a clash)
issue :
so now, MM has so many plugins - I’d guess we are all have the same update procedure
a) download new firmware and all_plugins.
b) delete firmware and plugin folders, to ensure ‘clean’ MM
c) unzip, drag over folders from download
d) boot mm, update firmware
note: I cannot just ‘overwrite’ in (b), as version number of plugin file may change, so you’d have stale files.
step (b) means I lose anything that is not released in all_plugins.
use-case / my issue
I have various ‘custom plugins’, that aren’t in all_plugins, and likely never will be.
step (b), means I have to copy them across again.tbc, its not a huge issue… just an extra step.
But also, I’d prefer if these plugins were in a separate folder anyway, for organisation etc.
as, I kind of view ‘all-plugins’ as factory/supported modules, not strictly true but you can see where Im coming from.
Im sure its not a feature many will use…
I see 3 possible use-cases
- users testing beta / test versions of plugins
- plugins that are ‘released’ outside of all_plugins for whatever reason ( * )
- devs
( * ) I could see my Erae plugin being released as simple github download, simply because 99% of users have zero use for it, as they don’t own Erae hardware 