1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
<page xmlns="http://projectmallard.org/1.0/"
type="guide"
id="pluginmanager2">
<info>
<link type="guide" xref="index#extra"/>
<desc>User plugin installation</desc>
</info>
<title>Plugin Manager 2</title>
<p>As of release 2.1.8 there is a plugin manager. It's available as
feature extension. Once acticated (after a restart) it brings up a
new <key>📦 Add</key> tab in the configuration window.</p>
<p><media type="image" src="img/pluginmanager2.png"
mime="image/png">Install dialog for user plugins</media></p>
<p>You can scan for available/new plugins there. And have them
downloaded right away. New plugins are just downloaded, not
implictly enabled. Reopen the config dialog to see them in the
regular lists.</p>
<section id="configuration">
<title>Configuration</title>
<p>Alternative download repositories may be configured. (Little
practical value at the moment and foreseeable future.)</p>
<p>And you can let the plugin manager handle regular plugins as
well. After reconfiguring existing channel plugins, they get
automatically run, or disabled in the user interface (without
any restart). Which won't work for most feature/core plugins.</p>
</section>
</page>
|
>
>
|
>
>
|
|
>
|
>
|
|
|
>
>
|
|
>
>
>
>
>
>
>
>
|
>
>
>
>
>
>
>
>
|
1
2
3
4
5
6
7
8
9
10
11
12
13
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
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
<page xmlns="http://projectmallard.org/1.0/"
type="guide"
id="pluginmanager2">
<info>
<link type="guide" xref="index#extra"/>
<link type="topic" xref="configuration#plugins"/>
<desc>User plugin installation</desc>
</info>
<title>Plugin Manager 2</title>
<p>For updating or installing new plugins (extra channels or
features), there's a user plugin manager. It's available as
feature extension itself.</p>
<p>Once acticated (after a restart) it brings up a new <key>📦
Add</key> tab in the configuration window.</p>
<p><media type="image" src="img/pluginmanager2.png"
mime="image/png">Install dialog for user plugins</media></p>
<p>You can scan for available/new plugins there. And have them
downloaded right away. New plugins are just downloaded, not
implictly enabled. Reopen the config dialog to see them in the
regular <key>📻 Channels</key> or <key>🔌 Feature</key> tabs, and
then enable them.</p>
<section id="configuration">
<title>Configuration</title>
<list>
<item><p>Alternative download repositories may be configured. (Little
practical value at the moment.)</p></item>
<item><p>And you can let the plugin manager handle autoactivation
of changed plugin states.</p>
<list>
<item><p>After reconfiguring existing channel plugins, they get
automatically instantiated or disabled in the user interface.
(Which avoids the usual restart).</p></item>
<item><p>This currently doesn't work with feature/core
plugins. Plugin deactivation is mostly visual, but does not undo
menu extensions or undefine callback hooks.</p></item>
</list>
</item>
</list>
</section>
<section id="configuration">
<title>User plugins</title>
<p>Downloaded plugins are stored in <file>~/.config/streamtuner2/plugins</file>.
To remove them, delete the individual *.py files there manually.</p>
<note style="bug"><p>Currently system-installed core plugins take
precedence over downloaded updates.</p>
<p>And you'll have to take care to eventually refresh/delete outdated user plugins,
whenever you install a newer Streamtuner2 version.</p></note>
</section>
</page>
|