Configuration files

The user directory

Beginning with version 0.2.8, TMNav store its configuration files in a special directory called .tmnav which is created in the home-directory of the current user.

On boot time, TMNav first checks for the existence of the .tmnav-directory and its contents. If any of the required files are missing, TMNav will create them.

Currently, TMNav needs three files for proper operation:

tmnav.xml: Contains information about available renderers, abstractors and providers. Additionally this is the place where you register custom extensions, that use TMNav's plugin API.
Read more for some details about the xml used in tmnav.xml
tmnavdefaults.xml: Contains more fundamental information, like fonts to use or configuration of RendererViews. Settings specified in this file may be overlapped by settings of the last session and therefor does not become visible. See session persistency for how to instruct tmnav to ignore settings from prior sessions.
panckouckecontext.xml: Contains TMNav's custom panckoucke-context. See the panckoucke documentation for additional details.

Customizing TMNav

You may edit any of the files in the .tmnav-directory. If you want to reset TMNav to the factory settings, simply remove one or several files or the .tmnav-directory as a whole. TMNav will recreate the missing items on next startup.

TMNav does not use the .tmnav-directory to store session data. Therefor TMNav never perform any changes in any of the files. What TMNav does is, that it copies files as a whole from its internal repository, if any of the required files are missing at startup.

The one and only file that is of interest in terms of user customisation is tmnav.xml. The settings for the rendererviews from tmnavdefault.xml are overlaid by the session data and panckouckecontext.xml as well is partially overriden by tmnav.xml.