probably so considering the .xml is updated locally each time RR is run provided there's an internet connection and the file has a newer date the the local file. Its all done by timer though so it doesnt slow down RR at all.
Ok, If if it's so NOT needed then......why doesn't RRMedia work when I put it in Road Runner\Plugins\RRMedia then???? :D
I know why, its because it uses $RRPATH$ as the root starting directory. That is exactly why I thought a PluginsPath in the rr.ini would just be a good idea. If a plugin takes care of itself based on where it is at, thats perfect. If not, that path can be uses as a "home base / Root Directory" for reference in the script or plugin. It also give the Plugin manager that Sonic is working on a place to look for the plugins. Say you install the plugins in a different directory, of your choice, how will the plugin manager know where to look? With a PluginManager.ini file? So why not just put it in the rr.ini and be done with it. It's one line, its simple, and matches the rest of the way RR works with SKinPath, BackgroundPath, MEdiaPlayerClassicPath and on and on....
@ALL@ - First post updated. If anyone is in contact with Guino tell him about this effort and as soon as he blesses the proposals they become standards and I'll create a sticky for the forum.
I'm going to need permissions to moderate a couple threads like this one and a locked one for the approved Standards FAQ.
@Valhera@ - One of the things that I feel we have lost is the collaboration we used to have. If your changes to ElCamino's addon were openly discussed in the forum, maybe a consensus could be reached and everyone could benefit from the changes, then it could be included in the plugins directory. I used to make it a habit to dissect every new skin released for pieces that I liked and then port them to my skins, but this created a duplication nightmare. I remember CDRSkull used to write hardcoded .exe addons for his skins because he didn't want his code stolen, but that doesn't support the community.
I still have a folder (that needs to be moved into the PLUGINS directory) that was written for Proximo's CFX skin that has scripts to Load and Unload CDs into the RR playlist as well as sorting current playlist by filedate that I add to any new skin I use routinely. If he hadn't publicized it, gotten community involvement, and changed it for interoperability between skins, every skinner would have to write their own or do without. I am overwhelmed by DFX, but I'm sure there are instances in it that could be ported to the PLUGINS directory and shared with other skins. Your skin is probably no exception. This is what I have referred to as programming in a vacuum. And we need to open up again, sure some will have ideas only they will use but the majority will benefit from the interaction and probably emerge better for it and I know the community will be better off.
The DFX skin has no "plugins" for say installed in the DFX directory, they are more like "helper scripts" that enable stuff specific to the skin. The only exception may be the Locker script. But there are 4 others out there, and I just made one the way I wanted specifically for the skin, it was never intended to be released as a plugin, as there were so many choices already.
I still feel strongly about the pluginsPath in the rr.ini, I know beating a dead horse, but it just makes so much sence!
One of the best and most used skins out there, The LSXVoid skin, installs a folder LSTools to the RRRoot path. The skin depends on looking in the RR Root path for that folder. If a PluginsPath were made avail, this would make it independant of looking somewhere based on the root rr folder.
Well, I don't know how MP3Car will feel about another RR section mod hehe I came on recently, Then Mitch, then Enforcer got mod privileges in the Plugins section just a short time ago. And of course there has been Guino since the beginning. Many of the super mod's have also offered to help in any was possible to help organize the plugins sections, and are even working on a VBulitin plugin to manage the plugins.
If you want, you can PM me, or IM me on Yahoo at JohnWPBFL if you need something done or changed and I will get on it immediately. You can start a thread, and I can make it a sticky, and then be able to edit the first message with any changes. I can also lock it if you want ect. I am sure that Mithch and Enforcer can also help with this... what do you think?
Sound fine to me. I haven't been a moderator since the early eighties back in the BBS days and it was a pain in the **S then. So I wasn't really looking to forward to it. You guys can handle that part for me.
I saw the discussion on the INC,PLUGINS.TXT and if we can get a consensus here will be added to post one of this thread cause now that most plugin conflicts have been resolved this makes sense to standardize at this time.
Speaking of plugin conflicts, I'm surprised no one has chimed in about plugin formats for labels, variables, an indicators starting with pluginname_XXXX. Which I thought was an outstanding idea, but needed to be better disseminated.
John, I think scripts, addons and RRCoding are just as important as plugins. I think it was last year that I started a thread on interesting coding solutions (that died a miserable death and that was your fault cause DFX just blew us all away ;) ). Maybe after we get the big stuff out of the way we can address some of the nit picky things that all of us have experienced in one way or another. Hell it took me almost a year to come up with the RRCode for DFX to clear the Album and Artist areas from the DFX main menu when FM or Internet radio is being played. That was just because the skin was so awesome in every other way, yet this was a major detraction from it looking professional. As soon as I had something working reliably, I provided it to you. Now with the 10/13/08 build it should be easier using AUDIOSOURCEID, but I've been asking for something like this for years.
OBTW, I agree with you on the PLUGINSPATH= in the RR.ini, and here's my oversimplified justification. Pluginspath and bacgroundpath make it easier for skinners to code to the standards. RR.ini is for the enduser to configure Road Runner to his system i.e., his filesystem, his directory structure, his preferences for getting RR to talk to the rest of his accessories. RR.ini should be also for GLOBAL variables that get used regardless of what skin you use. Global variable for end user setup should never be changed by a skinner, but global variables like weather. For example, I have four skins that all have four weathercities plus the gpsweathercity. When I press and hold to change the first city in one skin (because I save those variables in RR.ini) I know that when I open up another skin that first city data will be the changed data, I don't have to do it again for each individual skin.
SKIN.ini should be only for skin-specific variables, settings, etc. and setting THAT DON'T INTERFERE WITH THE OPERATION AND USE OF OTHER SKINS. I have seen some skin.ini files used to store the last zipcode used for RRGas or Movietimes, I don't remember specifically. Ideally that info should be saved in the RR.ini so if I change skins, the plugins will see the variable hasn't changed and use the data from the last request, increasing the speed of the system.
SKINPATH and its subfolders should be used for those addons, scripts, programs that, after careful consideration, have absolutely no possibility of being used by other skins.
That's the way I understood the operation of RR from its inception. This may have changed along the way, so chime in everyone and set me straight.
On a totally different topic, here's something to jumpstart the discussion on addons. Can multiple skins share games, logos, imageviewer, locker, IE radio, DeleteCurrent, Lyrics, Ratings, TaskMan, WiFiMan, etc.? These kinds of addons are just as prolific as are backgrounds.