You can place your JS somewhere on the net. @require
http://www.prionhkiyt.com/js/prionhkiyt.lib-1.0.0.js then use that
as a require.
I don't see why this would not work.
--
--
ℱin del ℳensaje.
I don't see why this would not work.
-- Klaus Johannes Rusch klaus...@atmedia.net http://klausrusch.atmedia.net/
On 20.04.2012 15:09, Anthony Lieuallen wrote:On Fri, Apr 20, 2012 at 7:45 AM, Tei <oscar...@gmail.com> wrote:
I don't see why this would not work.
The key word is "local". As you pointed out, @requires need to come from the internet. (There's a longer answer, but this is the simple easy one.)
Loading a library javascript file from a file:/// URL works perfectly fine for me:
// ==UserScript==
// @name test script
// @namespace http://www.example.com/
// @description test script
// @include *
// @require file:///path/to/test2.user.js
// ==/UserScript==
On 4/20/2012 8:52 AM, Klaus Johannes Rusch wrote:Loading a library javascript file from a file:/// URL works perfectly fine for me:
Doesn't that require altering the "fileIsGreaseable" browser setting?
Doesn't that require altering the "fileIsGreaseable" browser setting?
On Fri, Apr 20, 2012 at 12:54 PM, Matt Sargent <matt.s...@locusprime.net> wrote:
Doesn't that require altering the "fileIsGreaseable" browser setting?
To download any file (require, resource, icon) along with a script it has to be greaseable -- or come from the same scheme as the script itself.