blob: aa22e31c1589a453db47e9b6795a2f5549dc4eb3 [file] [log] [blame]
<html>
<head>
<link rel="stylesheet" href="../webroot/stylesheet.css">
<link href="https://fonts.googleapis.com/css?family=PT+Sans" rel="stylesheet">
</head>
<body>
<h1>Scripts</h1>
Scripts are helpers that you want to integrate closer with your running application.
<p>
By adding locations to <i>Preferences / Scripting / Script Locations</i> contained script files get visible in the <i>Script Explorer</i> view.
</p>
<h2>Executing Scripts</h2>
You may launch scripts directly from the <i>Script Explorer</i> view by double clicking them. Further scripts can be included using the scripts: URI scheme:
<pre>include("scripts://your script");</pre>
<h2>UI Integration</h2>
Magic headers in script files allow to hook your scripts right into the UI of your running application.
You may extend view toolbars and menus as well as popup menus.
<p>
A full list of featured keywords is available on <a href="https://wiki.eclipse.org/EASE/Scripts">our Wiki</a>.
</p>
<p>
Entries in the <i>Script Explorer</i> view do provide properties which allow simpler editing of keywords.
</p>
<h2>Other Keywords</h2>
UI integration is not the only use case for keywords. They may also be used to automatically trigger scripts on certain events like resource changes, keyboard shortcuts or messages on the event bus.
<h2>Your own Keywords</h2>
Keyword support is extensible allowing to add your own keywords and event types.
</body>
</html>