JALOPY | Java Source Code Formatter Beautifier Pretty Printer
Overview • Download • Documentation • Plug-ins • Links • Contact
Features | History | Manual | FAQ | Javadoc
This page generated: June 8 2004
Chapter 4. Settings
Prev | Part I. Jalopy core | Next
## Chapter 4. Settings Provides a detailed discussion of all available settings to configure Jalopy. Jalopy stores all settings as files inside its Settings directory (or subdirectories thereof). This directory is located in the user home directory (`$HOME/.jalopy`). A graphical user interface is provided to easily configure the settings. Please refer to the individual Plug-in chapters in Part II, “Plug-ins” for information on how to display it from within the Plug-in you received. ## 4.1. General Jalopy stores its settings in a binary file `$HOME/.jalopy/`PROJECT_DIR`/preferences.dat`. However you can import/export your settings in both the binary, and a textual XML format. A group of settings forms a code convention. ### 4.1.1. Convention Lets you name a group of settings, a code convention. Name The name of the code convention. The name must be no longer than 10 characters. Description Stores a short description for the code convention. ### 4.1.2. Compliance Lets you specify whether Java sources should be treated as JDK 1.3 or as JDK 1.4 compatible. The latter means `assert` will be recognized as a reserved keyword. Source compatibility Lets you choose the JDK version to use for source compatibility. ### 4.1.3. Import/Export Use the Import... and Export... buttons to import an already-saved code convention, or export your current settings as a new code convention. You can choose between the binary `.jal` format or an XML representation. Jalopy is able to import settings from both local and distributed locations. Just specify a valid Internet address (either starting with http:// or www.) for the latter. Jalopy will then attempt to synchronize its settings with the given url on every invocation. That way it is easy to share a single code convention across a group of developers. Please note that versions prior to 1.0b8 stored the backup directory always as an absolute file. Therefore after importing a code convention, you should check whether this directory points to your preferred backup directory. This advice holds true even for later versions in case you've changed the default backup directory. However if the backup directory setting is left untouched, the directory is stored relative to the Jalopy settings directory. This way you can savely share your code convention across different systems and platforms.
Prev | Up | Next
Chapter 3. Usage | Home | 4.2. Projects
to top