Well if a plugin is in a standard place, and registered just once, there shouldn't be any issues.
A skin can use it if it wants, and if doesn't, then it doesn't.
Putting 3 or 4 copies of a plugin in 3 or 4 different skin folders is just ridiculous.
Printable View
Well if a plugin is in a standard place, and registered just once, there shouldn't be any issues.
A skin can use it if it wants, and if doesn't, then it doesn't.
Putting 3 or 4 copies of a plugin in 3 or 4 different skin folders is just ridiculous.
Just trying to make skin install so its just a matter of copying a file to skin folder and have everything work without any fancy installers or a bunch of other stuff to install and setup. I Knew I would get a lot of $hit for this.
:dance::lol::dance::lol:
Um...you have me lost on this one! There are no plugins that the dfx installer installs to the skin dir, it installs them to the "default" location aka the Road Runner directory. I would also assume that in the case of the dfx skin, john has it set to not uninstall or over-install any previous exsisting plugins in the rr dir. I think I can count the number of times on one hand that I have used the dfx installers so I unfortunity can't say for a 100% whether its a fact or not, so I'll just go with 99% sure..:).Quote:
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!
:) "For example, if DFX4 "....I must have over looked those couple of words..
You usually just overlook "ME" so I feel honored to be able to correct you this time.
Ok progress has been made and i'm about at the point where i'm ready to release to some developers for testing. I just need to come up with a readme. At this point the browser will browse and download plugins but not install. In order for the install to work there need be a standardised format to releasing plugins. It definitely COULD happen.. but someone .. ANYONE needs to drop ideas on it lol. Anyways, if any of you developers would like to test by all means let me know.
I'll take a look
Me too...
I said it once, and I'll say it again...
Road Runner(or whatever you want to call it)\Plugins\plugin folder\plugin files...
Seek, Clean, and most importantly...Organized!! Over 75% of programs usually follow something along this line, this should be no different.
I wish that this would have been done long long ago as i have even mentioned it to guino at least twice about making a std for plugins. :rolleyes:
Road Runner\Plugins\Plugin Name\Files
yes
Now this should be simple with the extension plugins, and as long as people use relative paths should not be an issue.
AI scripted ones may be different though, but I'm not sure about that, you'll know better than me.
Standalone exe's again may cause extra issues, but agian as long as relative paths are used should be fine.