GM.getResourceText: Difference between revisions
From GreaseSpot Wiki
Jump to navigationJump to search
m →<code>resourceName</code>: Cleaned up mini-description |
m →Examples: Neutralized example |
||
| Line 38: | Line 38: | ||
<code><pre> | <code><pre> | ||
// ==UserScript== | // ==UserScript== | ||
// @name | // @name My Script | ||
// @namespace | // @namespace <nowiki>http://www.example.com/gmscripts/</nowiki> | ||
// @description | // @description Scripting is fun | ||
// @include | // @include <nowiki>http://www.example.com/*</nowiki> | ||
// @resource | // @resource prototype http://www.example.com/prototype.js | ||
// ==/UserScript== | // ==/UserScript== | ||
/ | (function() | ||
{ | |||
// some code | |||
var myPrototype = GM_getResourceText("prototype"); | |||
// some code | |||
})(); | |||
</pre></code> | </pre></code> | ||
Revision as of 07:53, 12 December 2007
Description
This API method loads an external resource, such as an external JavaScript routine, and returns the string for use in the DOM.
Syntax
GM_getResourceText( resourceName )
- Value: Function
- Returns: String
- Compatibility: Greasemonkey 0.8.0+
Parameters Properties resourceName
- All properties are optional except resourceName.
Properties
resourceName
- Value: String
- Usage:
resourceName = "metadata-resource-name[1]";
- This value is used in retrieval of the same named resource specified in the corresponding metadata block @resource key. After it is retrieved, no formatting on the resource will occur, and it will be returned upon completion of this API method.
Examples
// ==UserScript==
// @name My Script
// @namespace http://www.example.com/gmscripts/
// @description Scripting is fun
// @include http://www.example.com/*
// @resource prototype http://www.example.com/prototype.js
// ==/UserScript==
(function()
{
// some code
var myPrototype = GM_getResourceText("prototype");
// some code
})();
Notes
[1] While the variable names here are non-semantic, it is assumed that it should be compatible with JavaScript variable naming conventions and XML/CSS naming conventions to help keep things consistent.
