Jaidyn Ann
45462ffa98
This allows easy re-use of commands, tying names to URL-regexes rather than command-strings. Much more user-friendly, I reckon! Also, now we use “$URL” instead of “%s” for URL substitution in commands. More shelly that way.
36 lines
905 B
HTML
36 lines
905 B
HTML
<!DOCTYPE html>
|
||
<html>
|
||
<head>
|
||
<meta charset="utf8">
|
||
</head>
|
||
<body>
|
||
<section>
|
||
<h3>Shell commands</h3>
|
||
<p>Add shell commands, to be executed with a page’s URL as its argument. In a command, $URL will be replaced with the target page’s URL.</p>
|
||
<table id="commandTable">
|
||
<tr>
|
||
<th>Name</th>
|
||
<th>Shell command</th>
|
||
</tr>
|
||
</table>
|
||
<button style="width: 5em;" id="save-cmd">Apply</button>
|
||
</section>
|
||
|
||
|
||
<section>
|
||
<h3>URL/Page rules</h3>
|
||
<p>Associate the above commands with URLs, based on regex rules. When a URL is tied to a command, a button will appear in context-menus and the address bar to run said command.</p>
|
||
<table id="regexTable">
|
||
<tr>
|
||
<th>URL regex</th>
|
||
<th>Shell command</th>
|
||
</tr>
|
||
</table>
|
||
<button style="width: 5em;" id="save-regex">Apply</button>
|
||
</section>
|
||
|
||
|
||
<script src="options.js"></script>
|
||
</body>
|
||
</html>
|