+To use JavaInspect via Java API, no further installation is
+needed. JavaInspect will be embedded into your project as dependency.
+This is described in <a href="#orgc792989">usage via Java API</a>. It will expect GraphViz to be
+available in the system.
+</p>
+
+<p>
+To use JavaInspect as a commandline tool, JavaInspect source
+repository has to be cloned locally: See <a href="#org1f40be1">Source code</a>.
+</p>
+
+<p>
+Then study and execute installation script:
+</p>
+<pre class="example">
+commandline launcher/install
+</pre>
+
+
+<p>
+After installation, new commandline tool should be available
+</p>
+<pre class="example">
+javainspect
+</pre>
+
+
+<p>
+Quick commandline usage help can be viewed by issuing
+</p>
+<pre class="example">
+javainspect --help
+</pre>
+</div>
+</div>
+
+<div id="outline-container-orgf9f5b99" class="outline-2">
+<h2 id="orgf9f5b99"><span class="section-number-2">5.</span> Usage</h2>
+<div class="outline-text-2" id="text-5">
+<p>
+JavaInspect can be controlled in 2 different ways:
+</p>
+<ul class="org-ul">
+<li><a href="#org952985c">as standalone commandline utility</a></li>
+<li><a href="#orgc792989">as embedded Java library via Java API</a></li>
+</ul>
+</div>
+
+<div id="outline-container-org952985c" class="outline-3">
+<h3 id="org952985c"><span class="section-number-3">5.1.</span> Usage as commandline utility</h3>
+<div class="outline-text-3" id="text-5-1">
+</div>
+<div id="outline-container-org78673fb" class="outline-4">
+<h4 id="org78673fb"><span class="section-number-4">5.1.1.</span> Available commandline arguments</h4>
+<div class="outline-text-4" id="text-5-1-1">
+<p class="verse">
+-j (existing files)…<br />
+    JAR file(s) to render.<br />
+<br />
+-c (existing directories)…<br />
+    Classpath directories<br />
+<br />
+-n (string)<br />
+    Graph name. (default: "graph")<br />
+<br />
+–debug<br />
+    Show debug info.<br />
+<br />
+-h, –help<br />
+    Show commandline usage help.<br />
+<br />
+-k<br />
+    Keep dot file.<br />
+<br />
+-ho<br />
+    Hide orphaned classes.<br />
+<br />
+-w (one to many strings)…<br />
+    Whitelist glob(s).<br />
+<br />
+-b (one to many strings)…<br />
+    Blacklist glob(s).<br />
+<br />
+-r (one to many strings)…<br />
+    root class(es).<br />
+<br />
+-d (existing directory)<br />
+    Target directory. Default is current directory.<br />
+<br />
+-t (options: png, svg)<br />
+    Target image type. Default is: svg.<br />
+</p>
+</div>
+</div>
+<div id="outline-container-orgbf7fb2b" class="outline-4">
+<h4 id="orgbf7fb2b"><span class="section-number-4">5.1.2.</span> Specifying classes to render</h4>
+<div class="outline-text-4" id="text-5-1-2">
+<p>
+Normal Java application has immense complexity. In addition to code
+that was directly written by particular project developers, lots of
+functionality is typically added as frameworks or libraries to the
+project. In addition there is significant Java standard library.
+</p>
+
+<p>
+Because JavaInspect uses reflection, it does not easily distinguish
+between those. In normal situation you would rather want to visualize
+only code that was developed specifically for your project and leave
+frameworks like Spring etc. out. If you visualize all classes that are
+possibly reachable from you project, you will easily get huge and
+incomprehensible graph.
+</p>
+
+<p>
+JavaInspect can digest compiled Java classes in 2 modes:
+</p>
+<ol class="org-ol">
+<li>Provide list of Jar files. Use <b>-j</b> option.</li>
+<li>Provide list of filesystem directories that can be used as
+classpath root. Use <b>-c</b> option.</li>
+</ol>
+
+<p>
+Currently JavaInspect uses following algorithm to add classes to
+rendered graph:
+</p>
+
+<ul class="org-ul">
+<li>All classes that were found in Jar files are added to graph by default.</li>
+<li>None of the classes that were found in filesystem directories are
+added to the graph by default (unless explicitly referenced). (TODO:
+for consistency it would be better to add them too by default)</li>
+<li>If whitelist is specified (<b>-w</b> option) everything that is not
+matched by whitelist pattern(s) will be removed from the graph.</li>
+<li>If blacklist is specified (<b>-b</b> option) everything that is matched
+by blacklist pattern(s) will be removed from the graph.</li>
+<li>Root classes can be specified using <b>-r</b> option. Root classes will
+be added to the graph. JavaInspect will then try to recursively
+discover all classes that were referenced by root class and add
+those also to the graph.</li>
+</ul>
+</div>
+</div>
+</div>
+
+<div id="outline-container-orgc792989" class="outline-3">
+<h3 id="orgc792989"><span class="section-number-3">5.2.</span> Usage via Java API</h3>
+<div class="outline-text-3" id="text-5-2">
+<p>
+Requires that classes to be visualised are available in the classpath.
+</p>
+
+<p>
+To get JavaInspect into same classpath with your projecs I so far came
+up with 2 solutions:
+</p>
+
+<ol class="org-ol">
+<li>Add JavaInspect library in your project as a dependency.</li>
+
+<li>Create new Java project for the purpose visualizing your other
+projects and include JavaInspect and your projecs binary artifacts
+(Jar's) into new project classpath. Built binary Jar's (with no
+source code) are sufficient because JavaInspect operates via
+reflection.</li>
+</ol>
+
+<p>
+Simple Java based control/configuration code needs to be written for
+each project. I usually put such code into directories devoted for