I threw a pic up in post 1 to help explain what i'm trying to acheive here.
- -I for one would like this option with in Road Runner.- -
Uploading to MP3car downloads.
edit: Uploaded, now awaiting approval
edit2 it has been approved.
Well here is my 2 cents and I know I will get some $hit for this but.
I think the plugins should be in each skin file and not have to be registered that way the skinners would have everything needed and pre setup for that skin and not affect other skins.
This info could/should also be stored in the plugin itself as labels for display/browse both within RR or other applications, it doesn't take much to open a plugin and get that info ... it's just like:
It is also possible to make a plugin be auto-registered if RR knows the location of such plugin, other than that, it has to be registered manually.Code:
Set Plugin = CreateObject("<DLLNAME>.RRPlugin")
Version = Plugin.ReturnLabel("PLUGINVER","")
Desc = Plugin.ReturnLabel("PLUGINDESC","")
Set Plugin = Nothing
I use a centralized backgrounds directory as defined in rr.ini. Why are all the skinners creating their own? Why don't their installers read the rr.ini and add their background to the existing directory? Why is there a backgrounds and backgroundspath defined in RR.ini if everyone who uses it redefines where it points?
I know I lost the battle on the "C:\Program Files\Road Runner\Plugins" as default directory for plugins, but for those of us that do use it, it can't be too difficult to check that directory for a specific plugin subdirectory and if exist point the skin installer to it instead of installing another copy in the skin directory. Automated Installers registering plugins is a terrible idea! For example, if DFX4 added all the plugins it's capable of using under its skin folder and registered them -they work great for DFX, but when I'm done looking and delete the DFX directory from my skins directory, every other program/skin that used those registered plugins are suddenly going to stop working, and I don't know why!
As far as I know, the only addin that has a problem with a centralized plugin directory is "Coverfile" , so if the developer can't figure out how to make his plugin work in a centralized location, tell the skinners not to add it to their installers, explain why its not there, and how to get it. I really think this is better than breaking a previous install, especially if you're loading a skin just to take a look at it and your only option is a full install.
Maybe mitchjs can add "pluginspath" to RR.
In fact I have started a thread with a Standardisation for plugins.
And see how that flies.
That's why I said (and not have to be registered)