
JavaArt Chapter 4. Visualization with Whorld

From the website:

  Killer Game Programming in Java
  http://fivedots.coe.psu.ac.th/~ad/jg

  Dr. Andrew Davison
  Dept. of Computer Engineering
  Prince of Songkla University
  Hat yai, Songkhla 90112, Thailand
  E-mail: ad@fivedots.coe.psu.ac.th


If you use this code, please mention my name, and include a link
to the website.

Thanks,
  Andrew

============================

The tracer application consists of 8 Java files:

   * MIDIInfo.java
         - for listing MIDI device information

   * SendParam.java
         - for sending a single parameter value to Whorld

   * WhorldTrace.java, StreamRedirecter.java, WhorldEvents.java,
     Visualizer.java, MethodVisual.java, WParams.java
         - the WhorldTrace application

There are 2 test applications for the tracer:

  * BusyProg.java
  * Comparison.java


There are 2 batch files:

  * compile.bat
  * runTrace.bat
     - they both assume that tools.jar is in
           c:\Program Files\Java\jdk1.6.0_10\lib\


----------------------------
Other Tools Required:

This example utilizes:

   * the LoopBe1 virtual MIDI driver (http://www.nerds.de/en/loopbe1.html)

   * the Whorld visualizer (http://www.churchofeuthanasia.org/whorld/)
       - configure it to use the LoopBe1 Internal MIDI as input
           via Options | MIDI tab

----------------------------
Compilation:

  > compile *.java

The compilation of MIDIInfo, SendParam, and the test applications 
can use javac if you like:

  > javac MIDIInfo.java

  > javac SendParam.java

  > javac BusyProg.java
  > javac Comparison.java


----------------------------
Execution of MIDIInfo:

  > java MIDIInfo

----------------------------
Execution of SendParam:

  > java SendParam <parameter name> <byte value>
e.g.
 > java SendParam rotateSpeed 51
      - LoopBe1 must be installed, and be the input for Whorld;
      - Whorld should be running so the visualization can be shown

or
 > java SendParam
      - it lists all the parameter names that the program recognizes

----------------------------
Execution of WhorldTrace:

  > runTrace <java-file-to-be-traced>

e.g.
  > runTrace BusyProg
or
  > runTrace Comparison
      - LoopBe1 must be installed, and be the input for Whorld;
      - Whorld should be running so the visualization can be shown


Note: you can also run the test applications directly (but they're
not that interesting):

  > java BusyProg
or
  > java Comparison

---------
Last updated: 11th April 2009
