-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add automatic update support #2531
Comments
@i-cant-git that doesn't automatically get triggered, only when you click it. |
Yes any implementation for this would have scheduled and manually triggered updates as an option. The point is the ability to download, check whether it's newer, then install if so. |
I shared here because #1743 is closed. |
Any updates on when this could potentially be top of the issues list(milestone/time-frame)? While GM4 is good, this is a major drawback for me in it's usability. Revisions to scripts occur quite frequently in my environment and without auto-updating(like we had in GM v3) it's tedious and can often lead to breakages. ie. When a website updates it's structure/content and the GM does not update in sync to handle the changes in the website(because you need to manually re-install it). |
I'm actively working on this; see b0b93bc . Remaining (at least):
|
Don't (auto) update a script that's been edited since install time. Refs greasemonkey#2531
There should be a (more?) progress indicator for updates. Including: the script's data should update in-place, if you click "update now" and there is indeed an update available. |
Describe `UserScriptUpdateNow`, and update it to make the caller more aware of the result. Refs greasemonkey#2531
Including one to help in testing script (auto) updating. Refs greasemonkey#2531
The vast majority of this is in the current (2018.07.25) nightly ( https://arantius.com/misc/gm-nightly/ ), the rest will be in today's. I'd appreciate any and all testing. |
I was going to ask if you wanted a tester. I’ll see if I can get the nightly release installed and get back to you Monday. Thanks. |
Just some unfiltered impressions (tried to immitate a dummy user):
|
This change has nothing to do with the install window.
You're confused. GM 4 doesn't do anything with that value. (It's still in the parser, but nothing else uses it in any way.)
Among all the rest of your comments this sounds legitimate (but it was hard to read as three seemingly-independent bullet points -- they only make sense as one unit).
Take a look at the latest nightly including work for #2728 . |
Well, as I said, these bullet points were created after clearing my brain, very nightly, unrelated, unfiltered, unsorted, pretty much of a brainstorm in the night. And as it went confusing with that failing update feature, it left only one valid point (the last one), that was not very helpful. Need time for a detailed examination... To the last item: The 07-27 (really? My previous install date was 07-28!) version is much better. Congratulations! Just one thing though: As I said, I've changed that script. If I click |
Dummy user feedback also. I know this is the initial release so this might sound overly critical, given I'm sure their is more to come. So let me start by saying thank you for adding updates back. As I called out before this is something that helps me greatly. Feedback
|
Fine, but what am I supposed to do with that? Just ignore it? You said it, so I responded.
I know. We have fewer UI options under WebExtensions. And is this really important? How would you want it to look/appear as it happens?
This is intentional. It tries to be intelligent: checking frequently when scripts are likely to have changed, and infrequently when not (based on the history of checks).
Would you mind filing this as its own issue?
Good point, will add. |
So that it will be newer than edit time, if necessary. Refs greasemonkey#2531
Allow rapid checks when each finds a new version. Continue exponentially decaying down towards more infrequent checks from ther. In addition, do fuzzing last to make a flurry of checks even less likely. (If we're shut down for a week, then every timer expires. If several find an update, they'll now each check somewhere in 3 hours +/- 15% -- not all in exactly 3 hours.) Refs greasemonkey#2531
This seems to have been working well in nightlies for a while. |
n.b.
The text was updated successfully, but these errors were encountered: