2009-03-31, 20:35
Seriously, there's no need to do it as separated version, you can easily adapt it... I don't remember in which plugin I saw this and I'm not at my HTPC at the moment, so can't look if I have it there, but you just need to create some variable your self and check if special exists, if it does, use it, if not, don't. Then use your variable across the script instead of P:// or special://. There, the script will work for anyone, no matter which build they are using.
I can't test the plugin right now for the obvious reasons but I'm not sure the plugin will work because special:// points to the correct user folder, where the user is saving their settings and stuff, P:// does not (as far as I know). If someone, like me, prefers to have everything in the user folder (where it belongs) it probably won't work. But I don't know exactly how you are using paths in your script, so I may be wrong...
Maybe someone else can test this.
I can't test the plugin right now for the obvious reasons but I'm not sure the plugin will work because special:// points to the correct user folder, where the user is saving their settings and stuff, P:// does not (as far as I know). If someone, like me, prefers to have everything in the user folder (where it belongs) it probably won't work. But I don't know exactly how you are using paths in your script, so I may be wrong...
Maybe someone else can test this.