Development/Tutorials/Plasma4/JavaScript/API-Extensions: Difference between revisions
Neverendingo (talk | contribs) m (Text replace - "<code ini>" to "<syntaxhighlight lang="ini">") |
m (D ed moved page Development/Tutorials/Plasma/JavaScript/API-Extensions to Development/Tutorials/Plasma4/JavaScript/API-Extensions) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 7: | Line 7: | ||
X-Plasma-RequiredExtensions=FileDialog,MyCustomQScriptExtension | X-Plasma-RequiredExtensions=FileDialog,MyCustomQScriptExtension | ||
X-Plasma-OptionalExtensions=LaunchApp,HTTP | X-Plasma-OptionalExtensions=LaunchApp,HTTP | ||
</ | </syntaxhighlight> | ||
The Simplified Javascript Engine then decides if the widget will actually get that extension or not. Failure to load a required extension will result in script execution being aborted. | The Simplified Javascript Engine then decides if the widget will actually get that extension or not. Failure to load a required extension will result in script execution being aborted. | ||
Latest revision as of 23:27, 11 September 2014
Using Extensions
An API extension is a security controlled set of functions and objects that are loaded on demand. These extensions are requested by the widget by listing the required and the optional extensions (if any) it wants loaded in its metadata.desktop file. This way, even prior to the widget being loaded, Plasma can know what it will want.
Required extensions are requested using the X-Plasma-RequiredExtensions key, and optional extensions with the X-Plasma-OptionalExtensions. For example:
X-Plasma-RequiredExtensions=FileDialog,MyCustomQScriptExtension
X-Plasma-OptionalExtensions=LaunchApp,HTTP
The Simplified Javascript Engine then decides if the widget will actually get that extension or not. Failure to load a required extension will result in script execution being aborted.