File: olh_pluginwin.htm

package info (click to toggle)
mm3d 1.3.15-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 9,404 kB
  • sloc: cpp: 99,351; sh: 4,043; perl: 2,464; makefile: 1,318; ansic: 383; xml: 137
file content (54 lines) | stat: -rw-r--r-- 1,990 bytes parent folder | download | duplicates (2)
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
      <h1>Plugins Window</h1>

      <p>
      The <b>Plugins Window</b> shows you what plugins are installed and active.
      </p>

      <p>
      Plugins can add support for additional features, see
      <a href="olh_develop.html#plugins">Development &sect; Plugins</a>
      for details.
      </p>

      <p>
      Plugins are located in a directory on your hard drive.
      Plugins can be in subdirectories or symbolic links.
      <ul>
      <li>
      Using the Flatpak on Linux, Maverick Model 3D uses
      <code>$HOME/.var/app/moe.clover.mm3d/data/mm3d/plugins/1.3</code>.
      </li>
      <li>
      On macOS, Maverick Model 3D uses <code>$HOME/Library/Application Support/Maverick Model 3D/plugins/1.3</code>.
      </li>
      <li>
      On other Unix-like systems, Maverick Model 3D uses <code>$HOME/.mm3d/plugins/1.3</code>
      and <code>/usr/local/share/mm3d/plugins/1.3</code>, although the shared path can
      be changed at compile time.
      </li>
      <li>
      On Windows, Maverick Model 3D uses <code>%APPDATA%\Maverick Model 3D\plugins\1.3</code>
      and the <code>plugins\1.3</code> subdirectory where Maverick Model 3D was installed.
      </li>
      </ul>
      </p>


      <p>
      The main component of the plugins window is a table that contains
      a list of plugins.  Each plugin should also provide a <b>Version</b> string
      and a <b>Description</b> string.  There is also a <b>Status</b> column that tells you
      if the plugin is properly initialized and currently active. <b>Filename</b> specifies
      the full path of the plugin.
      </p>

      <p>
      All plugins can be disabled at run time by specifying <code>--no-plugins</code> 
      on the command line.  Specific plugins can be disabled by specifying
      <code>--no-plugin=<i>plugin_name</i></code> on the command line.  
      <code>--no-plugin</code> can be specified more than once.
      </p>

      <p>
      Press <b>Ok</b> to close the window.
      </p>