quote:
Originally posted by markee
This would be extremely useful for someone who gets a lot of scripts to have a look at just the methods used before deciding what to do with the script, people like me. I know I could always dismantle the script and look at the *.js file but I couldn't be bothered and just install it instead.
I totally agree with this; you took the words right of my mouth...
...because:
quote:
Originally posted by Patchou
if you really want to check the scirpt before importing it, just rename the .plsc file to .zip and extract the files 
.
If you're dealing with hundreds of scripts and very regulary download scripts to check them out, doing this manually is very time consuming, slows down stuff and actually a hassle. Also, many times, checking how the ScriptInfo.xml is viewed thru the importer is part of that 'script-investigation'...
Also, you might wanna check out a script later on too. If you don't want to run a script, you either need to start the script extracting all over again, or you manually need to add it to the registry.
It is indeed a very big hassle actually and something I cursed upon regulary too (if I may say so)...
...but:
quote:
Originally posted by alexp2_ad
this would confuse a lot of people who haven't used scripts before.
[SNIPPED]
I suppose optional would be OK, but I like the current system best.
is of course very understandable and I agree with this too...
Hence why I like to suggest a
hidden registry option for it, so that only the people who actually are used to scripts and know what they are doing, can turn this off.
In that way, people who aren't used to scripts, who are new to scripts and all the other 'beginners' would still see the normal default way as it is now...
/ 
