|
|
Jesse, Can you provide an upload link for Scriptwrights to upload previous versions? I have a few previous revisions I'd like to put up for history. Maybe a form to upload the file and a date-field to indicate when it was originally uploaded? (That is unless you have all the previously uploaded files, but are yet to be associated.) Also, on the 'Versions' page I have a few ideas. First, show the current version at the top of the list. Then, what do you think about adding a checkbox next to each revision so one could check the differences between revision A & revision F? Thanks!
|
|
|
how about the ability to delete previous versions? sometimes, I'll update my script, and then seconds later, someone suggests something or I'll add something I forgot about, creating a hunk of versions, when it's really just one new version. |
|
|
I would like to see the diffs before saving (making public) an updated script... |
|
|
@QP: You beat me to my requests ... I had to delete them as I read over the previous posts. @avg / @znerp / @Jesse: It would be nice to be able to delete previous versions. To head off abuse, limit deletions to revisions that nobody ever installed. @GIJoe: I like your "preview-by-diff" idea; it would have helped me find a bug that forced me to re-post only a few minutes after the previous update. ... then again, if I could delete it as noted above, it wouldn't be such a problem. |
|
|
Two suggestions:
|
|
|
Hi, anyone can inform what's the GMT used by the server to define those times? I think I may need to know for the updater, not sure though... thanks :) |
|
|
I plan to rework the upload/update flow soon. Goals include adding comments to revisions, previewing the changes before saving, requiring a description/summary before it is shown in public indexes, and more. It will be in phases so we can talk through the issues as it gets implemented. |
|
|
It would be also nice to have a beta version, just to do some install test before release it. |
|
|
Hi Jesse, most of the scriptwrighters keep a script's version log, it would be nice if it can be joined together with the script's versions. Moreover it would be very nice if all the script's versions with the same @version meta tag were together grouped. |
|
|
Sometimes I see code to be forked, and today I found a script that was blatantly stolen from me with one string translated into another language, took some time to spot the differences. So I would request a way to diff two different scripts by script id and version. |
|
|
@PhotodeusWhy not download those 2 and use a program for that. I don't see a point for this suggestion. |
|
|
Yea... What's the point in having automated tools to do the work for me when I can do it by hand!
Of course I used a program to compare the script. That's what I've done so far and it's annoying. |
|
|
It would be good if on the screen showing the different revisions it showed the script's version from the metadata. This would help people know which the major changes are. I would also love to do difs between scripts. |
|
|
Hi!
|
|
|
I want that too, but in the mean time: Userscripts : Script Version by w35l3y. |
|
|
Please update this great script as it hasn't worked for quite some time now.
|
|
|
Yes :) please update
|
|
|
I'd really like to be able to delete versions. I read about the security risks, but I don't think it's that big a problem. The ability to go back and identify the "evil" version won't really help the people who installed it. I'd use it for removing similar versions (e.g. I changed the wording of something, but no functional code.) and also for removing accidental updates. Last night I managed to paste in the wrong script, resulting in quite a mess. I'd like to be able to remove those, since it's not even the right script. |
|
|
Thlayli wrote: Having the malicious versions available lets us identify a malicious user and delete their account. |
|
|
Having the malicious versions available lets us identify a malicious user and delete their account. Then versions should be able to be disabled for installation if it was a mistake, but still be readable so users can identify them as malicious or not. |
|
|
RunningBlind wrote: I agree and I even think you should be able to disable the current version and I think Jesse said that he would implement that awhile back. |
|
|
Userscripts : Script Version really is useful, as already pointed out by a couple people in this thread, but are there any plans to include that script's features server side? It would be nice to see that info from any computer as well as for the versions I released before installing that script. It would also be nice to see a little graph of installs over time, but I guess the historical information required for this might not be available. |
|
|
I'd like a possibility to remove previos versions of my scripts, because I'm planning to obfuscate my scripts' code, and this makes no sense if you can watch the previous versions. UPDATE: As I see, someone has already requested this feature. You could of course keep the versions on the server to identify malicios users but just make them unavailable for others. |
|
|
eWolf wrote: How do you expect your users to trust your script if you obfuscate it? |
|
|
I didn't read the whole topic, but what's about a "Changelog"? Everytime you change a script, you can add some information, that will be displayed. Like this:
Changelog:
|