More Than Just an Obfuscator, It's an Advanced Optimizer, Size Reducer and Packaging System
Anyone who has ever done programming knows the value of correct, efficient code. Traditionally, an optimizer is used to increase code performance. Optimizing tools for Java have been up until now immature at best. DashO-Pro implements many standard optimizing transforms unavailable in today's Java compilers, as well as some new transforms targeted specifically for Java bytecode.

One classic optimization is dead code elimination. DashO-Pro takes this to the nth degree by removing all unused information in your program. preEmptive Solutions has provided the following sample code to demonstrate DashO-Pro's removal techniques:

class MyClass {
int Z;
public static void main(String args[]) {
System.out.println("Hello World");
}

public void doesNothing() {
Z = 5;
OtherClass X = new OtherClass();
X.doOtherThings();
}
}

In this example, DashO-Pro's algorithms detect that the "doesNothing" method is never called: therefore, it is removed along with "OtherClass" and the "Z" variable. DashO-Pro's output only includes the absolute minimum set of classes, methods and fields required by your application. Your code size is minimized, often a desired feature for applets and other code that needs to move around the network.

Using DashO-Pro
DashO-Pro can be run as a command line or GUI application. When running as a command line program there are five runtime options that can be used with DashO-Pro:
1. -f :force execution. This option, as the name suggests, forces execution, even when your application uses dynamic class loading (e.g,. by using the Class forName method). To use this option, it is necessary to specify all dynamically loaded classes in the configuration file; alternatively, you may allow DashO-Pro to automatically detect possible dynamically loaded classes.
2. -v :verbose output. When this option is used information is given about the progress of the execution.
3. -i :investigate only. This option tells DashO-Pro not to create any disk files. A report will be generated which specifies the candidates for removal.
4. -q :run quietly. In this mode, DashO-Pro runs completely without printed output. Use this option for inclusion into application build sequences. The verbose option will be overridden here.
5. : configuration file. This allows the naming of a specific configuration file, which is required for running DashO-Pro. This is a handy option when using multiple, tailor-made configurations in DashO-Pro. Trigger methods are not entered on the command line, as they must be included in configuration file.

When using the GUI, it is not necessary to write a configuration file, as the GUI is really a front end to the configuration file. The interface is initiated by running the DashO-ProGui class from the jar file. The Windows enthusiast will be delighted to know that double clicking the icon will run the interface. I found the GUI to be well laid out and a snap to move around in.

DashO-Pro's triple feature of optimization, obfuscation and compression makes it an extremely valuable tool in the professional Java developer's bag of tricks. If you have a need to streamline and hide your code, it's a must have!