That's how require works (at install time; it's a way to organize a big script into parts and/or share those parts among scripts), and that won't change, but script update checking is coming soon. Check out the beta announced yesterday. On Sep 23, 2011 5:10 PM, "Andrew Sohn" <[email protected]> wrote: > I work with a team of developers on a web application. Over time I've > written several GreaseMonkey scripts to speed up the things that I do > on a regular basis. Anyway, I've started sharing the scripts with the > rest of my team but instead of sharing the javascript I wanted to try > sharing the just the headers of the scripts and hosting the actual > javascript in a remote place to make distribution easier. example: > phpmyadmin_server_list.user.js > // ==UserScript== > // @name phpMyAdmin Server List > // @namespace ajsohn > @include our-domain/phpMyAdmin/main.php* > @require our-domain/~asohn/GreaseMonkey_Library.js > @require our-domain/~asohn/GreaseMonkey_Library/ > phpMyAdmin_Server_List.js > // ==/UserScript== > > > (if you're curious, this script mangles the server drop-down list to > prepend <options> for the database hostnames that our team's product > uses. - it's a long list. So this way the hostnames that we care about > are at the top of the list and the SysAdmins are non-the-wiser ;) ) > > > So anyway, I noticed that GreaseMonkey will go out and retrieve the > files specified by @require and store them on the local machine. > That's fine for something that doesn't change or expand it's > functionality very often (like jQuery or Prototype). I played with > @require a little bit and fixed an issue that I was seeing by > appending the @require with "?1" but that would probably have a > performance penalty if it causes GreaseMonkey goes out and retrieves > the remote files on every page (and frame) load. I thought about > handing out a batch/shell script that would remove the "cached" > versions of the remote files from each sub-directory in the gm_scripts > directory but then it's back to square one because having each team > member run a script every so often just as tedious as distributing the > library via email every so often. > > If there was a built-in "clear cache" feature for GreaseMonkey I think > it would save me a lot of grief. > Thoughts? > > -- > You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en. >
-- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
