To access the preferences page select Window->Preferences (or Eclipse-Preferences on Mac OS X) then expand the AgileJ item.
You can choose between Alphabetical, which arranges fields and methods in alphabetical order and Declared which keeps the members in the order in which they were declared in the source code.
You can choose between Java and UML, where Java means the format
type name
and UML means the format
name : type
You can choose which font is used to draw text on all class diagrams. Click the Change button to pick a font.
The point of the default folder is to save time with the creation of new diagrams. While diagram files can be placed anywhere in the open projects in the workspace you may find it easier to keep them all in one single folder, in which case that folder is specified here.
Selection colors give greater contrast which usually results in a clearer printout. Turn this option off if you want classes to appear on the printout as selected on screen at the time the print was created.
If your mouse has a wheel, then it can be faster to navigate around diagrams if you assign the mouse wheel to zooming in and out. However, selecting this option hides the scrollbars, so to scroll around the diagram it is necessary to use the hand scroll mode.
The way Java elements are drawn on the class diagrams is controlled by configuration information loaded from an xml file. There is a factory configuration file which AgileJ loads by default when the Custom Configuration File field is empty. If, however, you have created your own project-specific configuration file then enter it's location in this field.
Before a large number of classes are added to a diagram, a warning dialog offers to filter the selection of classes to be added. The Addition Threshold is the number of classes above which this warning appears.
This value throttles the number of classes which may be added to a class diagram in one operation. Without this constraint it is easy to drop, say, a single jar file containing thousands of classes onto a class diagram. This would take minutes to complete and be unlikely to result in a visually meaningful class diagram. The default is 200; meaning that any drop which contains in excess of 200 types will be rejected.
This percentage value controls the magnification applied to all diagrams as they are exported to any of the four supported image formats. The range is 10% to 200%;
There are seven grades of license key:
default (no license) |
non-commercial |
evaluation |
ide-single |
ide-multi |
single |
multi |
|
---|---|---|---|---|---|---|---|
View class diagrams (read only) in the Eclipse IDE |
Y |
Y |
Y |
Y |
Y |
Y |
Y |
Create and edit class diagrams in the IDE |
N |
Y |
Y |
Y |
Y |
Y |
Y |
Canvas without watermark |
N |
Y |
N |
Y |
Y |
Y |
Y |
Can create, run and rerun batches |
N |
Y |
Y |
N |
N |
Y |
Y |
Can view batch output by browser |
Y |
Y |
Y |
Y |
Y |
Y |
Y |
Floating License * |
n/a |
Y |
N |
N |
Y |
N |
Y |
Expiry |
never |
12 months |
30 days |
10 years |
10 years |
10 yrs |
10yrs |
Needs the batch optional feature installed |
N |
Y |
Y |
N |
N |
Y |
Y |
* Floating licenses are licenses which may be shared by users in a team where the team size has been stated at the time of creating the license.
When AgileJ StructureViews opens an editor it checks the validity of the current license and prompts for a new license if the license has expired. To apply an upgrade to an existing valid license, paste it into the license key field. To check information about the license, select the Help-About AgileJ StructureViews menu.