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

not that I'm the most prolific plugin creator .. but that sounds like a solid plan !

Yay...

Originally Posted by Sonicxtacy02

well i stand corrected then! . Might i take the time to request a few standards for plugins.. not because i want to "dictate", but because it'll save me and most everyone else fits when it comes to plugins. That being said, all plugins should be compressed in ZIP format. Blue gave me some code making it very easy to install plugins from within my plugin browser if they are compressed via .Zip vs. .Rar. This of course means NO installers for plugins. Also, if there are dlls other than the main plugin .dll that need be registered you have 2 options:

1. register them in your code(if you need help with this pm me)
2. document which files need registering along with the method they need be registered (regsvr vs codebase etc)

These little requirements should make most all plugins past and present compatible with the plugin browser.

so Yay or Nay ?

That seems to me like a solid plan.

Mulling over this thread and comments posted, a lot of good points & resolutions have been proposed.

I, for one, are in agreement w/ the use of $rrpath$Plugins\ folder and the use of the $pluginspath$ variable.

It just makes sense and falls in-line with RR's structure.

So when is this proposed to happen?

I am NOT in agreement with the use of a pluginpath as Enforcer said, its pointless and un-needed!!

And a Yay for everything else...

Originally Posted by Valheru

...

Well yes and no .. for example. El Camino released the IE Radio plugin, but because of the way it displayed info (and because El kindly passed over this sources) the version in TEK3 is a different EXE than the one EL's supplied, but more importantly it uses different LABELS / VARIABLES .. so IE Radio.EXE that came with El-s skin will not display info correctly in TEK3 and vice versa ... this is also the case for 3 or 4 (of 11) other plugins in TEK3 skin.

How is this to be handled ... Do I re-release the updated IE Radio as a new version and overwrite the older version - meaning that someone elses skin will not work any more ?

Originally Posted by Blue ZX3

Any script/app that is customized for that particular skin should really be stored in the skin folder's "scripts" (or whereever the skinner wants to place it) folder just like all the scripts that make DFX run. They are all custom to that skin an is why they are all inside that skin's folder.

If it is not as the author released then it is a b'stard plugin and has no right in the plugins folder. Unless it is totally renamed and will not conflict with the original. Ie must also use all different label/button indicator names etc.

Originally Posted by Blue ZX3

I am NOT in agreement with the use of a pluginpath as Enforcer said, its pointless and un-needed!!

And a Yay for everything else...

Just had a peek down below and indeed hell hath frozen over.

I know, I know, for once we actually agree on something...)

Originally Posted by enforcer

just had a peek down below and indeed hell hath frozen over.

Hey BlueZX3 what about the "background=" thing in RRConfig mentioned earlier in post #7?

Originally Posted by Fiberoptic

Is there anything we can do to help?

i could sure use a small amount of space for the .xml file the plugin browser will update from. At this point i'm using my own webspace... but upon release i'll need something a bit more reliable. An simple ftp i could upload to would do wonders.

might be worth having a few mirrors for the xml filelist