14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
+
-
-
+
+
+
-
+
-
|
"configwin": true,
"continuous_record": false,
"delicast": true,
* Plugins are scanned for meta infos on each startup (there isn't too many), and instantiated according to config table.
* Hooks/`type:` are not used much. Instead class types are used implicitly, or plugins register themselves with the main application.
* `config:` options show up in a neat combined settings window, defaults are applied on startup / to the conf{} dict.
* Defines an [extra `arg:` attribute](http://fossil.include-once.org/streamtuner2/wiki/plugin+meta+data) for the `config:` list.
## Powershell: [Clicky](http://fossil.include-once.org/clickycoloury/)
* Albeit has a [full parser](http://fossil.include-once.org/clickycoloury/artifact/fb2017bd6797bf6c2c9df6c92966632c7262cb61), only the config options are fully used.
* `type:` covers a few magic values (init*, inline, cli, …)
* Has a [full parser](http://fossil.include-once.org/clickycoloury/artifact/fb2017bd6797bf6c2c9df6c92966632c7262cb61), and utilizes both config options and other meta fields at runtime..
* `type:` covers a couple of magic values (init*, inline, cli, window, …) deciding on when to run/inline a script.
* But primarily the `category:` is used for UI hookup (menu structuring). Which is one of the more basic uses for plugin meta data.
* Defines a [bunch of custom fields](http://fossil.include-once.org/clickycoloury/wiki/plugin+meta+data) like `hidden:`, `nomenu:`, `vars:` (like config struct), `key:` and `shortcut:`, which avoids lots of code duplication for plugins/scripts.
* There's no plugin activation states as such, all scripts are "loaded" all the time.
* But there's no plugin activation states as such, all scripts are "loaded" all the time. Though there's a basic Plugin Manager now.
* Albeit there's a basic Plugin Manager now.
|