First stab a major manual restructuring.

[ardour-manual-diverged] / _manual / 11_working-with-plugins / 05_working-with-ardour-built-plugin-editors.html

diff --git a/_manual/11_working-with-plugins/05_working-with-ardour-built-plugin-editors.html b/_manual/11_working-with-plugins/05_working-with-ardour-built-plugin-editors.html
deleted file mode 100644 (file)
index 392ac87..0000000
--- a/_manual/11_working-with-plugins/05_working-with-ardour-built-plugin-editors.html
+++ /dev/null
@@ -1,33 +0,0 @@
----
-layout: default
-title: Working with Ardour-built Plugin Editors
----                        
-
-<p class="fixme">This section needs expansion, and at least one image</p>
-
-<p>
-  To view a plugin editor, double-click on the plugin within the 
-  <a href="/working-with-plugins/processor-box">processor box</a>. 
-  A new window will appear showing the editor/GUI for the plugin.
-</p>  
-
-<p>
-  If a plugin does not have its own GUI, Ardour will construct a
-  <dfn>generic plugin editor</dfn> from a small set of common control 
-  elements. Ardour will do this even for plugins that have their 
-  own, if <kbd class="menu">Edit &gt; Preferences &gt; 
-  GUI &gt; Use Plugins' own interface instead of Ardour's</kbd> is disabled.
-</p>
-
-<p>
-  The generic UI can be temporarily switched to by context-clicking on 
-  a processor and selecting <kbd
-  class="menu">Edit with generic controls</kbd>. This will be necessary to
-  access the <a href="/automation">plugin automation controls</a>.
-</p>
-
-<p>
-  In the generic UI, any controller can be reset to its default by
-  <kbd class="mod3 mouse">Left</kbd>-clicking on it.
-</p>
-