Configuration and Rules files

Configuration file

After closing InDesign for the first time with the Naviga Templates plugins installed a configuration file called "elastic-layout.config" will be created. Among other things it includes the registered license key.

Here is an example of a configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<config creator="lib-newspilot" date="2020-04-17 12:03:26" version="1.1">
  <config-map>
    <setting key="elastic-ui.disable.licence.propmt">
      <value>
        <bool>false</bool>
      </value>
      <default>
        <bool>false</bool>
      </default>
    </setting>
    <setting key="elastic-ui.log.depth">
      <value>
        <int>-1</int>
      </value>
      <default>
        <int>-1</int>
      </default>
    </setting>
    <setting key="elastic.licence">
      <value>
        <file>Oe0XGhHuik5fwIEAxtoQ890KFcWV5EWG5za</file>
      </value>
      <default>
        <string></string>
      </default>
    </setting>
    <setting key="elastic.log.depth">
      <value>
        <int>-1</int>
      </value>
      <default>
        <int>-1</int>
      </default>
    </setting>
    <setting key="elastic.rules.path">
      <value>
        <file>~/Library/Preferences/Naviga/ElasticLayoutPlugin/elasticrules.xml</file>
      </value>
      <default>
        <file>~/Library/Preferences/Naviga/ElasticLayoutPlugin/elasticrules.xml</file>
      </default>
    </setting>
  </config-map>
</config>

When installing Naviga Templates on an InDesign Server in a production environment it is essential to add this configuration file with a valid license key. Simply because the server do not have a UI to enter the license key.

When distributing plugins and settings to clients this file also needs to be distibuted, to get a valid license key.

Rules file

When running an elastic process for the first time, and every time the file is missing, the plugin will create a general rules file on the current local machine. This file contains settings that decides in what order the main elastic process will be executed. This is generally not something that one need to change, but if something needs to be changed it might be good to know that the file needs to be distributed to the clients.

The rules file can be reached using the menu in the Naviga Templates UI panel:

"Reveal rules file" will open the folder containing the rules file.

Here is an example of what the file can look like:

<?xml version="1.0" encoding="utf-8"?>
<elastic-rulesets creator="elastic-layout" version="1.0">
    <elastic-ruleset active="true">
        <elastic-rule type="handle.preprocess">
            <operation type="remove.empty.frames"/>
        </elastic-rule>
        <elastic-rule type="handle.overset">
            <operation type="remove.optional"/>
            <operation type="decrease.framesize"/>        
        </elastic-rule>
        <elastic-rule type="handle.underset">
            <operation type="increase.framesize"/>
        </elastic-rule>
        <elastic-rule type="handle.postprocess">
            <operation type="insert.rows.after.body"/>
            <operation type="fit-text-to-frame"/>
        </elastic-rule>
        <settings>
            <setting key="underset.threshold">2</setting>
        </settings>
    </elastic-ruleset>
    <global-settings>
        <setting key="underset.threshold">7</setting>
    </global-settings>
</elastic-rulesets>

During an upgrade of the Naviga Templates plugin it might be a good idea to remove the rules file if new functionality demands it.