Enables you to keep and manage several Jalopy configurations, also called profiles. A profile stores a given set of related settings, i.e. the code convention plus assorted user-specific preferences and data like file and dialog histories.
For every profile you define, a new subdirectory is created below the main settings directory where all related files will be stored.
The list component displays all currently known profiles. Click an entry to see what actions are available. Depending on the state and type of a profile, not all actions may be available.
In Figure 2.11, "Profiles settings page" above, the active profile is selected and therefore only adding new profiles or defining aliases would be allowed. Importing and exporting is always possible.
To add a new profile click the button. A dialog will appear that lets you create the new profile.
You need to enter the profile name, might add an optional informative description and if a profile is currently selected in the profiles view, you can choose whether you want to create a nested profile by selecting the parent profile. A nested profile will automatically adapt any changes made to its parent profile(s).
Name
The profile name needs to be unique and will be used as the name of the disk folder where all profile information will be stored. Therefore, you should avoid characters that your platform does not allow to be used in file paths.
As as convenience, when invoked from within one of the supported IDE's, the dialog provides a combo box with the names of all projects currently available in the IDE that have no corresponding Jalopy profile.
Description
The optional description must be no longer than 256 characters and can be freely chosen. It will be displayed in a tool tip when the mouse is moved over an entry.
Name and description are available for inclusion in templates. See the section called "Local variables" for more information.
Parent Profile
In order to provide the ability to easily manage profiles that largely share the same settings, you can create nested profiles. A nested profile will automatically adapt any changes made to its parent profile(s).
The typcial example would be a number of different projects that should receive the same formatting style, but require different headers. In order to setup such a scenario, you would create a master profile where you configure all shared settings, and afterwards create different nested profiles for each project where you define the individual headers. Later on, if you want to apply any changes to the formatting style of all projects, you would only alter the master profile and the changes will be propagated to the nested profiles automatically.
In order to create a nested profile, simply choose the parent profile here. If you choose "None", the new profile will be created as a root profile. Please note that this option is only available when a profile is currently selected in the list view.
When you add a new profile, the settings of the currently selected profile will be used to create the new profile. If you create a nested profile, the selected profile will be the parent profile.
This feature is only available with Jalopy 1.7 or later.