1

Currently I have to open it in Google Chrome from Notepad++ (CTRL+ALT+SHIFT+R) and click two buttons in Google Chrome and reload the page each time I want to get my user script loaded again in Google Chrome, how do I make this as simple as:

  1. Save the user script in Notepad++.

  2. Refresh the page in Google Chrome.

This would make testing different small changes during development much easier.

2
  • Does ctrl+shift+r work?
    – VenkatH
    Jun 9, 2012 at 20:34
  • @VenkatH: I don't see how a cache refresh would help here. Jun 9, 2012 at 20:37

1 Answer 1

1

See the "Controlling the Script and name" part of this SO answer. Once you setup your userscript as directed there, then you merely save your changed script file and hit one "Reload" link to update it in Chrome. It's much nicer than the drag and triple-click method, although you'll want to keep the extensions tab open for lots of rapid changes.

Alas, Chrome may never make it easier than that. I can't find it right now, but pretty sure I once saw a discussion where they didn't want to check extension/content-script source for updates on every page load. It would needlessly slow Chrome 99% of the time.

7
  • I don't want to surf to the extensions, scroll till I finally find the extension somewhere and then click the reload, that's even harder than the Notepad --> Google Chrome sequence. Jun 9, 2012 at 21:31
  • Then you could compile your own version of Chrome that checked extension files for updates at every (non cached) page load. ;) Sorry, that's the best Chrome allows for now. And no, my method is not hard at all in practice... Ctrl-S, Alt-tab(s), click, F5. Bada-bing, less than 1 second total, and only one click needed (even that can be done via the keyboard). Jun 9, 2012 at 21:33
  • So, doing a cache refresh would reload the unpacked extension? Jun 9, 2012 at 21:34
  • Only, in your custom Chrome build! That was a hypothetical scenario were you compiled your own Chrome browser. Jun 9, 2012 at 21:37
  • Okay, then this is the fastest Chrome way to do it if I keep the Extensions tab open. Slowing down Chrome by 99% is a lie because you can monitor file changes without any cost by subscribing to I/O events. I might end up writing a script that will automatically click the two buttons in Chrome in the end... Jun 9, 2012 at 21:41

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .