Thank you so much for updating Greasemonkey! I'm very happy you got it to work. Now I can stay with Firefox. I've successfully migrated my first script to the new version.
Observations: 1. As mentioned elsewhere, it took me quite a while to find out that there is no way to create a new script. I managed to install a random script from the Internet and copy-paste my script into it, as I see you recommend as well. 2. I'm not a programmer, so perhaps I'm stupid; but at first it wasn't clear to me that the polyfill thingy was only for backwards compatibility, not forward. After reading the blog updates, I didn't know I had to actually change e.g. GM_xmlhttpRequest into GM.xmlHttpRequest all over the script. Once I figured that out, it worked! Yay. 3. I'm still getting a rather cryptic error message in the web console (control-J): > <unavailable> > By the way, the reference (on the same line on the right side) is to something like "name-of-script:1644". When I click on that, a new tab opens on the address "view-source:user-script:name-of-script". Firefox says it cannot handle the address and gives some sort of error message. But that was probably to be expected; I read somewhere that this part was not finished yet. But the error message itself, what is it trying to tell me? The script just works. Thank you again! On Friday, 3 November 2017 17:05:50 UTC+1, Anthony Lieuallen wrote: > > On Fri, Nov 3, 2017 at 11:57 AM, Smylers <[email protected] <javascript:> > > wrote: > >> How to add my script was baffling. The blog posts mention that only the >> built-in editor is available now, not editing files directly on the >> file-system. So I spent quite some time looking for how to open the >> built-in editor, or a ‘new user script’ menu entry or similar. >> > > The "new script" feature is one of the many things that didn't make the > cut for the first version, it will come. For now as a temporary dirty > workaround: Just install (from the web) any script. Then edit it, replace > the whole thing to become what you want it to be. > > >> In the process of not finding that, I stumbled upon the ‘Get User >> Scripts’ menu item. That took me to a page whose first entry says that >> GitHub's Gist service can be used for hosting user scripts, so I pasted my >> script in there and went to the raw URL. The raw script was displayed in >> the browser, but it still wasn't clear what the process should be for >> getting it into Greasemonkey — I tried dragging the URL icon onto the >> Greasemonkey icon, and all sorts of things! >> > > Oops! I'm working on updating the wiki today. You got hit by #2631, > which you mention eventually finding. > > >> But it was far from clear from either the ‘user’ or ‘script author’ blog >> posts that that was what was required — probably cos I'm neither a user of >> publicly posted scripts nor an author of one, so the whole ‘hosting’ side >> was new to me. >> > > Yeah, you're probably not a typical user. Firefox 57 was a hard deadline > -- I wanted something that partially works rather than nothing at all. > > >> Seeking help on what was going on led me to this mailing list, and >> further down this thread somebody linked to a GitHub issue. Learning of the >> issues list, a quick search revealed the following issue, which explains >> why Gist no longer works for install: >> https://github.com/greasemonkey/greasemonkey/issues/2631 >> >> So I think the biggest problem is that the in-app ‘Get User Scripts’ link >> goes to a page which recommends a service that no longer works. >> > > I'll make sure to take that into account as I'm updating the documentation > in the wiki, thanks. > -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
