X-Git-Url: http://www2.svjatoslav.eu/gitweb/?a=blobdiff_plain;f=doc%2Findex.html;h=a9ae900ef7235a1a192e33339e6a919f85d70f14;hb=375d6ff0afd27c71927296cdb9c971a5d0c85341;hp=f011ad86b9ade1cff8ed7a594eeae98dc03bd26b;hpb=3c997802712d8f3d243832840f20757f6e2567da;p=javainspect.git diff --git a/doc/index.html b/doc/index.html index f011ad8..a9ae900 100644 --- a/doc/index.html +++ b/doc/index.html @@ -2,7 +2,7 @@
-JavaInspect is a Java library that primarily uses Java reflection to -discover and visualize any part of Java program provided that -classes to be visualised are available in the classpath. +JavaInspect is a Java library/commandline utility that primarily uses +Java reflection to discover and visualize any part of Java program.
JavaInspect currently has no GUI, configuration files, embedded -scripting support, direct Maven or Ant integration. The only way to -instuct Javainspect what to do is by using its Java API. +scripting support, direct Maven or Ant integration. See usage to learn +how to instuct Javainspect what to do.
--To get JavaInspect into same classpath with your projecs I so far came -up with 2 solutions: -
- -After discovering application structure and optionally filtering out unimportant parts, JavaInspect produces GraphViz dot file that describes data to be visualized. Then launches GraphViz to generate -bitmap graph in PNG format. By default on your Desktop directory. +bitmap graph in PNG or SVG format. +
+ ++By default on your Desktop directory when operated in library mode or +current working directory when operated as standalone commandline +application.
@@ -300,12 +299,93 @@ Graph legend:
-Currently the only way to control JavaInspect is by using Java -API. Simple Java based control/configuration code needs to be written -for each project. I usually put such code into directories devoted for +JavaInspect can be controlled in 2 different ways: +
+ ++To enable commandline support, (study and) execute script: +
++commandline launcher/install ++ +
+Warning: It was tested only on Debian Stretch linux. +
+ ++Available commandline arguments: +
+
+-j (existing files)…
+ JAR file(s) to render.
+
+-n (mandatory, string)
+ Graph name.
+
+–debug
+ Show debug info.
+
+-k
+ Keep dot file.
+
+-h
+ Hide orphaned classes.
+
+-w (one to many strings)…
+ Whitelist glob(s).
+
+-b (one to many strings)…
+ Blacklist glob(s).
+
+-d (existingdirectory)
+ Target directory. Default is current directory.
+
+-t (options: png, svg)
+ Target image type. Default is: svg.
+
+Requires that classes to be visualised are available in the classpath. +
+ ++To get JavaInspect into same classpath with your projecs I so far came +up with 2 solutions: +
+ ++Simple Java based control/configuration code needs to be written for +each project. I usually put such code into directories devoted for JUnit tests. Because it needs not to be compiled/embedded into final product or project artifact I'm just willing to visualize.
@@ -352,9 +432,9 @@ files. (Default is user desktop directory)This example demonstrates generating of class graph from hand picked classes and visualizing GraphViz itself. @@ -404,9 +484,9 @@ Result:
// Create graph @@ -437,9 +517,9 @@ Result:
Declare JavaInspect as dependency:
@@ -489,10 +568,12 @@ Add Maven repository to retrieve artifact from:GraphViz - shall be installed on the computer.
@@ -507,38 +588,121 @@ On Ubuntu/Debian use:+Note: Because this is side project (and I have many of them) I can +only contribute few hours per year at average. Any help is welcome. A +LOT of cool ideas could be implemented. For intstance: +
+ +