Lets you control miscellaneous settings.
In order to effectively use formatting of a project with several developers it is nice to be able to only format files which have changed. Jalopy provides two standard checksums to accomplish this. These work by taking a checksum of the file and comparing it to the one found in history. If this checksum is different, the file is parsed and formatted in memory and a new checksum calculated. If the new checksum is different than the checksum for the unformatted file, it is written to disk. This stops files that have just been updated from source control from having being formatted (and time stamps updated).
To enable the history feature, select your preferred checksum method from the combo box on the left. Adler32 is faster, but CRC32 is slightly more accurate.
The history information of previous formatting runs will be saved in a file "history.dat". Since Jalopy 1.0.3, you can specify the directory where the file is actually stored. The default is to store the history file in the current profile directory.
Note that the history file will grow over time, especially if one manages several big projects which share the same profile. So the history file could become quite huge. As all history entries are read into memory at startup, it could eat up quite a bit of memory. Therefore a simple history viewer is provided which enables you to selectively remove obsolete entries if the need should arise.
View
You can use the button to display the history viewer. Entries can be selectively removed via the popup menu.
Directory
To change the directory where the history data is stored, press the button. A dialog appears that lets you enter a new directory or - in case the history directory was already changed - select one from out of the last 10 chosen history directories.
Either enter a direcory in the text field directly, or press the button to invoke a directory browser that lets you search the file system for an existing folder or create a new one.
Since 1.0.3