Settings
- If the Keep local history of changes checkbox is selected, Studio saves current state of the project when it
changes something, e.g. on saving entities or screens. Additionally, you can create history revisions by clicking on
the bookmark button in the toolbar. The list of revisions with the ability to rollback to any revision can be opened
from the recent projects list - see the button on the right side of the selected row.
The local history repository is located in the
.studio/local_history
subdirectory of the project.
- When the Ask before closing a page containing changes checkbox is set, Studio shows the warning dialog
whenever you close a page containing unsaved changes.
- When the Check compatibility between data model and database scheme checkbox is set, Studio shows a
warning whenever you start the application server and the current state of the data model differs from the
database schema.
- If the Make plural forms checkbox is selected, Studio will make plural forms of nouns according to English grammar.
- If the
Generate script name in format 'yyMMddHHmm'
checkbox is selected, Studio will add current
time to the names of generated database update scripts, which may help to ensure correct sequence of scripts
when working in a team.
- If the Repeat entity parent package for screens checkbox is selected, and an entity is located in an
additional package inside
entity
, Studio will add this package for Generic UI screens generated by
templates. For example, if the Customer
entity is inside com.company.sample.entity.crm
,
the default package for its screens will be com.company.sample.web.crm.customer
.
- If the Use underscores in generated package names checkbox is selected, package names will include underscores
separating words according to camel case in a corresponding entity name. For example, when generating screens for
the
com.company.sample.CustomerGrade
entity, the package of the screens will be com.company.sample.customer_grade
.
If the option is off, the package name will be com.company.sample.customergrade
.
- The Display XML attributes on separate lines checkbox affects XML formatting. If it is set, each
attribute of an XML element is placed on a new line. You may want to switch off this checkbox to save vertical
space. Then the XML formatter will put attributes on the new line only after exceeding the maximum line length,
specified in the Maximum XML line length field.
- The Do not delete columns started with field allows you to specify a prefix for table columns, that
should not be tracked by Studio. If you add a column to a table mapped to an entity,
and not map the column to an entity attribute, Studio will generate an update script dropping
this column. To avoid dropping, you can exclude this script on the Database scripts page, and it will not be
generated again. Alternatively, you can set a common prefix for such columns in the Do not delete columns started with
field and name the column accordingly. For example, enter
NOT_MAPPED_
in the field and name the
column NOT_MAPPED_CODE
.
- The Column length for enums with ID of String type field allows you to set a length of the database
column which is mapped to an attribute of enum type with the identifier of String type. For example, if you use
short identifiers always consisting of one character, you can set 1 in this field to save database space.
- The Default parent package name for screens field allows you to specify a default package to be used
instead of
screens
when generating a Generic UI screen from template not associated with an entity.
It is also added before the package with entity name for templates associated with an entity. For example, if
you set ui
in this field and create a blank screen, the default value for the package will be
com.company.sample.web.ui
.
- The Default access modifier sets the modifier which Studio uses when generates entity fields.
- The Instant hot deploy checkbox allows you to turn off hot deploy. If hot deployment is enabled, Studio
dynamically updates the UI of your deployed web application as you apply or save changes to views, screens,
messages or the main menu.
- You can edit Hot deploy settings to customize hot deployment directories. For example, you might want to
add folders where your web portal HTML and JavaScript files are located. When you change these files, Studio
will copy them to respective destinations inside Tomcat. So you can just reload your web portal page to view
the changes.
- The Installed plugins list shows extensions and plugins loaded by Studio from the
~/haulmont/studio/plugins
directory.
Most of the settings are stored in the studio-settings.xml
file
in the project folder. It is recommended to add this file to the version control system together with all project
sources.