comparison develop.html @ 37:b9ecf03a2bce website

* link to mtp2, slight rearrangement

       <li><a href="http://vamp-plugins.org/wiki/">Wiki</a></li>
       </ul></div>
 
       <h2 id="firstpara">Developing Vamp plugins and hosts</h2>
 
-	<p><i>Hosted by <a href="http://sourceforge.net/projects/vamp/"><img align="center"
-	      src="http://sourceforge.net/sflogo.php?group_id=192001&type=1"
-width="88" height="31" border="0" alt="SourceForge.net Logo"/></a></i></p>
-
       <p>Vamp is an easy system to develop plugins for.  It has
       a standard cross-platform SDK which includes API documentation,
       example plugins, ready-to-use C++ base classes, the C API
       header, and a test host.</p>
 
-      <p>The formal Vamp API is defined in C for the greatest level of
-      binary compatibility.  However, plugins and hosts are strongly
-      encouraged to make use of the set of C++ base classes provided.
-      This is particularly advisable since the values returned by a
-      plugin may have relatively complex structures.</p>
+      <p>Vamp plugins use a C binary interface for the greatest level
+      of binary compatibility.  However, plugins and hosts are
+      strongly encouraged to make use of the set of C++ base classes
+      provided in the SDK.</p>
 
       <ul><li>Download the <b>Vamp plugin SDK</b> (<b><i>new!</i></b> version 2.1):
+
+	<a href="http://sourceforge.net/projects/vamp/"><img style="float:right"
+	      src="http://sourceforge.net/sflogo.php?group_id=192001&type=1"
+width="88" height="31" border="0" alt="SourceForge.net Logo"/></a>
 
       <ul><li>The development headers and source code: <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1.tar.gz">Gzipped tar file</a> or <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1.zip">ZIP file</a> (the contents are identical).</li>
 
       <li>Pre-compiled library and host binaries for <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1-binaries-win32-mingw.zip">Windows (MinGW)</a>, <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1-staticlibs-win32-msvc.zip">Windows (MSVC: static libraries only)</a>, <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1-binaries-osx-universal.tar.gz">OS/X (universal)</a>, <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1-binaries-i686-linux.tar.gz">32-bit Linux</a>, <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1-binaries-amd64-linux.tar.gz">64-bit Linux</a>, and <a href="http://downloads.sourceforge.net/vamp/vamp-plugin-sdk-2.1-binaries-i686-solaris.tar.gz">32-bit x86 Solaris</a>.</li>
 

       <ul>
 
       <li>Read the Vamp plugin SDK <a href="guide.pdf">Programmers
       Guide</a>.</li>
 
-      <li>Read a <a href="http://vamp-plugins.org/wiki/mtp1">tutorial on building a new plugin</a> using OS/X command-line tools.</li>
+      <li>Read a tutorial on building a new plugin: <a href="http://vamp-plugins.org/wiki/mtp1">using OS/X command-line tools</a> or <a href="http://vamp-plugins.org/wiki/mtp2">using Visual C++ on Windows</a>.</li>
 
       <li>Read <a href="vamp-programmer-presentation.pdf">a presentation</a> about the principles of Vamp plugins for
       potential developers.</li>
 
       <li><a href="code-doc/index.html">Read the API documentation online</a>.  Your plugins will normally derive from <a href="code-doc/classVamp_1_1Plugin.html">the Vamp::Plugin class</a>.</li>