10.02.2013 Views

SlickEdit User Guide

SlickEdit User Guide

SlickEdit User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

JAVA<br />

This tab provides the following fields and options:<br />

• Enable Live Errors - When selected, the Live Errors feature is activated. This setting is checked<br />

by default if <strong>SlickEdit</strong> has detected a valid JDK 6, or compatible, installation on your system, the<br />

first time a Java project is opened. For some coding, you may want to disable Live Errors since it<br />

will point out all syntax errors, which are common in incomplete code.<br />

After activating Live Errors, you can use the rte_next_error command to jump through the live<br />

errors in the current file. Bind this command to a key sequence for more efficiency.<br />

NOTES<br />

• For Java Live Errors to work, you must have the full JDK downloaded and installed from<br />

Sun, and you must specify the root of the JDK installation in the JDK installation directory<br />

field of the Java Options dialog (Build > Java Options), unless it is automatically detected<br />

upon startup. There is no requirement that you build your code with JDK 6, only that it is<br />

available to Live Errors.<br />

• If you have Java Live Errors running and wish to specify a different JDK 6 (or compatible<br />

JDK) root, after changing the JDK path on the Java Options dialog, you must restart<br />

<strong>SlickEdit</strong>.<br />

• In order to boost performance, Java Live Errors generates .class files as you code. These<br />

files are stored in the java_rte_classes subdirectory of your config. You can remove these<br />

files, but they will be rebuilt the next time Java Live Errors is invoked.<br />

• To specify the source compliance level, use the Source Compliance level setting on the<br />

Compiler Tab.<br />

368 <strong>SlickEdit</strong>® <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!