Thread: Discussion of Standardization in RoadRunner skins, plugins, addons and whatever else

1st post updated. Saw a post by Guino in another thread. Wonder if anyone's told him about this one, yet?

Here's my view on the proposals:

1.a-I've fixed the source to check for the background image file (it it exisits), if the file is not found, it'll try to use a file set in "defaultbg" (variable set in skin.ini), if that does not exist, then it will default to a BLACK background.

1.b-I've added a presetspath setting which defaults to RoadRunner\Presets\ -- this is where presets will load/be saved by default.

2-I've added a default backgroundspath variable to RoadRunner\Backgrounds\ -- this is really just so skinners have a default setting when not specified in the INI files

3-I've added a default pluginspath variable to RoadRunner\Plugins\ -- this is really just so skinners have a default setting when not specified in the INI files. RR won't care where the plugins are, as long as they're properly registered. I LIKE and I'm in FAVOR of setting a STANDARD place for plugins, but I'm not keen of making it a REQUIREMENT.

4-This really is an agreement between skinnersm, but I do Like this idea, still worth mentioning that users may want to use a specific plugin with only this or that skin.. or may want to NOT use this or that plugin with a specific skin, so it would be nice to see the plugins.

5-This is a great idea for organization.

6-I agree and like the idea, I believe plugins could have some defined fields for identification, however, this may need some more discussion as it may require some extra handling from RR itself.

Nice to see ya, Guino!

#6 I have already been going through all my plugin's and creating a ind that is named same as the plugin. Could also easly add a label with its version.

I know i asked mitch about one other thing and IDK if he had talked to yet about his current changes.

Originally Posted by guino

Here's my view on the proposals:


6-I agree and like the idea, I believe plugins could have some defined fields for identification, however, this may need some more discussion as it may require some extra handling from RR itself.

No need to change anything in RR.


All a plugin needs to do, and I have started to add to mine (seeing as I made the suggestion), is set <pluginname> indicator to true, then if another plugin wants to know if a plugin is running it uses SDK.GetInd to find out (I assume RR will return indicator codes from extensions or is that the change that would be necessary?)


Also I like Blues idea of version, I think RRTrafficCams already has a version label of some sorts.




*Edit, just checked the label is called rrtc_program


Another edit @Guino, is there a command to tell a custom list to move (highlight) a specific number item in the list?

E! shouldn't that be more like rrtc_progver or something?

Originally Posted by Blue ZX3

E! shouldn't that be more like rrtc_progver or something?

Possibly, but that label was in the standalone version (someone requested a program version label, so I added program as the label) and I just ported it over when I did the extension and added rrtc to the front.


I would suggest <program ID>_version (rrtc_version) would probably be best

I'd like to add to #4.

Skinner's need to add a list of supported plugins that use skins outside of the RR standard skins.

I'm not sure how the plugin browser will handle that, but this will help users determinine
which plugins they can use and which they cannot in their current selected skin so they can add it according to their preferrences.

i.e. RRMedia - I suppose not everyone uses it and might not even skin for it.

Originally Posted by Sal R.

I'd like to add to #4.

Skinner's need to add a list of supported plugins that use skins outside of the RR standard skins.

I'm not sure how the plugin browser will handle that, but this will help users determinine
which plugins they can use and which they cannot in their current selected skin so they can add it according to their preferrences.

i.e. RRMedia - I suppose not everyone uses it and might not even skin for it.

the plugin manager(not only a browser no more) will not handle skins at all with the exception of adding the plugin to plugins.txt. After download/installation, a message box will appear telling users they may have to install skins and setup config files for some skins. There's just no other way to feasibly handle .skin file and image copy/pasting/setup.

Originally Posted by Sonicxtacy02

the plugin manager(not only a browser no more) will not handle skins at all with the exception of adding the plugin to plugins.txt. After download/installation, a message box will appear telling users they may have to install skins and setup config files for some skins. There's just no other way to feasibly handle .skin file and image copy/pasting/setup.

I kinda figured that, which why I suggested a list (i.e. PLUGINS_Supported.txt) that can be utilized whether or not a common plugin is useable for the current selected skin.