<?xml version="1.0" encoding="utf-8" ?>
<HEADING1 item="y" nospace="y" nobreaks="y" tlversion="1.3.5"
line0="{*Name*}"
line1="&lt;center&gt;&lt;h1&gt;{*Name*}&lt;/h1&gt;&lt;/center&gt;"
childtype="HEADING2">
<Name type="Text">TreeLine ReadMe</Name>
<Ref type="Text" ref="y"></Ref>
<HEADING1 item="y">
<Name>ReadMe File for TreeLine</Name>
</HEADING1>
<HEADING_CNTR item="y"
line0="{*Name*}"
line1="&lt;center&gt;&lt;h2&gt;{*Name*}&lt;/h2&gt;&lt;/center&gt;"
childtype="TEXT_PARA">
<Name type="Text">an information storage program</Name>
<Ref type="Text" ref="y"></Ref>
</HEADING_CNTR>
<TEXT_CNTR item="y"
line0="{*Name*}"
line1="&lt;center&gt;{*Name*}&lt;/center&gt;">
<Name type="Text">by Doug Bell</Name>
<Ref type="Text" ref="y"></Ref>
</TEXT_CNTR>
<TEXT_CNTR item="y">
<Name>Version 1.4.0 (new stable release)</Name>
</TEXT_CNTR>
<TEXT_CNTR item="y">
<Name>April 14, 2011</Name>
</TEXT_CNTR>
<HEADING2 item="y"
line0="{*Name*}"
line1="&lt;hr /&gt;&lt;h2&gt;{*Name*}&lt;/h2&gt;"
childtype="HEADING3">
<Name type="Text">Contents</Name>
<Ref type="Text" ref="y"></Ref>
<CONTENTS_LINK item="y"
line0="{*Name*}"
line1="&lt;br /&gt;{*Link*}&lt;br /&gt;">
<Name type="Text">Background</Name>
<Link type="InternalLink" html="y" linkalt="Name">background</Link>
<Ref type="Text" ref="y"></Ref>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Features</Name>
<Link>features</Link>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Legal Issues</Name>
<Link>legal</Link>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>System Requirements</Name>
<Link>sysreq</Link>
<CONTENTS_LINK_INDENT item="y"
line0="{*Name*}"
line1="&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{*Link*}&lt;br /&gt;">
<Name type="Text">Linux</Name>
<Link type="InternalLink" html="y" linkalt="Name">linux-sys</Link>
<Ref type="Text" ref="y"></Ref>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Windows</Name>
<Link>win-sys</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Installation</Name>
<Link>install</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Linux</Name>
<Link>linux-inst</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Windows</Name>
<Link>win-inst</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Using TreeLine</Name>
<Link>using</Link>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Revision History</Name>
<Link>revs</Link>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Questions, Comments, Criticisms?</Name>
<Link>contact</Link>
</CONTENTS_LINK>
</HEADING2>
<HEADING2 item="y">
<Name>Background</Name>
<Ref>background</Ref>
<TEXT_PARA item="y"
line0="{*Topic*}"
line1="&lt;p&gt;{*Text*}&lt;/p&gt;">
<Topic type="Text">Introduction</Topic>
<Text type="Text" html="y" lines="12">Do you have lots of sticky notes lying around with various useful information jotted down? Or many lists of books, movies, links, website logins, personal contacts, or things to do? Can you find them when you need them? Well, I often couldn't. So here's my answer.</Text>
<Ref type="Text" ref="y"></Ref>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Overview</Topic>
<Text>Some would call TreeLine an Outliner, others would call it a PIM. Basically, it just stores almost any kind of information. A tree structure makes it easy to keep things organized. And each node in the tree can contain several fields, forming a mini-database. The output format for each node can be defined, and the output can be shown on the screen, printed, or exported to HTML.</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>It's free</Topic>
<Text>Since I'm not in the software business, I'm making this program free for anyone to use, distribute and modify, as long as it is not incorporated into any proprietary programs. If you like the software, feel free to let others know about it. And let me know what you think - see the &lt;a href=&quot;#contact&quot;&gt;Questions, Comments, Criticisms?&lt;/a&gt; section for contact information.</Text>
</TEXT_PARA>
</HEADING2>
<HEADING2 item="y">
<Name>Features</Name>
<Ref>features</Ref>
<HEADING4 item="y"
line0="{*Name*}"
line1="&lt;h4&gt;{*Name*}&lt;/h4&gt;"
childtype="TEXT_BULLETS">
<Name type="Text">General</Name>
<Ref type="Text" ref="y"></Ref>
<TEXT_BULLETS item="y"
line0="{*Topic*}"
line1="&lt;li&gt;{*Text*}&lt;/li&gt;"
sibprefix="&lt;ul&gt;"
sibsuffix="&lt;/ul&gt;">
<Topic type="Text">Store information</Topic>
<Text type="Text" html="y" lines="7">Stores almost any type of information, including plain text, HTML, numbers, dates, times, booleans, URLs, etc.</Text>
<Ref type="Text" ref="y"></Ref>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tree structure</Topic>
<Text>The tree structure helps keep things organized.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Fields</Topic>
<Text>Each node can have several fields that form a mini-database.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Node types</Topic>
<Text>Several node types, with different sets of fields, can be included in one file.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Output format</Topic>
<Text>The node format, including fields, output lines and tree-view icon, can be defined for each node type.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Views</Name>
<TEXT_BULLETS item="y">
<Topic>Left-hand view</Topic>
<Text>The left-hand view defaults to a tree view but can show a flat list of descendants of the current node.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Filtering</Topic>
<Text>The left flat view also shows the results of filtering operations.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Right-hand view</Topic>
<Text>The right-hand view can show one of three views - for showing output, editing node data and editing node titles.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Show parent and children</Topic>
<Text>The right-hand view is normally split to show data from the parent node and its children.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Show multiple selection</Topic>
<Text>If multiple nodes are selected, the right-hand view shows all of their data.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Show descendant output</Topic>
<Text>The output view can be set to show indented output from all descendant nodes.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Navigation</Name>
<TEXT_BULLETS item="y">
<Topic>Incremental search</Topic>
<Text>There is a quick incremental search command to find a matching node title.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Find command</Topic>
<Text>There is a find command that searches through all node data.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Toggle selections</Topic>
<Text>Previous and next selection commands toggle selections to quickly move between parts of the tree.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Formatting</Name>
<TEXT_BULLETS item="y">
<Topic>Format dialog</Topic>
<Text>The dialog for data type configuration has several tabs to easily set all type, field and output parameters.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Format copies</Topic>
<Text>Formatting information can be copied from another TreeLine file.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>File Handling</Name>
<TEXT_BULLETS item="y">
<Topic>Undo/redo</Topic>
<Text>Undo and redo commands are available for all modifying operations.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>File formats</Topic>
<Text>TreeLine files are XML by default, but there are options for automatically compressing or encrypting the files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Document templates</Topic>
<Text>Document templates for new files are preformatted to cover basic needs.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Printing</Topic>
<Text>The formatted output can be printed with parent/child lines and  headers and footers.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>File Import and Export</Name>
<TEXT_BULLETS item="y">
<Topic>HTML export</Topic>
<Text>The data can be exported to HTML.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XSLT export</Topic>
<Text>An XSLT file can be exported to work with the XML TreeLine files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Text import/export</Topic>
<Text>Tab-delimited tables and tab-indented text files can be imported and exported.  Plain text files and Treepad files can be imported.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Bookmark import/export</Topic>
<Text>Mozilla and XBEL format bookmark files can be imported and exported.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Generic XML import/export</Topic>
<Text>Generic XML files can be imported and exported, allowing TreeLine to function as a crude XML editor.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>ODF import/export</Topic>
<Text>ODF text documents can be imported and exported as outlines.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Batch conversion</Topic>
<Text>Batch file conversions can be done from a command line interface.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Linking Objects</Name>
<TEXT_BULLETS item="y">
<Topic>URL links</Topic>
<Text>Clicking on URL fields in the output view opens the link in an external web browser.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Internal links</Topic>
<Text>There are internal link fields that select another node based on a reference or a keyword.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Executable links</Topic>
<Text>An executable link can run an external program or open a file when clicked.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Data Manipulation</Name>
<TEXT_BULLETS item="y">
<Topic>Sorting</Topic>
<Text>There are several sorting options.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Filtering</Topic>
<Text>The nodes can be filtered.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Conditional types</Topic>
<Text>A node's icon and output format can be changed conditionally based on its data.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check</Topic>
<Text>Text data can be spell checked (requires an external program - see the &lt;a href=&quot;#sysreq&quot;&gt;System Requirements&lt;/a&gt; section).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Arranging data</Topic>
<Text>Data can be automatically arranged using either parent references or categories from data fields.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Numbering</Topic>
<Text>There is an outline numbering feature.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Customization</Name>
<TEXT_BULLETS item="y">
<Topic>Customization</Topic>
<Text>There are many options for customizing both general and file-based attributes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Shortcuts and toolbars</Topic>
<Text>There are editors for keyboard shortcuts and toolbar commands.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Internationalization</Topic>
<Text>The user interface and documentation are available in English, French and German.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING2>
<HEADING2 item="y">
<Name>Legal Issues</Name>
<Ref>legal</Ref>
<TEXT_PARA item="y">
<Topic>Free software</Topic>
<Text>TreeLine is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either Version 2 of the License, or (at your option) any later version.</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>No warranty</Topic>
<Text>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. See the LICENSE file provided with this program for more information.</Text>
</TEXT_PARA>
</HEADING2>
<HEADING2 item="y">
<Name>System Requirements</Name>
<Ref>sysreq</Ref>
<HEADING4 item="y">
<Name>Linux</Name>
<Ref>linux-sys</Ref>
<TEXT_PARA item="y">
<Topic>Libraries</Topic>
<Text>TreeLine requires the following libraries and programs:</Text>
<TEXT_BULLETS item="y">
<Topic>Qt</Topic>
<Text>Qt (Version 4.4 or higher)</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Python</Topic>
<Text>Python (Version 2.4, 2.5 or 2.6)</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>PyQt</Topic>
<Text>PyQt (Version 4.4.0 or higher - see &lt;a href=&quot;http://www.riverbankcomputing.co.uk&quot;&gt; www.riverbankcomputing.co.uk&lt;/a&gt; for more information)</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XML parser</Topic>
<Text>An XML parser is required, such as the expat library or the PyXML package</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check</Topic>
<Text>If spell checking capability is desired, either the aspell (preferred) or ispell programs are required (these are packaged with most distributions)</Text>
</TEXT_BULLETS>
</TEXT_PARA>
</HEADING4>
<HEADING4 item="y">
<Name>Windows</Name>
<Ref>win-sys</Ref>
<TEXT_PARA item="y">
<Topic>Binary</Topic>
<Text>Using the files provided in the installer, TreeLine should run on any computer running Windows XP, Vista or 7.</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Spell check</Topic>
<Text>If spell checking capability is desired, an external program is required.  Either aspell (preferred) or ispell must be installed.  See &lt;a href=&quot;http://aspell.net/win32/&quot;&gt; aspell.net/win32/&lt;/a&gt; or &lt;a href=&quot;http://www.luziusschneider.com/Speller/English/&quot;&gt; www.luziusschneider.com/Speller/English/&lt;/a&gt; to download one of the programs and its dictionaries for any desired languages.</Text>
</TEXT_PARA>
</HEADING4>
</HEADING2>
<HEADING2 item="y">
<Name>Installation</Name>
<Ref>install</Ref>
<HEADING4 item="y">
<Name>Linux</Name>
<Ref>linux-inst</Ref>
<TEXT_PARA item="y">
<Topic>Basic install</Topic>
<Text>Extract the source files from the treeline tar file, then change to the TreeLine directory in a terminal.  For a basic installation, simply execute the following command as root:  &quot;python install.py&quot;</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Install options</Topic>
<Text>To see all install options, use: &quot;python install.py -h&quot;&lt;br /&gt;&lt;br /&gt;

To install TreeLine with a different prefix (the default is /usr/local), use:  &quot;python install.py -p /prefix/path&quot;</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Internationalization</Topic>
<Text>To install language translations for TreeLine, download the &quot;treeline-i18n-...&quot; tar file that matches the version number of the main TreeLine file (ignore the letter suffix on the translation version number).  To install the program and translation files simultaneously, extract the translation file from the same directory where the main treeline tar file was extracted and run the install command as described above.  If TreeLine is already installed, extract the translation file to any directory and run the translation's install command as described above.</Text>
</TEXT_PARA>
</HEADING4>
<HEADING4 item="y">
<Name>Windows</Name>
<Ref>win-inst</Ref>
<TEXT_PARA item="y">
<Topic>Basic install</Topic>
<Text>Simply execute the downloaded installation file (treeline-x.x.x-install.exe).  It will install the program with its libraries and optionally create file associations and shortcuts.</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Spell checker</Topic>
<Text>To use TreeLine's spell checker, an external program (aspell or ispell) must be installed (see the &lt;a href=&quot;#sysreq&quot;&gt;System Requirements&lt;/a&gt; section).</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Internationalization</Topic>
<Text>To install language translations for TreeLine, download the &quot;treeline-i18n-...&quot; exe file that matches the version number of the main TreeLine file (ignore the letter suffix on the translation version number).  To install the translation files, simply execute the translation file.</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Modify source code</Topic>
<Text>If you wish to modify the source code or write your own PyQt programs for Windows, do not use the above procedure. Instead, you need to install Python (see &lt;a href=&quot;http://www.python.org&quot;&gt; www.python.org&lt;/a&gt;), Qt (see &lt;a href=&quot;http://www.trolltech.com&quot;&gt; www.trolltech.com&lt;/a&gt;), and PyQt (see &lt;a href=&quot;http://www.riverbankcomputing.co.uk&quot;&gt; www.riverbankcomputing.co.uk&lt;/a&gt;). Then extract the source code files from the Linux version (treeline tar file) to a directory of your choice and execute the treeline.py file.</Text>
</TEXT_PARA>
</HEADING4>
</HEADING2>
<HEADING2 item="y">
<Name>Using TreeLine</Name>
<Ref>using</Ref>
<HEADING3 item="y"
line0="{*Name*}"
line1="&lt;hr /&gt;&lt;h3&gt;{*Name*}&lt;/h3&gt;"
childtype="HEADING4">
<Name type="Text">Contents</Name>
<Ref type="Text" ref="y"></Ref>
<CONTENTS_LINK item="y">
<Name>Getting Started</Name>
<Link>start</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Introduction</Name>
<Link>start-intro</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Templates</Name>
<Link>start-templates</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Example Files</Name>
<Link>start-example</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Basics</Name>
<Link>basics</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Left Pane Views</Name>
<Link>basics-left</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Right Pane Views</Name>
<Link>basics-right</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Commands</Name>
<Link>basics-cmds</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Multiple Windows</Name>
<Link>basics-wins</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Tree Navigation</Name>
<Link>nav</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Keyboard Shortcuts</Name>
<Link>nav-keys</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Selection</Name>
<Link>nav-select</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Searching</Name>
<Link>nav-search</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Tree Editing</Name>
<Link>edit</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Edit Menu</Name>
<Link>edit-menu</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Shortcuts</Name>
<Link>edit-shortcuts</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Right Pane Views</Name>
<Link>edit-view</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Spell Check</Name>
<Link>edit-spell</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Formatting and Node Types</Name>
<Link>format</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Setting Nodes to a Type</Name>
<Link>format-set</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Type List</Name>
<Link>format-type</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Type Config</Name>
<Link>format-config</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Field List</Name>
<Link>format-fields</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Field Config</Name>
<Link>format-fieldconf</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Output</Name>
<Link>format-output</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Title Formatting</Name>
<Link>format-title</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Skipped Lines</Name>
<Link>format-skip</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>HTML Tags</Name>
<Link>format-html</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Formatting Examples</Name>
<Link>format-example</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Other Field References</Name>
<Link>format-refs</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Sibling Prefix and Suffix</Name>
<Link>format-sibling-text</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Link Reference Field</Name>
<Link>format-link-ref</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Generic and Derived Types</Name>
<Link>format-derived</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Conditional Types</Name>
<Link>format-condition</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Copying Formats</Name>
<Link>format-copy</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Field Types</Name>
<Link>fields</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Field Options</Name>
<Link>field-options</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Text Type</Name>
<Link>field-text</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Choice, Combination and Boolean Types</Name>
<Link>field-choice</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Number Type</Name>
<Link>field-number</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Date and Time Types</Name>
<Link>field-date</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Linking Types</Name>
<Link>field-link</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Unique ID Type</Name>
<Link>field-unique</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Advanced Options</Name>
<Link>field-advanced</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Tree Data Manipulation</Name>
<Link>data</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Category-based Commands</Name>
<Link>data-category</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Reference-based Commands</Name>
<Link>data-ref</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Sorting</Name>
<Link>data-sort</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Filtering</Name>
<Link>data-filter</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Numbering</Name>
<Link>data-number</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Change Selections</Name>
<Link>data-change</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Printing</Name>
<Link>print</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Print Options</Name>
<Link>print-options</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Page Setup</Name>
<Link>print-setup</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Printer Font</Name>
<Link>print-font</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Header and Footer</Name>
<Link>print-header</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Print Preview</Name>
<Link>print-preview</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Printing Problems</Name>
<Link>print-problems</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>File Handling</Name>
<Link>file</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>File Compression</Name>
<Link>file-comp</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>File Encryption</Name>
<Link>file-enc</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Auto Save</Name>
<Link>file-auto-save</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Saved Tree States</Name>
<Link>file-states</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Command Line</Name>
<Link>file-cmdline</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>File Import</Name>
<Link>import</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>General Information</Name>
<Link>import-general</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Delimited Text</Name>
<Link>import-delim</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Plain Text</Name>
<Link>import-plain</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Treepad Files</Name>
<Link>import-treepad</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Bookmark Files</Name>
<Link>import-bookmarks</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Generic XML</Name>
<Link>import-xml</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>ODF Text Document</Name>
<Link>import-odf</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>File Export</Name>
<Link>export</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>General Information</Name>
<Link>export-general</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>HTML</Name>
<Link>export-html</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Delimited Text</Name>
<Link>export-delim</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Bookmark Files</Name>
<Link>export-bookmarks</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Generic XML</Name>
<Link>export-xml</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>XSLT</Name>
<Link>export-xslt</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>ODF Text Document</Name>
<Link>export-odf</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Customizations</Name>
<Link>custom</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Options</Name>
<Link>custom-options</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Fonts</Name>
<Link>custom-fonts</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Keyboard Shortcuts</Name>
<Link>custom-keys</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Toolbars</Name>
<Link>custom-tools</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Colors</Name>
<Link>custom-color</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Tree Icons</Name>
<Link>custom-icons</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Plugins</Name>
<Link>plugins</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Description</Name>
<Link>plugins-intro</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Installation</Name>
<Link>plugins-install</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Interface</Name>
<Link>plugins-intrf</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
<CONTENTS_LINK item="y">
<Name>Common Problems</Name>
<Link>errors</Link>
<CONTENTS_LINK_INDENT item="y">
<Name>Closed Panes</Name>
<Link>errors-panes</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>XML Error</Name>
<Link>errors-xml</Link>
</CONTENTS_LINK_INDENT>
<CONTENTS_LINK_INDENT item="y">
<Name>Printing</Name>
<Link>errors-print</Link>
</CONTENTS_LINK_INDENT>
</CONTENTS_LINK>
</HEADING3>
<HEADING3 item="y">
<Name>Getting Started</Name>
<Ref>start</Ref>
<TEXT_HEAD item="y"
line0="{*Topic*}"
line1="&lt;h4&gt;{*Topic*}&lt;/h4&gt;"
line2="&lt;p&gt;{*Text*}&lt;/p&gt;">
<Topic type="Text">Introduction</Topic>
<Text type="Text" html="y" lines="12">TreeLine is a more complex program than it appears at first glance.  Reading much of this documentation is highly recommended in order to learn to use it effectively.&lt;br /&gt;&lt;br /&gt;

The &lt;a href=&quot;#basics&quot;&gt;Basics&lt;/a&gt; section describes views and selections.  To learn how to move around and change the tree, refer to the &lt;a href=&quot;#nav&quot;&gt;Tree Navigation&lt;/a&gt; and &lt;a href=&quot;#edit&quot;&gt;Tree Editing&lt;/a&gt; sections.  Next, its time to go beyond using TreeLine with only simple text for each node.  To learn about setting up custom data for each node, refer to the &lt;a href=&quot;#format&quot;&gt;Formatting and Node Types&lt;/a&gt; and the &lt;a href=&quot;#fields&quot;&gt;Field Types&lt;/a&gt; sections.</Text>
<Ref type="Text" ref="y">start-intro</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Templates</Topic>
<Text>When starting a new file, the templates dialog gives a choice of nodes with a single line of text or with long text.  The single line template only has a node title, while the long text options have a title and a multiple line text field in each node.  For long text, you can also choose between plain text, which preserves line breaks, and HTML text, which allows more complex formatting.&lt;br /&gt;&lt;br /&gt;

There are a few more specific options, including canned setups for personal contact information, a book list and a to-do list.</Text>
<Ref>start-templates</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Example Files</Topic>
<Text>Various TreeLine sample files can be opened by using the &quot;File-&amp;gt;Open Sample&quot; command.  They include (roughly in order of increasing complexity):</Text>
<Ref>start-example</Ref>
<TEXT_BULLETS item="y">
<Topic>sample_basic_contacts</Topic>
<Text>The &quot;sample_basic_contacts&quot; file is a format for storing contact information.  Several fields are used for various pieces of information.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_basic_booklist</Topic>
<Text>The &quot;sample_basic_booklist&quot; file is a list of books, providing an example of configuring nodes to contain data.  Several different field types are used to create author and book data types.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_basic_longtext</Topic>
<Text>The &quot;sample_basic_longtext&quot; file contains a long text field under each node, similar to the Treepad program.  It also shows the difference between plain text and HTML text fields.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_color_items</Topic>
<Text>The &quot;sample_color_items&quot; file uses HTML tags in data type formats to provide color output. See also the &lt;a href=&quot;#format-html&quot;&gt;HTML Tags&lt;/a&gt; section.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_char_format</Topic>
<Text>The &quot;sample_char_format&quot; file is an example of using HTML tags in the data to control font formatting.  See also the &lt;a href=&quot;#format-html&quot;&gt;HTML Tags&lt;/a&gt; and the &lt;a href=&quot;#field-options&quot;&gt;Field Options&lt;/a&gt; sections.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_bookmarks</Topic>
<Text>The &quot;sample_bookmarks&quot; file is an example of  using external HTML links.  This is the file setup that is used when importing or exporting bookmark files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_intern_links</Topic>
<Text>The &quot;sample_intern_links&quot; file shows how to do links that lead to elsewhere in the TreeLine file.  See also the &lt;a href=&quot;#field-link&quot;&gt;Linking Types&lt;/a&gt; section.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_table_booklist</Topic>
<Text>The &quot;sample_table_booklist&quot; file shows how to use HTML tags and sibling prefixes and suffixes to create tables in the output.  See also the &lt;a href=&quot;#format-advanced&quot;&gt;Advanced Settings&lt;/a&gt; section.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_other_fields</Topic>
<Text>The &quot;sample_other_fields&quot; file is an example of alternate field references, including references to ancestor nodes, child nodes and file information.  See also the &lt;a href=&quot;#format-refs&quot;&gt;Other Field References&lt;/a&gt; section.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>sample_conditional_todo</Topic>
<Text>The &quot;sample_conditional_todo&quot; shows how to use conditional types to change node output based on node content.  See also the &lt;a href=&quot;#format-derived&quot;&gt;Derived&lt;/a&gt; and &lt;a href=&quot;#format-condition&quot;&gt;Conditional Types&lt;/a&gt; sections.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>readme</Topic>
<Text>The &quot;readme&quot; file itself shows many types of formatting, including  headings, bullets, internal links and pictures.</Text>
</TEXT_BULLETS>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Basics</Name>
<Ref>basics</Ref>
<TEXT_HEAD item="y">
<Topic>Left Pane Views</Topic>
<Text>The default view in the left pane is the &quot;Tree View&quot;.  Parent nodes can be opened and closed to display or hide their indented descendant nodes.&lt;br /&gt;&lt;br /&gt;

The other tab in the left pane is the &quot;Flat View&quot;.  It displays all of the descendants of the nodes that are selected in the &quot;Tree View&quot; in a flat list.  It also shows the results of filtering operations (see the &lt;a href=&quot;#data-filter&quot;&gt;Filtering&lt;/a&gt; section).</Text>
<Ref>basics-left</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Right Pane Views</Topic>
<Text>The right pane is tabbed to show one of three different views of the data. The &quot;Data Output&quot; view shows the formatted text for each node and is read-only (see &lt;a href=&quot;#fig-1&quot;&gt;Figure 1&lt;/a&gt;). The &quot;Data Editor&quot; view shows a text edit box for each data field within a node (see &lt;a href=&quot;#fig-2&quot;&gt;Figure 2&lt;/a&gt;). The &quot;Title List&quot; view shows a list of node titles that can be modified using typical text editor methods.&lt;br /&gt;&lt;br /&gt;

When a parent node is selected in the tree, the right view will default to showing information about the selected node in an upper pane and information about the selected node's children in the lower pane.  The &quot;View-&amp;gt;Show Child Pane&quot; command will toggle the display of the child nodes.  If the selected node has no children, the view will show a single pane with information about the selected node only.&lt;br /&gt;&lt;br /&gt;

When multiple nodes are selected in the tree, the right view will not display any child node information.  It will instead show information about every selected node.&lt;br /&gt;&lt;br /&gt;

When the &quot;View-&amp;gt;Show Output Descendants&quot; command is toggled, the &quot;Data Output&quot; tab will show an indented list with information about every descendant of a single selected node.&lt;br /&gt;&lt;br /&gt;

The initial state of the views can be controlled by changing the startup conditions in &quot;Tools-&amp;gt;General Options&quot;.&lt;br /&gt;&lt;br /&gt;

By default, the number of nodes displayed simultaneously in the &quot;Data Editor&quot; view is limited.  Buttons in a heading allow the next or previous set of nodes to be displayed.  This provides a convenient way to page through the node information without slowing the program by trying to display too many fields.  The number of pages to display can be set in &quot;Tools-&amp;gt;General Options&quot;.</Text>
<Ref>basics-right</Ref>
<FIGURE item="y"
line0="{*Topic*}"
line1="&lt;p&gt;{*Picture*}&lt;/p&gt;"
line2="&lt;p&gt;&lt;b&gt;{*Caption*}&lt;/b&gt;&lt;/p&gt;">
<Topic type="Text">Output pane picture</Topic>
<Caption type="Text" html="y" lines="2">Figure 1:  Output Pane</Caption>
<Picture type="Picture" html="y">doc_main.png</Picture>
<Ref type="Text" ref="y">fig-1</Ref>
</FIGURE>
<FIGURE item="y">
<Topic>Edit pane picture</Topic>
<Caption>Figure 2:  Edit Pane</Caption>
<Picture>doc_edit.png</Picture>
<Ref>fig-2</Ref>
</FIGURE>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Commands</Topic>
<Text>Most of the menu and tool-bar commands apply to the items selected in the left view. In general, they perform an operation on the nodes themselves or on the descendants of the nodes. Multiple nodes can be selected by holding down the &quot;Ctrl&quot; and &quot;Shift&quot; buttons when clicking with the mouse.&lt;br /&gt;&lt;br /&gt;

To add information to a new TreeLine document, use the &quot;Edit-&amp;gt;Add Child&quot; command to create a new node. Then combinations of the add and insert commands may be used for additional nodes. Alternatively, new node titles may be typed into the &quot;Title List&quot; view in the right pane.</Text>
<Ref>basics-cmds</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Multiple Windows</Topic>
<Text>Multiple TreeLine windows with different files can be opened within the same TreeLine session. The &quot;Open files in new windows&quot; option in &quot;Tools-&gt;General Options&quot; controls whether new windows are used when opening or creating files.&lt;br /&gt;&lt;br /&gt;

The &quot;Window-&gt;New Window&quot; command will create a new window with views of the same TreeLine file. Changes in either window are saved in the same document. This can be used to work in different sections of the file simultaneously. For performance reasons, the non-active window does not show the changes made in the active window until either the non-active window is focused or the &quot;Window-&gt;Update Other Window&quot; command is issued.&lt;br /&gt;&lt;br /&gt;

Starting TreeLine (from a shortcut, file association or command line) will activate an existing TreeLine session if it is already running. A new window will be opened if an unopened file was specified by file association or in the command line.</Text>
<Ref>basics-wins</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Tree Navigation</Name>
<Ref>nav</Ref>
<TEXT_HEAD item="y">
<Topic>Keyboard Shortcuts</Topic>
<Text>There are several keyboard commands that can be used for tree navigation. The up and down arrow keys move the selection. The left and right arrows open and close the current node. Holding the CTRL and SHIFT keys with &quot;J&quot; or &quot;K&quot; moves between siblings, skipping children. The CTRL key and &quot;U&quot; moves to an item's parent. The &quot;Home&quot;, &quot;End&quot;, &quot;Page Up&quot; and &quot;Page Down&quot; keys can be used to move quickly through the tree.  The CTRL and SHIFT keys can be held with the &quot;Page Up&quot; and &quot;Page Down&quot; keys to move the tree view even when a different pane is focused.&lt;br /&gt;&lt;br /&gt;

All of these keys and the keyboard shortcuts for pull-down menu commands can be customized by using the &quot;Tools-&amp;gt;Set Keyboard Shortcuts&quot; command.  The shortcut editor has tabs for menu and non-menu based commands.  Simply type the new key sequence with the appropriate field selected.&lt;br /&gt;&lt;br /&gt;

Another way to move through the tree is to type the first letter of a visible node title. Hitting the letter again moves to the next possibility.</Text>
<Ref>nav-keys</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Selection</Topic>
<Text>Multiple nodes can be selected by holding down the CTRL or the SHIFT keys when changing the active node.  Individual nodes are added or removed from the selection when the CTRL key is held.  The selection of all nodes between the old and new active nodes are toggled when SHIFT is held.  The active node can be changed by using the mouse or by using any of the keyboard navigation methods.&lt;br /&gt;&lt;br /&gt;

The &quot;View-&amp;gt;Previous Selection&quot; and &quot;View-&amp;gt;Next Selection&quot; commands can be used to toggle through a history of selections, allowing faster navigation through the tree.&lt;br /&gt;&lt;br /&gt;

By default, the selection sequence doesn't matter.  However, if the general option for multiple selection is changed to &quot;Selection Order&quot;, nodes selected with CTRL key held are output in the order selected.</Text>
<Ref>nav-select</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Searching</Topic>
<Text>There are two ways to search for nodes. These methods can find nodes that are buried in the tree structure. The first is the &quot;Tools-&amp;gt;Find&quot; command. Keywords can be entered in a modeless dialog box. A node is found if the keywords are matched in any of the node's fields.  The matching text will highlight in the &quot;Data Output&quot; pane.&lt;br /&gt;&lt;br /&gt;

The next method is an incremental search, started by typing CTRL + &quot;/&quot;.  Then type the search string, which shows up in the lower status bar area. The search will progress as the string is being typed. The incremental search only finds text in the node's titles.  The previous search can be repeated with the &quot;F3&quot; key and backward with &quot;Shift-F3&quot;.&lt;br /&gt;&lt;br /&gt;

By default, parent nodes will automatically open and close when found with the search methods, by typing the first letter, and with the &quot;next sibling&quot; keyboard command. This behavior can be disabled in &quot;Tools-&amp;gt;General Options&quot;.</Text>
<Ref>nav-search</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Tree Editing</Name>
<Ref>edit</Ref>
<TEXT_HEAD item="y">
<Topic>Edit Menu</Topic>
<Text>The commands in the &quot;Edit&quot; menu (except for undo and redo) operate on the selected nodes in the left tree view. The cut, copy and paste commands can be an exception to this, since they operate on the right view when something is selected there. And keep in mind that, in general, the descendants of the selected nodes are also affected.&lt;br /&gt;&lt;br /&gt;

Paste will add a copied nodes as the last child of the selected node.  If more than one node is selected, additional copies are added under each selected node.&lt;br /&gt;&lt;br /&gt;

The &quot;Edit-&amp;gt;Paste Node Text&quot; command renames the selection based on either the text in the clipboard or the title of the top node in the clipboard.</Text>
<Ref>edit-menu</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Shortcuts</Topic>
<Text>There are several shortcuts for use in tree editing. Drag and drop will move or copy nodes to become a children of the destination node. Clicking on a selected node will rename it. Pressing the enter key will insert a new node, and pressing the delete key will remove the selected nodes. If desired, these shortcuts can be disabled in &quot;Tools-&amp;gt;General Options&quot;.</Text>
<Ref>edit-shortcuts</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Right Pane Views</Topic>
<Text>In the right pane, the &quot;Data Editor&quot; view provides the most direct way to edit the data within a node. If the edited field is used in the title formatting, the node title in the tree will show the changes. The field editor will scroll, allowing multiple lines of text to be entered.&lt;br /&gt;&lt;br /&gt;

There are items in the &quot;Data Editor&quot; box context menus to add HTML font tags around selected text. These tags include bold, italics, underline, size and color. Note that the fields must be set to display HTML content (see the &lt;a href=&quot;#fields&quot;&gt;Field Types&lt;/a&gt; section) for this to be effective.&lt;br /&gt;&lt;br /&gt;

Another edit box context menu item will add an internal link in the text.  The status bar will then prompt the user to click on the link destination in the tree view.  This will add an internal link to that destination to the text in the edit box.  Of course, the field must be set to display HTML content for this to be effective.&lt;br /&gt;&lt;br /&gt;

An external editor can also be invoked from a &quot;Data Editor&quot; box context menu.   After the text editor saves changes and is closed, the changed text will be in the text box.  The EDITOR environment variable can be used to specify the editor to start, or, if the variable doesn't exist, TreeLine will prompt for an executable to set as the default.&lt;br /&gt;&lt;br /&gt;

Also in the right pane, the &quot;Title List&quot; view is useful to quickly rename child titles or to add new child nodes. A text list of new nodes can even be pasted directly into this view.</Text>
<Ref>edit-view</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Spell Check</Topic>
<Text>There is a spell check command in the &quot;Tools&quot; menu.  Use of this command requires an external program to be installed (either aspell or ispell - see the &lt;a href=&quot;#sysreq&quot;&gt;System Requirements&lt;/a&gt; section).  If there are any misspelled words in the selected branch, a dialog will allow the word to be ignored, added to the dictionary, replaced with a suggestion or edited.  This will spell check the text in all data fields of each node.&lt;br /&gt;&lt;br /&gt;

By default, the spell check will use dictionaries for the current operating system language.  If using aspell, there is an option under &quot;Tools-&amp;gt;File Options&quot; to specify an alternate two-letter language code for the current TreeLine file.  Note that the appropriate aspell dictionary files must be installed and that this option does not work with ispell.</Text>
<Ref>edit-spell</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Formatting and Node Types</Name>
<Ref>format</Ref>
<TEXT_HEAD item="y">
<Topic>Setting Nodes to a Type</Topic>
<Text>By default, a new TreeLine document contains two node types: &quot;ROOT&quot; and &quot;DEFAULT&quot;. The type is shown at the top of each node box in the &quot;Data Editor&quot; right-hand view. The creation of new types and the customization of types is described below. To set the selected nodes to a specific type, use the &quot;Data-&amp;gt;Set Item Type&quot; menu. Alternately, to set a series of child and descendant nodes to a specific type, use the &quot;Data-&amp;gt;Set Descendant Types&quot; command. The resulting dialog box allows the selected nodes, their children, all descendants, or descendants matching logical conditions to be set to the highlighted type. The dialog box can be left open while the tree selection is changed to set more nodes.</Text>
<Ref>format-set</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Type List</Topic>
<Text>The &quot;Type List&quot; is the first tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot;.  The list of data types can be modified by the buttons on the right.  New types can be added, and existing types can be copied, renamed or deleted.</Text>
<Ref>format-type</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Type Config</Topic>
<Text>&quot;Type Config&quot; is the second tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot;.  It contains a selection for the default child type.  If set, this will be the initial type used for new children with this type of parent.  If set to &quot;[None]&quot;, children will default to either the type of their siblings or their parent.&lt;br /&gt;&lt;br /&gt;

The &quot;Change Icon&quot; button allows the selection of a custom tree icon for this data type.  The &quot;Clear Select&quot; button on the icon dialog can be used to set the icon to &quot;None&quot;, so that no icon will be displayed for this type.   To avoid showing any tree icons, the &quot;Show icons in the tree view&quot; general option can be unset.</Text>
<Ref>format-config</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Field List</Topic>
<Text>The &quot;Field List&quot; is the third tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot;.  The list of fields within a data type can be modified by using the buttons on the right.  New fields can be added, and existing fields can be moved up and down in the list, renamed or deleted.</Text>
<Ref>format-fields</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Field Config</Topic>
<Text>&quot;Field Config&quot; is the fourth tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot; (see &lt;a href=&quot;#fig-3&quot;&gt;Figure 3&lt;/a&gt;).  The field type and its output format string can be set (see the &lt;a href=&quot;#fields&quot;&gt;Field Types&lt;/a&gt; section for details).  Extra prefix and suffix text to be output with the field can also be set, and a default field value for new nodes can be entered.  There is a choice between plain text, which preserves line breaks, and HTML text, which allows various formatting options.  Finally, the number of lines displayed in the editor for the field can be specified.</Text>
<Ref>format-fieldconf</Ref>
<FIGURE item="y">
<Topic>Field config picture</Topic>
<Caption>Figure 3:  Field Config Tab</Caption>
<Picture>doc_fieldconf.png</Picture>
<Ref>fig-3</Ref>
</FIGURE>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Output</Topic>
<Text>&quot;Output&quot; is the last tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot; (see &lt;a href=&quot;#fig-4&quot;&gt;Figure 4&lt;/a&gt;).  The left half of the dialog shows the fields.  The right half shows the formatting for the title (used for the node text in the tree view) and the node output. The formatting consists of text lines with embedded fields. The fields are shown as &quot;{*field_name*}&quot;. The field that is selected in the list can be added to a format at the cursor position with the &quot;&amp;gt;&amp;gt;&quot; keys.  The format field reference at the cursor can be removed with the &quot;&amp;lt;&amp;lt;&quot; keys.</Text>
<Ref>format-output</Ref>
<FIGURE item="y">
<Topic>Output tab picture</Topic>
<Caption>Figure 4:  Output Tab</Caption>
<Picture>doc_output.png</Picture>
<Ref>fig-4</Ref>
</FIGURE>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Title Formatting</Topic>
<Text>When a node in the tree is renamed, the program attempts to match the title formatting pattern to set the appropriate fields. If the title formatting is too complex, it may not correctly guess the intent. Things like adjacent fields with no characters separating them should be avoided unless you do not wish to rename nodes from the tree.&lt;br /&gt;&lt;br /&gt;

If the text data used for a tree view title has multiple lines, only the first line will be used as the title.</Text>
<Ref>format-title</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Skipped Output Lines</Topic>
<Text>If a line in the output formatting contains one or more fields and all of those fields for a given node are empty, the line is skipped. No blank line or embedded text will be output for that line. Note that this does not apply to a line without any fields (only embedded text). Also, when a line ending with a &amp;lt;br/&amp;gt; or an &amp;lt;hr/&amp;gt; tag is skipped, the ending tag is retained.</Text>
<Ref>format-skip</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>HTML Tags</Topic>
<Text>Simple HTML formatting tags can be used in node output formats. Commonly used tags include &quot;&amp;lt;b&amp;gt;bold&amp;lt;/b&amp;gt;&quot;, &quot;&amp;lt;u&amp;gt;underline&amp;lt;/u&amp;gt;&quot;, &quot;line break&amp;lt;br/&amp;gt;&quot;, &quot;&amp;lt;hr/&amp;gt;horizontal line&quot;, and various font tags. Complex block tags should generally be avoided. When the &quot;Allow HTML rich text in formats&quot; file option is disabled, formatting tags are treated as plain text.  For an example of tag use, see the &quot;sample_color_items&quot; file (by using the &quot;File-&amp;gt;Open Sample&quot; command).&lt;br /&gt;&lt;br /&gt;

A line break is automatically output after each formatting line, unless the &quot;Add line breaks after each line&quot; file option is unset.  In addition, the &quot;Add blank lines between nodes&quot; file option determines whether there is also an automatic blank line between node outputs. A line break tag (&quot;&amp;lt;br&amp;gt;&quot;) can be used at the end of the formatting to get the same effect, or a horizontal line tag (&quot;&amp;lt;hr&amp;gt;&quot;) may be used instead to separate the nodes.</Text>
<Ref>format-html</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Formatting Examples</Topic>
<Text>Here is an example of output formatting for a book list:&lt;br /&gt;&lt;br /&gt;

&amp;lt;hr/&amp;gt;&quot;{*Title*}&quot;&lt;br /&gt;
(c) {*Copyright*}, Rating: {*Rating*}&lt;br /&gt;
{*PlotDescription*}&lt;br /&gt;&lt;br /&gt;

Sample files with various kinds of formatting are included in the program distribution.  They can be opened by using the &quot;File-&amp;gt;Open Sample&quot; command.  They are also listed in the &lt;a href=&quot;#start-example&quot;&gt;Example Files&lt;/a&gt; section.</Text>
<Ref>format-example</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Other Field References</Topic>
<Text>References to fields that are not contained within the node can be added to the output.  Pushing the &quot;Show Advanced&quot; button on the &quot;Output&quot; tab of the configure dialog makes a reference level selection become visible.&lt;br /&gt;&lt;br /&gt;

If the reference level is changed to &quot;File Info Reference&quot;, fields containing file meta-data can be added to the output.  These include the file name, path, size, and modified time. These are shown as &quot;{*!field_name*}&quot; in the title and output format editors.&lt;br /&gt;&lt;br /&gt;

There are field references to various ancestor nodes (parents, grandparents, etc.).  These require the data type of the reference to be specified.  This selection determines the field names that are available, but the data from any type with a matching field name will be shown in the output.  References to fields from parent and grandparent nodes are shown as &quot;{**field_name*}&quot; and &quot;{***field_name*}&quot;, respectively. There are also general ancestor references, shown as &quot;{*?field_name*}&quot;, that take data from the closest ancestor with a matching field.&lt;br /&gt;&lt;br /&gt;

References to child nodes can also be added.  These also require that the child data type be specified.  The child data becomes embedded in the parent output.  The child data is delimited with a separator string defined as a file option.  The separator defaults to a comma and a space, but can be set to &amp;lt;br&amp;gt; or anything else.&lt;br /&gt;&lt;br /&gt;

Finally, a &quot;Child Count&quot; reference can be added.  This field will show the number of children (&quot;Level1&quot; field) or grandchildren (&quot;Level2&quot; field) of a node.  These are shown as {*#Level1*} in the format editors.&lt;br /&gt;&lt;br /&gt;

For examples of these fields, see the &quot;sample_other_fields&quot; file (by using the &quot;File-&amp;gt;Open Sample&quot; command).</Text>
<Ref>format-refs</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Sibling Prefix and Suffix</Topic>
<Text>Pushing the &quot;Show Advanced&quot; button on the &quot;Type Config&quot; tab of the configure dialog makes a sibling text section become visible, with settings for sibling prefix and suffix tags.  These tags can often be left blank, but are useful for creating tables or bulleted lists.  These tags will be placed before and after sibling groups of the proper type.  For example, to create an output table, the sibling prefix tag could be set to &quot;&amp;lt;table border=&quot;1&quot;&amp;gt;&quot; and the suffix tag could be set to &quot;&amp;lt;/table&amp;gt;&quot;.  Then, the output format could be set to:&lt;br /&gt;&lt;br /&gt;

&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&quot;{*Title*}&quot;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;(c)  {*Copyright*}&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;&lt;br /&gt;

Also see the &quot;sample_table_booklist&quot; example file (by using the &quot;File-&amp;gt;Open Sample&quot; command).&lt;br /&gt;&lt;br /&gt;

Siblings should generally be of the same type, or at least have the same prefix and suffix tags.</Text>
<Ref>format-sibling-text</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Link Reference Field</Topic>
<Text>One of the fields for each type is designated as the link reference field.  By default, it is the first field in the list.  Pushing the &quot;Show Advanced&quot; button on the &quot;Type Config&quot; tab of the configure dialog shows the selector for this field.&lt;br /&gt;&lt;br /&gt;

The link reference field is used for internal link references and for the arrange and flatten by reference commands.  The contents of this field should generally be unique if usage of these functions is planned.</Text>
<Ref>format-link-ref</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Generic and Derived Types</Topic>
<Text>Data types can be set to derive their field settings from a generic type.  This allows types with different output formatting to always use the same set of fields.  Any changes to the generic's list of fields and field types are automatically reflected in the fields of all derived types.  This does not apply to a field's output formatting, which can still be set independently.&lt;br /&gt;&lt;br /&gt;

There are two methods for creating derived types.  First, a derived option can be selected when copying a type on the &quot;Type List&quot; tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot;.  Alternately, a generic type can be specified from the derived type's &quot;Type Config&quot; tab of the dialog if the advanced functions are shown.</Text>
<Ref>format-derived</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Conditional Types</Topic>
<Text>Conditional expressions can be used to automatically assign a data type based on each node's content.  Conditions can be assigned only to a generic type and its associated derived types.  This allows the automatic assignment of different output formatting or different icons depending on each node's field data.&lt;br /&gt;&lt;br /&gt;

The conditional dialog box is accessed from a button on the &quot;Type Config&quot; tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot; if the advanced functions are shown.  Each line of the condition includes a field, an operator and a comparison value (see &lt;a href=&quot;#fig-5&quot;&gt;Figure 5&lt;/a&gt;).  The operators include equality, greater than, less than, starts with, ends with, and contains.  There are also True and False operators that will toggle the type of all nodes simultaneously.&lt;br /&gt;&lt;br /&gt;

For special field types such as dates, times, and booleans, the comparison value should be entered in the same format that is used in the Data Editor window.  In general, the starts with, ends with, and contains operators should not be used for these special fields, since the comparison is done using an internal data representation.  Dates and times also support a special comparison value of &quot;now&quot;, which is always interpreted as the current date and time.&lt;br /&gt;&lt;br /&gt;

The &quot;Add New Rule&quot; button is used to add additional condition lines.  The lines can be joined with &quot;and&quot; or &quot;or&quot; operators.  The &quot;Remove Rule&quot; button deletes the last condition line.  If only a single line is present, the &quot;Remove Rule&quot; button completely removes the condition.&lt;br /&gt;&lt;br /&gt;

Conditions do not have to be set for all types in a family.  If no conditions are true for a node, the program will select a blank condition over a false one.&lt;br /&gt;&lt;br /&gt;

For an example, see the &quot;sample_conditional_todo&quot; file (by using the &quot;File-&amp;gt;Open Sample&quot; command).</Text>
<Ref>format-condition</Ref>
<FIGURE item="y">
<Topic>Conditional dialog picture</Topic>
<Caption>Figure 5:  Conditional Dialog</Caption>
<Picture>doc_condition.png</Picture>
<Ref>fig-5</Ref>
</FIGURE>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Copying Formats</Topic>
<Text>Another method for changing data type formatting is to copy the formats from another TreeLine file. This is done with the &quot;Data-&amp;gt;Copy Types from File&quot; command. All types from the chosen file are copied. Any types in the current file with matching names are overwritten, but types with unique names are retained.</Text>
<Ref>format-copy</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Field Types</Name>
<Ref>fields</Ref>
<TEXT_HEAD item="y">
<Topic>Field Options</Topic>
<Text>The field type and options are set in the &quot;Field Config&quot; tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot; (see &lt;a href=&quot;#fig-3&quot;&gt;Figure 3&lt;/a&gt;).  The field type may be set to text, number, choice, combination, auto choice, date, time, boolean, URL, path, internal link, executable link, unique ID, email, or picture.   Prefix and suffix text can be entered and will show up whenever the data is not blank.&lt;br /&gt;&lt;br /&gt;

There are also settings for text content handling that can be set to allow HTML rich text in the field data or to preserve line breaks (ignoring HTML code). If HTML rich text is used, carriage returns are ignored and non-escaped &quot;&amp;lt;&quot;, &quot;&amp;gt;&quot; and &quot;&amp;amp;&quot; symbols do not display. There is also a general option available that makes new fields default to HTML content.  For an example of rich text use, see the &quot;sample_char_format&quot; file (by using the &quot;File-&amp;gt;Open Sample&quot; command).&lt;br /&gt;&lt;br /&gt;

Several of the field types use a formatting string to define their output. For a list of available formatting characters, use the &quot;Format Help&quot; button. Entries in the data editor which do not match the format will cause the field name label to show in bold, and the output for that field will be replaced by &quot;#####&quot;.</Text>
<Ref>field-options</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Text Type</Topic>
<Text>The default field type is a text field. These fields are edited using edit boxes in the data editor view. The edit box height expands when redisplayed after adding several lines of text. The edit box height can also be set explicitly in the &quot;Field Config&quot; tab.</Text>
<Ref>field-text</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Choice, Combination and Boolean Types</Topic>
<Text>The choice and combination field types allow for the selection of text items from a pull-down edit list. The formatting strings for these types list the items separated with the &quot;/&quot; character (use &quot;//&quot; to get a literal &quot;/&quot; in an item). Choice is used to select a single item and combination to select multiple items. The pull-down edit list for combination allows items to be added or removed. Also, the initial text of an item can be typed and auto-completed.&lt;br /&gt;&lt;br /&gt;

The boolean field type is similar to choice, but defaults to options such as &quot;True/False&quot;, &quot;yes/no&quot; and &quot;1/0&quot;.&lt;br /&gt;&lt;br /&gt;

There is also an AutoChoice field type.  Like Choice, it provides pull-down selection items, but it does not have a formatting string.  The pull-down is automatically populated with all previously used entries.</Text>
<Ref>field-choice</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Number Type</Topic>
<Text>In the number type, special characters in the format define the display of the numbers.  The format uses a string of &quot;#&quot; (optional digit) and &quot;0&quot; (required digit) characters to define the output formatting. For example, pi formatted with &quot;#.#&quot; is &quot;3.1&quot; and formatted with &quot;00.00&quot; is &quot;03.14&quot;. Regardless of the formatting, digits to the left of the decimal point are not truncated, since that would display an incorrect result.  But use care to show enough decimal places (either optional or required) to avoid problems with round-off error.&lt;br /&gt;&lt;br /&gt;

The radix character can be specified as either &quot;.&quot;  or &quot;,&quot; to handle internationalization.  For use as a thousands separator, use &quot;\,&quot; or &quot;\.&quot;.  For example, a large number may be formatted as &quot;#\,###\,###.##&quot; or as &quot;#\.###\.###,##&quot;.  Press the &quot;Format Help&quot; button from the field format dialog for more formatting details. &lt;br /&gt;&lt;br /&gt;

Unlike most other formats, the number type also uses the output format for display in the Data Editor.  Of course, any new entry with a reasonable format is correctly interpreted (but the correct radix character must be used).</Text>
<Ref>field-number</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Date and Time Types</Topic>
<Text>In the date, and time field types, special characters in the formats are replaced by elements of the data, similar to number fields.  Press the &quot;Format Help&quot; button from the field format dialog for formatting details. &lt;br /&gt;&lt;br /&gt;

There are also formats for these types under &quot;Tools-&amp;gt;General Options-&amp;gt;Data Editor Formats&quot;. These control how these fields are displayed in the Data Editor view. Generally, entries in the data editor with various formats will be correctly interpreted regardless of this setting, but dates must use the correct day-month-year sequence. Also note that the date editor format does not support days of the week.  Entries which cannot be interpreted will cause the field name to show in bold.&lt;br /&gt;&lt;br /&gt;

A default initial field value of &quot;Now&quot; can be used to get a time-stamp of node creation.</Text>
<Ref>field-date</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Linking Types</Topic>
<Text>The URL, path, and email field types are used to create links in the output. URL is for a standard web link (defaults to http:// unless otherwise specified), path is for a local file link (defaults to file:///), and email is for a mail link (defaults to mailto:). When clicked in the output window. these links open an external browser or email program. In exported HTML, they act as regular links. Simply enter the desired full path (such as &quot;www.bellz.org/treeline/index.html&quot;) in the data editor. In Linux, setting the &quot;BROWSER&quot; environment variable to a string like &quot;mozilla %s&quot; will result in the desired browser being used.&lt;br /&gt;&lt;br /&gt;

There is also an internal link field type. It creates a clickable link in the Data Output window that selects the next node with matching text in its reference field. If link or reference fields contain multiple lines, each line is treated as a separate link or reference, respectively. If desired, the same field can be used as both the link and reference fields, so that clicking on a keyword in one node's field selects the next node that also has that keyword. If exported to HTML, the internal links function as links to page anchors, but, in cases with duplicate references, they only find the uppermost reference on the page instead of the next one.  For an example, see the &quot;sample_intern_links&quot; file (by using the &quot;File-&amp;gt;Open Sample&quot; command).&lt;br /&gt;&lt;br /&gt;

The ExecuteLink field type runs an external program when its link is clicked.  The command to run is given by the text of the field.  Or the field's prefix may contain the program name, so that the field's text is used for arguments or file names.  A general option can disable these links when security is a concern.&lt;br /&gt;&lt;br /&gt;

The picture field type will show a referenced picture in the output. Enter the path to a local image file in the data editor. Supported image types include JPEG and PNG.  GIF is support is optional - it may be supported depending on build options in the Qt library.  Of course, when exporting HTML, the picture will show as long as the browser supports the format.</Text>
<Ref>field-link</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Unique ID Type</Topic>
<Text>A Unique ID field type is automatically loaded with unique numbers. This is often useful for ensuring that the link reference field is always unique.&lt;br /&gt;&lt;br /&gt;

Initially, the field's format string is set to the desired first number in the series, with optional leading zeros and optional leading or trailing characters. The initial number and the extra characters are useful to avoid duplication of numbers in different files.  All nodes of the data type will get an automatically assigned ID. The field format string will always show the next available number, which will be given to the next new node of that type.</Text>
<Ref>field-unique</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Advanced Options</Topic>
<Text>The &quot;Show Advanced&quot; button in the &quot;Field Config&quot; tab of the &quot;Data-&amp;gt;Configure Types Dialog&quot; brings up additional settings.&lt;br /&gt;&lt;br /&gt;

Link fields can display alternate text in place of the target URL.  This is done by specifying an alternate text field.&lt;br /&gt;&lt;br /&gt;

There is also a setting to flag fields as required to be filled in. Those fields will be marked with an asterisk in the data edit view.&lt;br /&gt;&lt;br /&gt;

Fields can also be set as hidden, to prevent them from showing in the data edit view.</Text>
<Ref>field-advanced</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Tree Data Manipulation</Name>
<Ref>data</Ref>
<TEXT_HEAD item="y">
<Topic>Category-based Commands</Topic>
<Text>The &quot;Data&quot; menu contains commands for arranging and flattening the data by category and by reference. These methods are used to automatically add and remove levels of nodes below the current node in the tree.&lt;br /&gt;&lt;br /&gt;

The &quot;Add Category Level&quot; command allows you to select one or more of the fields that the child nodes have in common. These fields are used to create new parent nodes for the children, grouping them by common categories. For example, in a list of books, picking the &quot;author_first_name&quot; and &quot;author_last_name&quot; fields will result in a tree with the books under new nodes for each unique author.&lt;br /&gt;&lt;br /&gt;

The &quot;Flatten by Category&quot; command is almost the opposite of &quot;Add Category Level&quot;. It eliminates any descendant nodes with children, transferring their data fields to their children. It will rename fields instead of overwriting data with the same field names, but this command is most useful when the children and parents are different types with unique field names.</Text>
<Ref>data-category</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Reference-based Commands</Topic>
<Text>The &quot;Arrange by Reference&quot; and &quot;Flatten by Reference&quot; commands arrange data nodes by using pointers to the value of their parent's reference data field. These commands rely on nodes having unique values in the reference field, such as an ID number. The &quot;Flatten by Reference&quot; command adds a field containing the parent's ID to each descendant node. It then places all of the nodes under the selected root node. The &quot;Arrange by Reference&quot; command does the opposite, placing each node under the parent with the referenced ID. If there are multiple nodes with the same ID, the nearest node above the child is chosen. Any nodes with lost parents are placed directly under the selected root node.&lt;br /&gt;&lt;br /&gt;</Text>
<Ref>data-ref</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Sorting</Topic>
<Text>The &quot;Data-&amp;gt;Sort&quot; command brings up the sort dialog.  It contains options for sorting the entire tree, the selected branches, the selection's children or the selection's siblings. The sorting can be based on specific fields within specified types or on titles only.&lt;br /&gt;&lt;br /&gt;

Sorting by types allows the selection of several fields to be used as the first key, second key, etc.  Multiple types can be selected in the list on the left.  The fields that the selected types have in common are listed on the right.  The fields to be used as keys are selected in order with the left mouse button and the direction is changed with the right mouse button.</Text>
<Ref>data-sort</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Filtering</Topic>
<Text>The &quot;Data-&amp;gt;Conditional Filter&quot; command limits the display of nodes in the flat view based on user-defined rules.  First, the type to be filtered is selected. Next, logical rules may be entered based on any of the type's fields (similar to &lt;a href=&quot;#fig-5&quot;&gt;Figure 5&lt;/a&gt;). Multiple rules can be linked by the &quot;and&quot; and &quot;or&quot; operators (press the &quot;Add Rule&quot; button). The &quot;True&quot; rule can be used to show all of the nodes of a given type.  Only descendant nodes that match the rules will be shown in the &quot;Flat View&quot; pane.  The filtering stays in effect for the &quot;Flat View&quot; pane until it is cleared using the &quot;Data-&amp;gt;Clear Filtering&quot; command (see &lt;a href=&quot;#fig-6&quot;&gt;Figure 6&lt;/a&gt;).&lt;br /&gt;&lt;br /&gt;

The &quot;Data-&amp;gt;Text Filter&quot; command works similarly, except it only prompts for a text search string. Only the nodes that have a match for that string somewhere in their field data are displayed in the &quot;Flat View&quot;.  Again, the filtering stays in effect for the &quot;Flat View&quot; pane until it is cleared using the &quot;Data-&amp;gt;Clear Filtering&quot; command.</Text>
<Ref>data-filter</Ref>
<FIGURE item="y">
<Topic>Filtering picture</Topic>
<Caption>Figure 6:  Filter Results</Caption>
<Picture>doc_filter.png</Picture>
<Ref>fig-6</Ref>
</FIGURE>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Numbering</Topic>
<Text>The &quot;Numbering&quot; command is used to add number fields to descendant nodes. The number fields do not automatically update when the tree is modified - the &quot;Numbering&quot; command must be repeated. In the dialog, a new or existing field name is entered, and the root (selected) node may be included in the numbering if desired. One of three styles may be chosen: outline style restarts numbering for each group of children, section style appends the child's number onto the parent's number, and single level style numbers only the first level of children. The default formats can be used (&quot;I, II..., A, B..., 1, 2...&quot; for outlines; &quot;1, 2..., 1.1, 1.2...&quot; for sections), or custom formats may be specified for each level. The custom formats should contain one of the following characters: &quot;1&quot;, &quot;A&quot;, &quot;a&quot;, &quot;I&quot;, or &quot;i&quot;. The series will continue from there (using numbers, letters or Roman numerals, respectively). The last occurrence of one of these characters in the format string is used - previous ones are assumed to be part of the format.</Text>
<Ref>data-number</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Change Selections</Topic>
<Text>Finally, the &quot;Change Selected Data&quot; command allows the values of a data field to be changed simultaneously for all selected nodes. Simply select the desired field and enter the new value.  To erase field values, enter a character then delete it - this will indicate that a blank field is desired.</Text>
<Ref>data-change</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Printing</Name>
<Ref>print</Ref>
<TEXT_HEAD item="y">
<Topic>Print Options</Topic>
<Text>The &quot;File-&amp;gt;Print Options dialog's first tab is &quot;General Options&quot;.  On the left, printing of the entire tree, the selected branches (all descendants) or the selected nodes can be selected.  The first two options print all of the descendants with the children indented.&lt;br /&gt;&lt;br /&gt;

On the right are options for drawing tree structure lines, including the root node, including only open children and keeping the first child with its parent.  The tree structure lines are drawn to connect parent and child nodes. They can make parent/child relationships easier to visualize, especially across multiple pages. The lines may not display as desired when using some HTML formatting tags.&lt;br /&gt;&lt;br /&gt;

By default, TreeLine will avoid breaking pages between a parent and its first child.  This behavior can be disabled by disabling the &quot;Keep first child with parent&quot; option.</Text>
<Ref>print-options</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Page Setup</Topic>
<Text>The second tab of the &quot;Print Options&quot; dialog box is &quot;Page Setup&quot;.  On the left are settings for page size, orientation and units.  On the right are settings for columns, indent offsets, and margins.</Text>
<Ref>print-setup</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Printer Font</Topic>
<Text>The third tab of the &quot;Print Options&quot; dialog box is &quot;Font Selection&quot;.  The printout will use the same font as the &quot;Data Output&quot; pane if the upper check box is checked.  If it is unchecked, a font can be selected specifically for printing.</Text>
<Ref>print-font</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Header and Footer</Topic>
<Text>The fourth tab on the &quot;Print Options&quot; dialog is used to set the print header and footer. There are file info fields on the left and six header/footer edit boxes (left, center and right justified) on the right. These fields can be added and combined with other text in the edit boxes, just like in the &quot;Output&quot; tab of the &quot;Data-&amp;gt;Configure Data Types&quot; dialog. The header and footer settings are saved with the TreeLine file.</Text>
<Ref>print-header</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Print Preview</Topic>
<Text>The print preview window can be shown by using the &quot;File-&amp;gt;Print Preview&quot; menu or with the button on the &quot;Print Options&quot; dialog.  Buttons on the window are used to navigate between pages, open the &quot;Print Options&quot; dialog, or open the print dialog.  The print preview will show more detail if its window is made larger.</Text>
<Ref>print-preview</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Printing Problems</Topic>
<Text>Some printing problems, especially problems with margins and word-wrapping, can be eliminated by changing the print font to a font that is better supported by the printer.</Text>
<Ref>print-problems</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>File Handling</Name>
<Ref>file</Ref>
<TEXT_HEAD item="y">
<Topic>File Compression</Topic>
<Text>A TreeLine file is in an XML text format. There are also options to work with compressed files (gzip format) to save space. Individual files can be set to compressed mode from either &quot;Tools-&amp;gt;File Options&quot; or from the save-as dialog. There is also a general option to set the default mode for new files.</Text>
<Ref>file-comp</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>File Encryption</Topic>
<Text>There is a file encryption option to password protect TreeLine files. Individual files can be set to encrypted mode from either &quot;Tools-&amp;gt;File Options&quot; or from the save-as dialog. There is also a general option to set the default for new files. The encryption uses the SHA hash function as a stream cipher - it should be fairly secure.</Text>
<Ref>file-enc</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Auto-Save</Topic>
<Text>An auto-save feature can store unsaved files with a &quot;~&quot; appended to the file name. The backup files are automatically removed when the file is saved or TreeLine exits cleanly. The auto-save time interval is set in the general options. Setting the interval to zero disables this feature.</Text>
<Ref>file-auto-save</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Saved Tree States</Topic>
<Text>When opening a recently used file, TreeLine will restore the states of open and selected nodes. This information is stored in the user's TreeLine configuration file. If desired, this feature can be disabled with a general option.</Text>
<Ref>file-states</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Command Line</Topic>
<Text>Command line options allow non-interactive file importing and exporting. This allows automated runs to be scheduled. For more details, run &quot;treeline -h&quot; (or &quot;treeline_dos -h&quot; in Windows) from the command line.</Text>
<Ref>file-cmdline</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>File Import</Name>
<Ref>import</Ref>
<TEXT_HEAD item="y">
<Topic>General Information</Topic>
<Text>A TreeLine file is in an XML text format. Other types of text files can be imported simply by opening them. Opening a file that is not valid TreeLine XML will result in a prompt for the type of import desired.</Text>
<Ref>import-general</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Delimited Text</Topic>
<Text>TreeLine will open a text file with a tree structure represented by tabs before each line. In this case, only the node title is imported, without any extra fields.&lt;br /&gt;&lt;br /&gt;

A tab-delimited table can also be imported. It becomes a single level of children under the root node, with each node containing fields from each table column. The first row of the table is used as field names and each subsequent row becomes a node.</Text>
<Ref>import-delim</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Plain Text</Topic>
<Text>There are two types of plain text import. One creates a separate node for each line in the file. The other creates a node for each paragraph, assuming the paragraphs are separated by blank lines. In both cases, the resulting TreeLine file will have all of the text under a single parent, but it is a good starting point. Additional structure can be added later.</Text>
<Ref>import-plain</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Treepad Files</Topic>
<Text>There is also a filter to import files from the Treepad shareware program.  Only Treepad text nodes are supported.</Text>
<Ref>import-treepad</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Bookmark Files</Topic>
<Text>TreeLine will import bookmark files in both the Mozilla HTML format (Mozilla, Firefox and Netscape browsers) and the XBEL format (Konqueror, Galeon and Elinks browsers). Each bookmark becomes a node with a name and a link field. Some information in the files, such as visited dates and icon references, is not imported.  For an example, see the &quot;sample_bookmarks&quot; file (by using the &quot;File-&amp;gt;Open Sample&quot; command).</Text>
<Ref>import-bookmarks</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Generic XML</Topic>
<Text>TreeLine will import and export generic XML files. These routines do not have much intelligence - each XML element becomes a node and each XML attribute becomes a field. XML text content become fields named &quot;Element_Data&quot;. This lets TreeLine function as a crude XML editor.</Text>
<Ref>import-xml</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>ODF Text Document</Topic>
<Text>TreeLine will import Open Document Format (ODF) text documents, from applications such as OpenOffice.org and KWord.   The node structure is formed based on the heading styles assigned in the document. Any text under each heading is assigned to that heading's node. The import filter is intended for simple text outlines only.  No formatting is maintained, and objects such as tables and pictures are not imported.</Text>
<Ref>import-odf</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>File Export</Name>
<Ref>export</Ref>
<TEXT_HEAD item="y">
<Topic>General Information</Topic>
<Text>Files are exported using the &quot;File-&amp;gt;Export&quot; command. This will show a dialog box of available export types and options.</Text>
<Ref>export-general</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>HTML</Topic>
<Text>Single-file HTML output is similar to printing, with similar options. It can include the print header and footer in the HTML, and the number of columns can be set.&lt;br /&gt;&lt;br /&gt;

There are also two multiple-file HTML export functions that create directory structures. Directories are named for the content of the reference data field, which must contain legal file names and not have duplicates under the same parent. The first form creates a table in each HTML file that contains the data for a set of siblings, as well as links to the parent and child pages.  The second form creates an HTML page for every node, with a navigation pane on the left side of each page that contains links to the node's parent, uncles and children.</Text>
<Ref>export-html</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Delimited Text</Topic>
<Text>Data can be exported to tabbed title text and tab-delimited tables. These formats are the same as the corresponding import formats. When exporting to a table, only the first level of children is used, so you may wish to flatten the data before exporting.</Text>
<Ref>export-delim</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Bookmark Files</Topic>
<Text>TreeLine will export bookmark files in both the Mozilla HTML format (Mozilla, Firefox and Netscape browsers) and the XBEL format (Konqueror, Galeon and Elinks browsers).</Text>
<Ref>export-bookmarks</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Generic XML</Topic>
<Text>TreeLine will import and export generic XML files. These routines do not have much intelligence - each node becomes an XML element and each field becomes an XML attribute, except for fields named &quot;Element_Data&quot; that become the element's text. This lets TreeLine function as a crude XML editor.</Text>
<Ref>export-xml</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>XSLT</Topic>
<Text>In addition to exporting data, the format for a file can be exported to an XSLT file. This can be used to display the XML data from a native TreeLine file in a compliant browser without exporting the data to HTML. Recent versions of most browsers are XSLT compliant. Note that complex field type formatting will be ignored by the XSLT.&lt;br /&gt;&lt;br /&gt;

When exporting to XSLT, a link to the XSL file is added to the TreeLine file.  Note that the TreeLine file must then be saved. In general, the TreeLine file should have a .xml extension so that the TreeLine file can be opened directly in a compliant browser. After that, the XSL file does not need to be re-exported for data changes (only for formatting changes).&lt;br /&gt;&lt;br /&gt;

If HTML tags are used in data formats that will be exported to XSLT, they should use xHTML style (&amp;lt;br /&amp;gt; instead of &amp;lt;br&amp;gt;). When exporting, there is a prompt for the name of an optional style sheet (css). This name is stored in the TreeLine file as the default for future exports. Also, the reference to the XSLT file in the TreeLine file may be removed with the &quot;Tools-&amp;gt;Remove XSLT Reference&quot; command.</Text>
<Ref>export-xslt</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>ODF Text Document</Topic>
<Text>TreeLine will export an outline to an Open Document Format (ODF) text document, compatible with OpenOffice.org and KWord. The title of each node is assigned a heading style at the appropriate level. Any other text in the output of each node becomes normal text under the heading. The export filter is intended for simple text outlines only.  Any HTML formatting is stripped, and objects such as tables and pictures are not supported.</Text>
<Ref>export-odf</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Customizations</Name>
<Ref>custom</Ref>
<TEXT_HEAD item="y">
<Topic>Options</Topic>
<Text>TreeLine's behavior can be modified with several settings available in &quot;Tools-&amp;gt;General Options&quot;.  Most of these options are covered elsewhere in this document.&lt;br /&gt;&lt;br /&gt;

Under Windows, a &quot;treeline.ini&quot; file in the user's application settings directory is used by default to store the settings.  For portable use of TreeLine, that file can be manually moved to TreeLine's &quot;lib&quot; directory.  Once it exists, a &quot;treeline.ini&quot; file in the &quot;lib&quot; directory will be used and updated automatically if the file isn't also in the user's application settings directory.</Text>
<Ref>custom-options</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Fonts</Topic>
<Text>Fonts used in the tree views, the output view and the editor views can be set in the &quot;Tools-&amp;gt;Set Fonts&quot; menu.</Text>
<Ref>custom-fonts</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Keyboard Shortcuts</Topic>
<Text>Keyboard shortcuts can be customized by using the &quot;Tools-&amp;gt;Set Keyboard Shortcuts&quot; command.  The shortcut editor has tabs for menu and non-menu based commands.  Simply type the new key sequence with the appropriate field selected.</Text>
<Ref>custom-keys</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Toolbars</Topic>
<Text>An editor to customize the toolbars is available from &quot;Tools-&amp;gt;Customize Toolbars&quot;.  The number of toolbars can be set and the buttons on each can be defined.</Text>
<Ref>custom-tools</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Colors</Topic>
<Text>User interface colors can be set using the last three items in the &quot;Tools menu.  If the &quot;Use Default System Colors&quot; command is enabled, the user background and text color settings are overridden.</Text>
<Ref>custom-color</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Tree Icons</Topic>
<Text>There is an icons directory in the user configuration directory (&quot;~/.treeline-1.x/icons&quot; on Linux, &quot;Documents and Settings\&amp;lt;user&amp;gt;\Application Data\bellz\treeline-1.x\icons&quot; on Windows).  Image files (PNG or BMP) placed into this directory are available for use as tree icons.</Text>
<Ref>custom-icons</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Plugins</Name>
<Ref>plugins</Ref>
<TEXT_HEAD item="y">
<Topic>Description</Topic>
<Text>TreeLine has an interface to plugin extension modules. This allows extensions to be written by various coders that provide functionality needed by a few users without adding bloat to the main application. The plugins can add new menu items, access the TreeLine data and read and write TreeLine Files.&lt;br /&gt;&lt;br /&gt;

Currently available plugins are listed on the &quot;Downloads&quot; page of the TreeLine web site.</Text>
<Ref>plugins-intro</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Installation</Topic>
<Text>The plugins are installed by copying their Python file (*.py) to a plugins directory.  This can be a directory in the TreeLine installation (&quot;&amp;lt;prefix&amp;gt;/lib/treeline/plugins/&quot; on Linux or &quot;TreeLine\lib\plugins\&quot; on Windows) or in the user configuration directory (&quot;~/.treeline-1.x/plugins/&quot; on Linux, &quot;Documents and Settings\&amp;lt;user&amp;gt;\Application Data\bellz\treeline-1.x\plugins\&quot; on Windows).  A list of loaded plugins can be found using the &quot;Help-&amp;gt;About Plugins&quot; command.</Text>
<Ref>plugins-install</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Interface</Topic>
<Text>Information about writing new plugins can be found in the &quot;plugininterface.py&quot; file in the TreeLine source code.</Text>
<Ref>plugins-intrf</Ref>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>Common Problems</Name>
<Ref>errors</Ref>
<TEXT_HEAD item="y">
<Topic>Closed Panes</Topic>
<Text>If one of the view panes is not visible when it should contain data, it has probably been collapsed to a size of zero.  This can apply to the left pane and to the upper and lower right panes.  To fix this, look for a thin stripe along one of the view borders that can be dragged back into its proper position.</Text>
<Ref>errors-panes</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>XML Error</Topic>
<Text>An error message, &quot;Error loading XML Parser&quot;, typically means that TreeLine could not find a necessary XML library. Under Linux, Python uses external libraries for parsing. Installing either the expat library or the PyXML package should fix the problem. Under Windows, Python includes a parser, so this error should not be seen unless files are missing or corrupt.</Text>
<Ref>errors-xml</Ref>
</TEXT_HEAD>
<TEXT_HEAD item="y">
<Topic>Printing</Topic>
<Text>Some printing problems, especially problems with margins and word-wrapping, can be eliminated by changing the print font to a font that is better supported by the printer.</Text>
<Ref>errors-print</Ref>
</TEXT_HEAD>
</HEADING3>
</HEADING2>
<HEADING2 item="y">
<Name>Revision History</Name>
<Ref>revs</Ref>
<HEADING3 item="y">
<Name>April 14, 2011 - Release 1.4.0 (new stable release)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Stable release</Topic>
<Text>This is a new stable release, ending the 1.3.x development series.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Translations</Topic>
<Text>This release is available in English, French and German, although the French documentation is not completely up to date.   Volunteers to do additional translations are welcome.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>File browser path</Topic>
<Text>The file browser used for editing path-based fields now remembers the previously used directory.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Toolbar icons</Topic>
<Text>Added icons for the New Window and Close Window commands so they can be added to toolbars.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>HTML export columns</Topic>
<Text>Fixed a bug that could keep the column control from being enabled during HTML export.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Major New Features Since 1.2.x:</Name>
<TEXT_BULLETS item="y">
<Topic>Multiple document interface</Topic>
<Text>Different files can be open in multiple TreeLine windows within the same TreeLine session.  This is controlled with commands in the new &quot;Window&quot; menu.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Multiple views of same file</Topic>
<Text>The &quot;Window-&gt;New Window&quot; command creates a new window with views of the same TreeLine file.  Changes in either window are saved in the same document.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Attach to session</Topic>
<Text>Starting TreeLine (from a shortcut, file association or command line) will activate an existing TreeLine session if it is already running.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Insert inline links</Topic>
<Text>An &quot;Add internal link&quot; context menu has been added to text boxes in the data editor.  It prompts for another node to be clicked with the mouse, then an inline internal link is added with that node's reference information.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML directory page export</Topic>
<Text>Added an &quot;HTML directory pages&quot; export option.  This will export a directory structure with an HTML file for every node.  A navigation pane on the left side of each page contains links to nearby nodes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Restore interface defaults</Topic>
<Text>New dialog buttons will restore the default configuration when customizing toolbars or shortcuts.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Help viewer search function</Topic>
<Text>A new text search function has been added to the help viewer.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>January 5, 2011 - Release 1.3.5 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It may contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.2.x) should be used for critical work.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Code cleanups</Topic>
<Text>Incorporated some minor code clean-ups (thanks to Erik Wegner for identifying them).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows binary</Topic>
<Text>The Windows binary is now based on the Python 2.7, Qt 4.7 and PyQt 4.8 libraries.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Sorting by type</Topic>
<Text>Fixed incorrect sorting by type with siblings of mixed types.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Print preview</Topic>
<Text>Fixed problems showing child lines in print previews if the lines option was changed with the preview open.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Rename option</Topic>
<Text>Really disable click-to-rename if the general option is unselected.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>September 22, 2010 - Release 1.3.4 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It may contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.2.x) should be used for critical work.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Icon image formats</Topic>
<Text>Added ico and gif as valid tree icon types.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>French translation</Topic>
<Text>The French GUI translation has been updated, but the documentation translation is still out of date.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>German translation</Topic>
<Text>Minor updates have been made to the German GUI translation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows binary</Topic>
<Text>The Windows binary is now based on the Python 2.7 library.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Window menu</Topic>
<Text>The list of windows in the Window menu is now properly updated after saving a file with a new name.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check</Topic>
<Text>Fixed a bug that could cause spell checks to hang.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>June 24, 2010 - Release 1.3.3 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It may contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.2.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>German translation only</Topic>
<Text>German is the only GUI and documentation translation that has been updated so far.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Help viewer search function</Topic>
<Text>A new text search function has been added to the help viewer.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data Editor view paging shortcut</Topic>
<Text>The keyboard shortcuts for scrolling the right-hand views (Ctrl+Page Up and Ctrl+Page Down) now cycle through the Data Editor view pages if there is no more room to scroll</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>System requirements</Topic>
<Text>The Linux system requirements have been updated to indicate that Qt 4.4 or higher is now required.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows installer</Topic>
<Text>The Windows installer now sets the sample and readme documents to read-only status.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>German translation</Topic>
<Text>The German GUI and documentation translation has been updated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Window cascading</Topic>
<Text>The cascading of new windows has been fixed.  It now references the current position of the previous window, and it avoids cascading windows off of the screen.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data Editor resizing</Topic>
<Text>The Data Editor widgets are now sized correctly when TreeLine is started in Data Editor mode.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Depreciation warnings</Topic>
<Text>The spell checker and the Linux installation script have been updated to avoid subprocess command depreciation warnings.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 14, 2010 - Release 1.3.2 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It may contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.2.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Translations not updated</Topic>
<Text>The GUI and documentation translations have not yet been updated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Documentation</Topic>
<Text>Updated the ReadMe file to cover the new features added during this development cycle.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Save prompt</Topic>
<Text>Fixed a major bug that prevented files from being saved at the &quot;Save Changes?&quot; dialog when closing a modified file.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>April 8, 2010 - Release 1.3.1 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It may contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.2.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Documentation not updated</Topic>
<Text>The documentation has not yet been updated to cover the new features.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Translations not updated</Topic>
<Text>The GUI and documentation translations have not yet been updated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Window update command</Topic>
<Text>Added a menu command that updates another window containing the same file (without waiting for a focus change).  This command also has a keyboard shortcut (Ctrl+W).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Hiding the status bar</Topic>
<Text>A menu option has been added to hide the status bar. There is also a new general option to hide it at startup.  A hidden status bar is automatically shown temporarily for important messages.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Toolbar restore defaults</Topic>
<Text>A new button on the toolbar editing dialog will restore the default toolbar configuration.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Keyboard shortcuts restore defaults</Topic>
<Text>A new button on the keyboard shortcuts editing dialog will restore the default shortcut configuration.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Windows portability</Topic>
<Text>Portability on Windows has been improved.  A &quot;treeline.ini&quot; config file in TreeLine's &quot;lib&quot; directory will be used if it's present and there are no config files in the user's application data directory.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Change selected data</Topic>
<Text>The Change Selected Data command has been updated to use Data Editor formats for dates and times.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>DOS TreeLine executable file</Topic>
<Text>An alternate TreeLine executable file (treeline_dos.exe) has been added to make batch command-line operations work from Windows.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugin interface improvements</Topic>
<Text>Additional plugin methods have been added for handling files and languages.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Spell check</Topic>
<Text>Fixed a problem spell checking with older versions of aspell when Unicode characters were present.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>October 14, 2009 - Release 1.3.0 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and probably contains bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.2.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Documentation not updated</Topic>
<Text>The documentation has not yet been updated to cover the new features.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Translations not updated</Topic>
<Text>The GUI and documentation translations have not yet been updated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Multiple document interface</Topic>
<Text>Multiple TreeLine windows with different files can be open within the same TreeLine session.  The &quot;Open files in new windows&quot; general option controls whether new windows are used when opening or creating files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Window menu</Topic>
<Text>A &quot;Window&quot; menu has been added with commands to create new windows, close windows, or select from a list of current windows.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Multiple views of same file</Topic>
<Text>The &quot;Window-&gt;New Window&quot; command creates a new window with views of the same TreeLine file.  Changes in either window are saved in the same document.  This can be used to work in different sections of the file simultaneously.  For performance reasons, the non-active window does not show the changes made in the active window until the non-active window is focused.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Attach to session</Topic>
<Text>Starting TreeLine (from a shortcut, file association or command line) will activate an existing TreeLine session if it is already running.  A new window will be opened if an unopened file was specified by file association or in the command line.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Insert inline links</Topic>
<Text>An &quot;Add internal link&quot; context menu has been added to text boxes in the data editor.  It prompts for another node to be clicked with the mouse, then an inline internal link is added with that node's reference information.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML directory page export</Topic>
<Text>Added an &quot;HTML directory pages&quot; export option.  This will export to a directory structure with an HTML file for every node.  A navigation pane on the left side of each page contains links to the node's parent, uncles and children.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>General options dialog to 3 columns</Topic>
<Text>The general options dialog has been split into three columns for better viewing on small, wide displays.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Add exports to plugin interface</Topic>
<Text>Additional export commands and export options have been added to the plugin interface.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>No initial default window position</Topic>
<Text>To avoid a problem on the Mac platform, when TreeLine is run for the first time, it lets the OS determine the window position.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>October 12, 2009 - Release 1.2.4 (stable release)</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>PyQt 4.6 workaround</Topic>
<Text>Added a work-around for a bug in PyQt 4.6's clipboard support that can prevent TreeLine from starting.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tree horizontal scroll</Topic>
<Text>Prevent an uncommanded horizontal scrolling to the left of the tree view when changing the selection.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 5, 2009 - Release 1.2.3 (stable release)</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Windows 98 compatibility</Topic>
<Text>A new build has been created for use on the Windows 98 operating system.  This fixes problems that made TreeLine 1.2.2 unusable on Windows 98.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Copy persistence</Topic>
<Text>Data copied to the Windows clipboard is now preserved after exiting from TreeLine.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Copy/paste error</Topic>
<Text>Fixed a bug on Windows that showed an error message at program exit if the copy command had been used during the session.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML directory export</Topic>
<Text>In an HTML directories export, characters that are illegal in directory names are now correctly removed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>January 8, 2009 - Release 1.2.2 (stable release)</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>German translation</Topic>
<Text>Added German translations of the GUI and the ReadMe file.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Translation updates</Topic>
<Text>Added a few missing strings to the translation files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Python 2.6 compatibility</Topic>
<Text>Substituted some imported modules to avoid deprecation warnings in Python 2.6.  Note that Python 2.3 is no longer supported.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows binary</Topic>
<Text>The windows binary has been updated to use Python 2.6, and the installer has been tweaked to reduce DLL conflicts.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Edit view tabbing</Topic>
<Text>Fixed problems using the tab key to change focus from the tree to the data editor.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>UniqueID fields in titles</Topic>
<Text>ID numbers are now properly assigned to new nodes with UniqueID fields in the title.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Child count in titles</Topic>
<Text>Fixed problems creating nodes with child count fields in the titles.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 4, 2008 - Release 1.2.1 (stable release)</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Rename input loss</Topic>
<Text>Fix the loss of entered text when the renaming of a node is ended by a command that changes the selected node.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Unicode file names</Topic>
<Text>Problems with opening files with Unicode file names from the command line or from a file association have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows JPEG support</Topic>
<Text>Fixed problems with JPEG and GIF image support in the Windows binary build.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tree view scrolling</Topic>
<Text>When commands change the tree view, it no longer scrolls vertically unless the current node is not visible.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Compressed encrypted files</Topic>
<Text>Fixed problems with files set to both compressed and encrypted modes.  But note that compressing an encrypted file still does not significantly reduce its size.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Mac support</Topic>
<Text>Problems on the Macintosh platform with detecting the text encoding and with setting the default theme have been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>June 17, 2008 - Release 1.2.0 (new stable release)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Stable release</Topic>
<Text>This is a new stable release, ending the 1.1.x development series.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Translations</Topic>
<Text>This release is only available in English and French.  The 1.0.2 release is still available, including German, Portuguese, Russian and Spanish translations.  Volunteers to update the translations are welcome.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>French GUI translation</Topic>
<Text>The French translations of the GUI and the ReadMe file have been updated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Replace with backup file</Topic>
<Text>When restoring an auto-saved backup file, TreeLine no longer replaces a the main file with the backup if the backup is not a valid TreeLine file.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Configure dialog</Topic>
<Text>Fixed a minor bug in the Configure Data Types dialog caused by unselecting a field in the Output pane.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Major New Features Since 1.0.x:</Name>
<TEXT_BULLETS item="y">
<Topic>Ported to Qt4</Topic>
<Text>TreeLine was extensively rewritten to port it to the Qt4 library (previous versions used Qt3.x on Linux and Qt2.3 on Windows).  Benefits include updated widgets and removal of the non-commercial license exception in Windows.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Templates</Topic>
<Text>Preformatted templates have been added for new TreeLine documents.  User-created templates can also be added.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Right view content</Topic>
<Text>The content of right-hand views varies based on the selection and other options.  A single selection still shows panes with the parent and its children, but a multiple selection will show all of the selected nodes in a single pane.  Also, the Data Output view can optionally show an indented view of all descendants, and the Data Editor view splits the display into pages to speed up display.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Multiple selection use</Topic>
<Text>More commands can make use of a multiple selection instead of just using the single active node.  Also, an option can set the sequence of showing and exporting multiple selections to either tree order or selection order.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Flat view and filtering</Topic>
<Text>There is a tab on the left-hand view for a flat node list showing the selected nodes and all of their descendants.  It is most useful for showing the results of filtering.  There is a conditional filter for specific rules and a text filter that searches all fields for a string.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Dialog changes</Topic>
<Text>Several dialogs have been reworked for usability.  The Configure Data Types and Print Options dialogs use tabs for better organization.  The Configure dialog also has initially hidden advanced features and is now modeless, so it can be left open while applying configuration changes.  The Sort, Export and Print Preview dialogs have also been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tree navigation</Topic>
<Text>Navigation through the tree is simplified by new commands that step through the selection history.  Also, search strings are now highlighted in the Data Output view for text searches.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Shortcuts and customization</Topic>
<Text>New dialogs have been added to customize keyboard shortcuts and tool bar buttons.  There is also a directory for user-defined tree icons.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>ODF</Topic>
<Text>New file import and export options convert between an outline and an Open Document Format (ODF) text document, compatible with OpenOffice.org and KWord.  Formatting is not maintained.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Unique ID fields</Topic>
<Text>A Unique ID field type has been added that is automatically loaded with unique numbers.  It is useful for link references.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>January 15, 2008 - Release 1.1.10 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is nearly ready to become a stable release, but it could still contain bugs.  Testing and bug reports are appreciated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>The French translation of the GUI is the only one completed so far.  None of the documentation translations  have been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages may not be available yet for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Delete old config file</Topic>
<Text>If you've installed previous development releases, it is recommended that you delete the old configuration file (&quot;~/.treeline-1.1/treelinerc&quot; on Linux, &quot;Documents and Settings\&amp;lt;login&amp;gt;\Application Data\bellz\treeline-1.1\treeline.ini&quot; on Windows) before running this release.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>HTML directories export</Topic>
<Text>Exporting to HTML directories has been improved.  The file names are generated from the reference field (were from the first field).  Internal links to nodes now work properly in the exported files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Save as default directory</Topic>
<Text>When saving a new file, the Save-As dialog now defaults to the top directory in the recent file list.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>French GUI translation</Topic>
<Text>A translation of the GUI in French is now available.  The i18n installation file is a separate download.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Documentation</Topic>
<Text>The ReadMe documentation file has been updated to clarify certain usage issues.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Setting files to generic</Topic>
<Text>The other controls in the configuration dialog are updated immediately when setting a data type to be derived from a generic.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Fix http load plugin</Topic>
<Text>A recent file list bug that affected the httpload plugin has been fixed.  Also, a library need by the plugin (urllib) has been added to the Windows installation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Status bar error</Topic>
<Text>An error message about removing a status bar widget has been eliminated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Mac encoding error</Topic>
<Text>An error on a Mac when setting the language encoding has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Unicode file paths</Topic>
<Text>Various issues with file paths containing Unicode characters have been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>June 13, 2007 - Release 1.1.9 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It could contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>The translations of the GUI and of the documentation have not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Delete old config file</Topic>
<Text>If you've installed previous development releases, it is recommended that you delete the old configuration file (&quot;~/.treeline-1.1/treelinerc&quot; on Linux, &quot;Documents and Settings\&amp;lt;login&amp;gt;\Application Data\bellz\treeline-1.1\treeline.ini&quot; on Windows) before running this release.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Filter result selection</Topic>
<Text>Initially select the top filtering result in the flat view to avoid issues with a blank selection.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Flat view rename</Topic>
<Text>Avoid entering rename mode when clicking on a multiple selection in the flat view.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Icon dialog size</Topic>
<Text>Maintain the size of the type icon dialog during a session.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Print unit options</Topic>
<Text>Remove the redundant printing units option from the general options dialog.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Documentation</Topic>
<Text>Extensively update the ReadMe documentation to match the current feature set.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>TODO template</Topic>
<Text>Add a new file template for TODO lists.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Paste references</Topic>
<Text>Fix incorrect internal references in groups of pasted nodes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tree rename</Topic>
<Text>Abort a tree rename operation if the new name does not match the title format.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Add numbering field</Topic>
<Text>Correctly add a field to the generic type when numbering a derived type.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Update field choices</Topic>
<Text>Properly update the pull-down choices for a choice or combination field after a configuration change.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Enable conditional type button</Topic>
<Text>Enable the conditional type button immediately after defining a type as derived.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Remove page number field</Topic>
<Text>Remove the page number field from the available file reference fields in the main configuration settings.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Filter menu update</Topic>
<Text>Properly update the Data menu after starting a filtering operation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing language code</Topic>
<Text>Fix an error due to a missing system language setting.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Unknown field type</Topic>
<Text>Properly handle a file open error due to an unknown field type.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 22, 2007 - Release 1.1.8 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It probably contains bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>The documentation and GUI translations have not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Delete old config file</Topic>
<Text>If you've installed previous development releases, it is recommended that you delete the old configuration file (&quot;~/.treeline-1.1/treelinerc&quot; on Linux, &quot;Documents and Settings\&amp;lt;login&amp;gt;\Application Data\bellz\treeline-1.1\treeline.ini&quot; on Windows) before running this release.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Command line ODF translation</Topic>
<Text>Translation of ODF text documents has been added to the command line batch processing options.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Use LC_MESSAGES for language</Topic>
<Text>The environment variable LC_MESSAGES is now checked before the LANG variable to determine the user's preferred language.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Problem with Unicode user name (option file)</Topic>
<Text>Problems writing the options file when there are Unicode characters in the username have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Miscellaneous Unicode bug fixes</Topic>
<Text>Various minor bugs in Unicode handling have been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 3, 2007 - Release 1.1.7 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and probably contains bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>The documentation and GUI translations have not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Delete old config file</Topic>
<Text>If you've installed previous development releases, it is recommended that you delete the old configuration file (&quot;~/.treeline-1.1/treelinerc&quot; on Linux, &quot;Documents and Settings\&amp;lt;login&amp;gt;\Application Data\bellz\treeline-1.1\treeline.ini&quot; on Windows) before running this release.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Templates</Topic>
<Text>Preformatted templates have been added.  The File-&amp;gt;New command brings up a dialog with a list of available templates.  The dialog is also shown at startup if the recent file list is empty.  Default templates are installed into TreeLine library directories.  New templates can be added to a user templates directory in the user settings location.  Template file names consist of a number for sorting, a language code and the name of the template.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Native Save As dialog</Topic>
<Text>The Save As dialog in Windows is now the native dialog.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>ODF export</Topic>
<Text>Problems exporting to an ODF text document when blank fields are encountered have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Installer error messages</Topic>
<Text>Added appropriate error messages to the Linux installer if some installer files are not found.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>April 17, 2007 - Release 1.1.6 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and probably contains bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.x) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>The documentation and GUI translations have not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Delete old config file</Topic>
<Text>If you've installed previous development releases, it is recommended that you delete the old configuration file (&quot;~/.treeline-1.1/treelinerc&quot; on Linux, &quot;Documents and Settings\&amp;lt;login&amp;gt;\Application Data\bellz\treeline-1.1\treeline.ini&quot; on Windows) before running this release.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Descendants in output view</Topic>
<Text>A new command (View-&amp;gt;Show Output Descendants) toggles the Data Output child view from showing only child nodes to showing an indented view of all descendant nodes.  A button was added to the default toolbar for this command.  Also, a new general option can make the descendant view the default at startup.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>ODF export</Topic>
<Text>A new file export option converts an outline to an Open Document Format (ODF) text document, compatible with OpenOffice.org and KWord.  The title of each node is assigned a heading style at the appropriate level.  Any other text in the output of each node becomes normal text under the heading.  Any HTML formatting is stripped.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>ODF import</Topic>
<Text>ODF text documents can be imported.  The node structure is based on the heading styles assigned in the document.  Any text under each heading is assigned to that heading's node.  Formatting is not maintained.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Modify config from Data Editor context menu</Topic>
<Text>New commands were added to the Data Editor context menus that open the Configure Data Types dialog with the editor's type and/or field already selected.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Shortcuts for editor html tag commands</Topic>
<Text>Keyboard shortcuts were added for the commands that add HTML tags in the Data Editor.  Icons were also added to these commands, so the toolbar editor can be used to place them on a toolbar if desired.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugin improvements</Topic>
<Text>The interface for writing plugin modules was improved by adding interfaces to the keyboard shortcut editor and the toolbar editor. Also, a plugin interface to get the plugin's directory was added.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Default field text</Topic>
<Text>Any default text for new fields is added when a node's data type is changed (not just to a new node), as long as there isn't already data in a field with the same name.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Auto open problem</Topic>
<Text>Fixed a problem with the automatic opening of the last file used if there are no valid recent files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Crash if user ID not found</Topic>
<Text>Fixed a crash at file open if the file's owner is not found in a Linux machine's user password database.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Text display issues</Topic>
<Text>Issues with the display of text  have been fixed if the Qt library being used is version 4.2.3  or greater (the Windows build now uses 4.2.3).  These issues showed up when scroll bars were shown and could hide the right edge of the text or the last line.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Paste or drag nodes from other session</Topic>
<Text>Multiple issues with dragging or pasting nodes between sessions of TreeLine were fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Undo updates an open config dialog</Topic>
<Text>If the Configure Data Types dialog is open, it is properly updated after the use of the undo command.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Find dialog focus</Topic>
<Text>The find dialog is properly focused when repeatedly shown.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Printing no nodes</Topic>
<Text>Fixed problems occurring when attempting to print an empty branch or an empty selection.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML directory export</Topic>
<Text>Fixed problems with the export of HTML directories.  It now removes illegal characters from directory names created from field contents.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Auto choice field updates</Topic>
<Text>Auto choice fields are now properly updated after configuration changes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Unique ID field help</Topic>
<Text>A missing help menu was added to the Unique ID field format editor.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>February 22, 2007 - Release 1.1.5 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and probably contains bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.0) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>The documentation and GUI translations have not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Delete old config file</Topic>
<Text>If you've installed previous development releases, it is recommended that you delete the old configuration file (&quot;~/.treeline-1.1/treelinerc&quot; on Linux, &quot;Documents and Settings\&amp;lt;login&amp;gt;\Application Data\bellz\treeline-1.1\treeline.ini&quot; on Windows) before running this release.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Unique ID fields</Topic>
<Text>A Unique ID field type has been added.  The field is automatically loaded with unique numbers.  Initially, the field's format string is set to the desired first number in the series, with optional leading zeros and optional leading or trailing characters.  All nodes of the data type will get an automatically assigned ID.  The field format string will always show the next available number, which will be given to the next new node of that type.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Sort dialog</Topic>
<Text>The node sorting commands have been consolidated into a single new dialog.  This provides more options for selecting what to sort (all nodes, branches, children or siblings) and how (by types and fields or by titles).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Selective numbering</Topic>
<Text>An option has been added to the numbering dialog to only number nodes where the number field already exists.  This allows node types in the branch that do not have the number field to be skipped.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Tree view scrolling</Topic>
<Text>The tree view no longer scrolls horizontally when the selection is changed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data Editor focus</Topic>
<Text>The focus behavior of the Data Editor view has been tweaked to allow easier tabbing between widgets.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>No multiple selection rename</Topic>
<Text>Clicking on a selected node to rename it is now disabled when multiple nodes are selected.  This avoids initiating a rename when the intent was to modify a multiple selection.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Insert sibling context menu</Topic>
<Text>The Insert Sibling Before command has been added to the node right-click context menu for consistency.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Smoother spell checking</Topic>
<Text>The Spell Check dialog is no longer hidden and re-shown between each misspelled word, resulting in smoother operation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Configure Data Types dialog</Topic>
<Text>The Output tab of the Configure Data Types dialog has been adjusted to avoid changing the dialog size when toggling the advanced options.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Print Options font selection</Topic>
<Text>The fonts in the Print Options dialog are sorted case insensitively, and the size of the dialog is fixed regardless of the selected font.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>File open from flat view</Topic>
<Text>Fixed a crash when opening a file with the flat view shown.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>No toolbars</Topic>
<Text>Fixed problems occurring when the number of toolbars was set to zero.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Undo of data commands</Topic>
<Text>Fixed undo operations for Numbering, data Add Category Level and Arrange by Reference commands.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Commands while renaming</Topic>
<Text>Fixed problems with undo and delete commands issued while a node is being renamed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Type and field renames</Topic>
<Text>Fixed problems with renaming data types and fields in the Configure Data Types dialog.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Reference types</Topic>
<Text>Avoid adding duplicate types to Other Field References in the advanced Output tab of the Configure Data Types dialog.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Cutting the root node</Topic>
<Text>No longer allow the Edit Cut command to operate if the root node is selected.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check freeze</Topic>
<Text>Fixed a freeze of the spell checker on some platforms.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Status line</Topic>
<Text>An empty rectangle that was sometimes shown on the status line at the bottom of the main window has been removed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Generic XML import</Topic>
<Text>An occasional problem with the import of generic XML was fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Import bad Unicode</Topic>
<Text>The importing of files with bad Unicode characters has been improved.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tree state restoring</Topic>
<Text>The restoring of tree states when opening a file has been made more robust.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Miscellaneous tracebacks</Topic>
<Text>Fixed several other minor tracebacks that can show up in a terminal or log file.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>January 18, 2007 - Release 1.1.4 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and is sure to contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.0) should be used for critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>The documentation and GUI translations have not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Selection history</Topic>
<Text>Previous and Next Selection commands have been added to the View menu.  These commands step through a history of tree selections for quicker navigation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Search highlighting</Topic>
<Text>When using the Find command with the Data Output view visible, the search string occurrences are highlighted in the output.  Note: in Linux, this feature requires Qt v4.2 or greater and PyQt v4.1 or greater.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>User icons</Topic>
<Text>An icons directory has been added to the user configuration directory (&quot;~/.treeline-1.1/icons&quot; on Linux, &quot;Documents and Settings\&amp;lt;user&amp;gt;\Application Data\bellz\treeline-1.1\icons&quot; on Windows).  Image files (PNG or BMP) placed into this directory are available for use as tree icons.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Move commands</Topic>
<Text>&quot;Move First&quot; and &quot;Move Last&quot; commands have been added to the Edit menu.  These commands move a child node to be the first or last child of its parent.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Tree scrolling</Topic>
<Text>Horizontal scrolling of the tree view when the contents are wide is now supported.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Command line</Topic>
<Text>The non-interactive command line options have been ported from the stable version.  These options allow batch processing of file imports and exports.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugin support</Topic>
<Text>Support for plugin extension modules has been ported from the stable version.  The interfaces to TreeLine functions are unchanged, but existing plugins will need to be ported to the Qt4 library.  An updated version of the httpLoad plugin is available.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>User plugin directory</Topic>
<Text>A plugins directory has been added to the user configuration directory.  This allows plugin installation without elevated privileges.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Translation support</Topic>
<Text>The code required to support GUI translations has been ported from the stable version, but the actual translations have not yet been updated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Windows copy/paste</Topic>
<Text>The problem with cut/copy/paste operations in Windows that produced an error message at application exit was fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data config undo</Topic>
<Text>Fixed several problems with the undo of changes to the Data Type Configuration.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Renaming nodes</Topic>
<Text>A bug that could sometimes add an extra node during renaming in the Tree View has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check replace</Topic>
<Text>Problems encountered when typing a replacement word during spell check have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check language</Topic>
<Text>A spell check language setting in File Options that is not available on the system is now ignored.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>December 21, 2006 - Release 1.1.3 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and is sure to contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.0) should be used for any critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>Some features from the stable release are not yet implemented here.  These include command line options, plugin support and translation support.  Also,  the documentation has not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Known bugs</Topic>
<Text>One known bug in the Windows version produces an error message at application exit if cut/copy/paste operations were done during the session.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Keyboard shortcut editor</Topic>
<Text>A new built-in editor for keyboard shortcuts has been added to the Tools menu.  It has two tabs:  one for menu commands and one for other commands.  Simply press the desired key combination to change the shortcut in the selected entry.  In general, printable characters without Ctrl or Alt modifiers should not be used for shortcuts.  Although the editor will accept them, they may not work properly when certain widgets are focused.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tool bar customization</Topic>
<Text>A dialog to customize the tool bars has been added.  It is accessed from the Tools menu.  This allows the user to select small or large icons, define the number of tool bars, and define the commands included in each tool bar.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Restoring node states</Topic>
<Text>The saving of node open/close states for recently opened files has been ported from the stable version.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Restoring split sizes</Topic>
<Text>The restoring of splitter sizes and the active right-hand tab from the previous session has been ported from the stable version.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Config file version</Topic>
<Text>The TreeLine configuration files now include a version number (.treeline-1.1 on Linux, treeline-1.1.ini on Windows) to avoid incompatibility issues with previous versions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>New keyboard shortcuts</Topic>
<Text>The default non-menu keyboard shortcuts have been changed to control-key sequences that function regardless of the focused widget.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Incremental search</Topic>
<Text>The incremental node title search has been ported from the stable version.  The default keyboard shortcut is now Ctrl+/.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Add node on enter</Topic>
<Text>The option to add a node when pressing the enter key has been ported from the stable version.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Flat view searching</Topic>
<Text>Searching for nodes with the flat view active now only finds nodes actually present in the flat view.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Drag &amp; drop fix</Topic>
<Text>Problems with drag &amp;amp; drop of nodes with Unicode content were fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Config dialog show icon</Topic>
<Text>The Icon Selection dialog under Configure Data Types now scrolls to the currently selected icon when opened.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 22, 2006 - Release 1.1.2 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Same</Topic>
<Text>All of the notes listed for Version 1.1.1 still apply.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Combo box crash</Topic>
<Text>Fixed a serious bug that caused TreeLine to crash when using a pull-down combo box on a field in the Data Editor view.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 21, 2006 - Release 1.1.1 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and is sure to contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.0) should be used for any critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>Several features from the stable release are not yet implemented here.  These include keyboard shortcuts for non-menu items, command line options, plugin support and translation support.  Also, restoring of tree node open/close states, window split locations and active tabs are not yet available.  And the documentation has not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Known bugs</Topic>
<Text>One known bug in the Windows version produces an error message at application exit if cut/copy/paste operations were done during the session.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Printing implemented</Topic>
<Text>Printing functionality has been added to the development series.  It now includes options to print the entire tree, the selected branches, or just the selected nodes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Printing interface</Topic>
<Text>A new Print Options dialog box is tabbed to give easier access to all of the options.  There are buttons that give a more logical progression from the options to the print preview and to the print dialog.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Configure dialog buttons</Topic>
<Text>The buttons at the bottom of the Configure Data Types dialog have been changed to OK/Apply/Reset/Cancel.  This can reduce the number of mouse clicks.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Initial configure dialog type</Topic>
<Text>The Configure Data Types dialog now defaults to the selected node's type when it is shown.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Moved .ini file</Topic>
<Text>On Windows, the TreeLine.ini file has been moved from the installation directory to a location under the &quot;Documents and Settings&quot; folder. This avoids problems on multi-user systems and for users with limited access rights.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Configure dialog updates</Topic>
<Text>The Configure Data Types dialog now updates properly after copying types from another file, adding numbering, and rearranging by category and reference.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Drag &amp; drop fix</Topic>
<Text>Various problems with node drag &amp;amp; drop that could result in inadvertent drops were fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Splitter height recall</Topic>
<Text>A bug that caused the right-hand view splitter to reset to even sizes was fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Saving file info field formats</Topic>
<Text>Problems with saving changes to the format of file information fields were fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Fixed help viewer issues</Topic>
<Text>Issues with some internal links and pictures in the help viewer were fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>September 12, 2006 - Release 1.1.0 (unstable development snapshot)</Name>
<HEADING4 item="y">
<Name>Notes:</Name>
<TEXT_BULLETS item="y">
<Topic>Development release</Topic>
<Text>This is an unstable development snapshot.  It is not feature complete and is sure to contain bugs.  Testing and bug reports are appreciated, but the stable release (TreeLine 1.0.0) should be used for any critical work.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Missing features</Topic>
<Text>Several features from the stable release are not yet implemented here.  These include printing, keyboard shortcuts for non-menu items, command line options, plugin support and translation support.  Also, restoring of tree node open/close states, window split locations and active tabs are not yet available.  And the documentation has not been updated.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Qt4 required</Topic>
<Text>On Linux, running TreeLine requires Qt version 4.1 or higher and PyQt version 4.0 or higher.  Binary packages are not yet available for these libraries in some distributions.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Known bugs</Topic>
<Text>One known bug in the Windows version produces an error message at application exit if cut/copy/paste operations were done during the session.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Ported to Qt4</Topic>
<Text>TreeLine was ported to the Qt4 library.  This involved a major rewrite of the code.  The previous versions used Qt3.x on Linux and Qt2.3 on Windows.  Benefits include updated widgets and removal of the non-commercial license exception in Windows.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tabbed config dialog</Topic>
<Text>The Configure Data Types dialog uses tabs for better organization.  Many tabs contain advanced features that can be shown if desired.  The dialog is also modeless, so it can be left open while applying configuration changes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Right view content</Topic>
<Text>The content of the right-hand view varies based on the kinds of nodes selected.  With a single parent node selected, it splits the view, showing the parent and its children (same as version 1.0.0).  With a multiple selection or with a childless node selected, it shows all of the selected nodes in a single pane.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Node selection sequence</Topic>
<Text>A general option sets the sequence for multiple selection to either tree order or selected order.  When nodes are selected with control-click under the selected order option, they show in the right-hand view in the order they were picked.  This sequence also applies to copy and export commands.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Multiple selection use</Topic>
<Text>More commands make use of a multiple selection instead of just using the single active node.  For example, the paste command will add duplicate children under each selected destination node.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Export node selection</Topic>
<Text>The export command includes options to export the entire tree, the selected branches, or just the selected nodes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data edit view speedup</Topic>
<Text>In order to render the Data Editor right-hand view faster, there is a general option to set the number of &quot;pages&quot; initially shown.  By default, only one page is shown.  Buttons allow toggling to the next page or all pages.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Flat view added</Topic>
<Text>There is a tab on the left-hand view to show a flat node list.  It shows the initially selected nodes and all of their descendants.  It is probably most useful when using filtering commands.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Filtering</Topic>
<Text>A conditional filter selects nodes based on rules for specific data types and fields, and a text filter selects based on finding the given text in any field.  Both filters show their results in the tabbed &quot;Flat View&quot; and remain in effect until removed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Child count field</Topic>
<Text>In the advanced mode, a child count field reference can be added to the output configuration.  It shows the number of children at a specified descendant level.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>July 6, 2006 - Release 1.0.0</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Version numbering</Topic>
<Text>A new version numbering system is being introduced.  This release is 1.0.0, to better indicate its stability.  The 1.1.x series will be started soon for less stable development releases.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>German ReadMe</Topic>
<Text>The German translation of the ReadMe file has been updated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Multiple selection drag</Topic>
<Text>Fixed a problem with duplicate nodes showing up when pasting multiple nodes on Windows.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Improper generic types</Topic>
<Text>Deriving types from other derived types is no longer allowed, since it did not function properly.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Encryption fix</Topic>
<Text>A problem with saving an encrypted file in the German version of TreeLine has been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>February 16, 2006 - Release 0.14.1</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Improved XSLT export</Topic>
<Text>Exported XSLT files now support field prefixes and suffixes.  Thanks to Roland Meister for supplying patches.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Added plugin functions</Topic>
<Text>Added functions to the plugin interface to allow plugins to open and close nodes.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Unicode in field names</Topic>
<Text>Fixed a problem with displaying output from fields with non-ASCII characters in their names.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Encrypted auto-save</Topic>
<Text>Auto save now works properly with encrypted files.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>December 20, 2005 - Release 0.14.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Type inheritance</Topic>
<Text>Data types can be set to derive their field settings from a generic type.  This allows types with different output formatting to always use the same field data.  Any changes to the generic's list of fields and field types are automatically reflected in the fields of all derived types.  A derived option can be selected when copying a type, or a generic type can be specified from the derived type's &quot;Advanced Configuration&quot; dialog box.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Conditional types</Topic>
<Text>Conditional expressions can be used to automatically assign a data type based on each node's content.  Conditions are assigned to a generic type and its associated derived types.  This allows the automatic assignment of different output formatting or different icons depending on each node's field data.  Conditions are specified from each type's &quot;Advanced Configuration&quot; dialog box.  Conditions do not have to be set for all types in a family, since, if no conditions are true for a node, the program will select a blank condition over a false one.  In addition, conditions that are always &quot;True&quot; or &quot;False&quot; are available to toggle the output format of all nodes of a certain type simultaneously by modifying the condition.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check language</Topic>
<Text>By default, the spell check uses dictionaries for the current operating system language.  A new option under &quot;Tools-&amp;gt;File Options&quot; can be used to specify an alternate two-letter language code for the current TreeLine file.  This only works with aspell and with the appropriate aspell dictionaries available.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Open sample menu</Topic>
<Text>A new menu item, &quot;File-&amp;gt;Open Sample&quot;, is a shortcut to the directory containing sample template files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Help menu</Topic>
<Text>A new menu item, &quot;Help-&amp;gt;Help Contents&quot;, directly opens the &quot;Using TreeLine&quot; section of the ReadMe file.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Type change title</Topic>
<Text>When changing a node's type, if the result would have been a blank title, TreeLine now adjusts the new title fields to maintain the original title text.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Picture paths</Topic>
<Text>Picture links with relative paths now resolve their reference based on the directory containing the current TreeLine file.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Font tag selection</Topic>
<Text>When applying a font tag in the editor view, the selection is maintained.  This allows multiple tags to be applied.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Prefix/suffix tags in titles</Topic>
<Text>HTML tags in field prefixes and suffixes are now removed in node titles.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML output</Topic>
<Text>Exported HTML has been made somewhat more compliant with standards.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows installer option</Topic>
<Text>A new option on the windows installer toggles the writing of installation directory and uninstall information to the registry.  When this and other options are disabled, TreeLine can be installed without modifying the registry.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>New sample files</Topic>
<Text>Four more sample files have been included.  These files provide examples of using TreeLine's features and can be used as templates.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>ReadMe changes</Topic>
<Text>The ReadMe file has been updated with descriptions of the sample files, with more internal links, and with screenshots.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Reference field save</Topic>
<Text>A problem with saving reference field settings for unused node types was fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Copied formats</Topic>
<Text>Formats copied from another file are now available immediately.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Escaped characters in titles</Topic>
<Text>Node titles from HTML-enabled fields that contain escaped characters (&amp;lt;, &amp;gt;, &amp;amp;) are now properly displayed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Default new node values</Topic>
<Text>Fixed some minor bugs concerning setting the default field value for new nodes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML directories output</Topic>
<Text>A problem with exporting HTML directories with very recent versions of the PyQt library was fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Child separators</Topic>
<Text>When displaying child data in node output, extra separators between blank entries are no longer shown.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 1, 2005 - Release 0.13.1</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Recent file option</Topic>
<Text>The number of recently used files listed in the File menu can be set using a new general option.  Note that this also controls how many files have their tree states (open/closed nodes, etc.) saved.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Language setting</Topic>
<Text>TreeLine now sets the interface language using the LANG environment variable (if set) before falling back to other locale settings.  This allows the operating system's locale settings to be overridden.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Locale error</Topic>
<Text>Problems starting TreeLine when the locale's LANG variable ends with &quot;@euro&quot; have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Rename new nodes</Topic>
<Text>Problems with the display of the rename edit box when creating new nodes in a long, scrolled tree view have been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>August 29, 2005 - Release 0.13.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Translation setup</Topic>
<Text>The TreeLine user interface and documentation have been internationalized.  Currently, translations are available for French and German.  Volunteers to translate into additional languages are welcome.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Internationalize number formats</Topic>
<Text>Number formats can be internationalized.  Periods and commas are supported as radix characters, and commas, periods or spaces can be set as thousands separators.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Print unit option</Topic>
<Text>A new general option can set printing units to either inches or centimeters.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>External editor</Topic>
<Text>An external editor can be invoked from a Data Editor text field context menu.  The EDITOR environment variable can be used to specify the editor to start, or, if the variable doesn't exist, TreeLine will prompt for an executable to set as the default.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Number editing</Topic>
<Text>The general option for a number editing format has been removed.  Instead, the output format is displayed in the editor.  Of course, any new entry with a reasonable format is correctly interpreted (but the correct radix character must be used).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spaces in link names</Topic>
<Text>Handling of spaces in filenames for the linking fields have been improved.   Paths with spaces selected in the file browser are properly quoted (Windows) or escaped (Linux).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Output view scrolling</Topic>
<Text>Page Up/Down commands in the Data Output view now leave a one-line overlap.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Interrupt ignore</Topic>
<Text>A Ctrl-C interrupt in a terminal is now ignored.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Bookmark separators</Topic>
<Text>A dummy field has been added to imported bookmark separator formats to avoid configuration problems.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XSLT paths</Topic>
<Text>Paths in links to XSLT files are now properly handled when not in the same directory as the XML file.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Renamed fields</Topic>
<Text>Format text is now immediately updated when renaming fields.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Undo</Topic>
<Text>Problems with undo after complex data changes have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Control characters</Topic>
<Text>Errors due to having ASCII control characters in TreeLine text have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spell check</Topic>
<Text>Problems with spell check of unicode characters have been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 4, 2005 - Release 0.12.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>AutoChoice field type</Topic>
<Text>A new AutoChoice field type provides pull-down selection of previously used entries.  Any new entries are automatically added to the pull-down.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Executable field type</Topic>
<Text>A new ExecuteLink field type runs an external program when its link is clicked.  The command to run is given by the text of the field.  Or the field's prefix may contain the program name, so that the field's text is used for arguments or file names.  There is also a general option to disable these links when security is a concern.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Path browsing</Topic>
<Text>A button that brings up a file browsing dialog has been added to the editor for Path, ExecuteLink and Picture field types.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Alternate text for link fields</Topic>
<Text>Link fields can display alternate text in place of the target URL.  This is done by specifying an alternate text field in the Advanced Field Format dialog.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Embedded child fields in output</Topic>
<Text>Fields from child nodes can be embedded in their parent's output.  Select a child reference from the Other Fields dialog.  The child data is delimited with a separator string defined as a file option.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>No line break file option</Topic>
<Text>A new file option allows the removal of line breaks from each output line.  This allows other HTML tags to be used to separate the output lines.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>New contains filter rule</Topic>
<Text>A &quot;contains&quot; rule to check for substrings has been added to the rules for node filtering and selective type changes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Open last-used right view</Topic>
<Text>The right-hand view that was previously used is now selected automatically on startup.  This can be disabled using the general restore window geometry option.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>PNG icons</Topic>
<Text>Toolbar and tree icons are loaded from individual PNG files instead of from an XPM file.  This improves icon quality.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Advanced dialogs</Topic>
<Text>Some features from the dialogs for data types and fields have been moved to advanced dialogs for simplicity.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Non-ascii letter search</Topic>
<Text>Unicode characters are accepted for first-letter tree searches.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Removed eval() calls</Topic>
<Text>All calls to the eval() function have been replaced for improved security.  Thanks to Roland Meister for providing patches.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Export HTML ReadMe file</Topic>
<Text>The HTML version of the ReadMe file is now exported from the TreeLine version.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Allow spaces in command line</Topic>
<Text>Spaces are permitted in Linux command line arguments.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Allow Qt command line options</Topic>
<Text>Qt command line options are supported.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugin improvements</Topic>
<Text>There have been several minor improvements to the plugin module interface.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Delete last child</Topic>
<Text>A serious problem with deleting the last child under the root item has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Incremental search</Topic>
<Text>Some keyboard shortcuts for incremental searching have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Saved tree state</Topic>
<Text>Open nodes are restored more consistently when opening files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Font issue</Topic>
<Text>A font issue on early versions of Qt3 has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>No dtd file search</Topic>
<Text>The search for dtd files linked from XML files has been disabled to eliminate errors.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Long line editor visibility</Topic>
<Text>Visibility problems with long unbroken text lines in data editors have been fixed in Qt3.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>February 16, 2005 - Release 0.11.1</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Sip compatibility</Topic>
<Text>Fixed a compatibility issue in the toolbar code that would prevent TreeLine from starting when PyQt was built against the newest versions of the sip library (versions 4.2rc1 and 4.2rc2).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Combination field types</Topic>
<Text>Problems with editing the data of combination field types have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugin interface</Topic>
<Text>A bug in the plugin interface for setting field formats has been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>February 4, 2005 - Release 0.11.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Tree view icons</Topic>
<Text>Icons have been added to the tree view. The icon assigned to each data type can be changed from the Configure Data Types dialog box. There are several generic icons available within TreeLine, and plugin modules can be written to add additional ones. A general option to disable the tree icons has also been added.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Copy formats</Topic>
<Text>A command has been added to the data menu to copy type formatting from another TreeLine file. All types from the chosen file are copied. Any types in the current file with a matching name are overwritten, but types with unique names are retained.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XML import and export</Topic>
<Text>Functions to import and export generic XML files have been added. These routines do not have much intelligence - each XML element becomes a node and each XML attribute becomes a field. This lets TreeLine function as a crude XML editor.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data editor height</Topic>
<Text>An editor height parameter has been added to text fields. This allows the number of lines in the data editor to be set for each field in each data type. As a result, the LongText field type becomes redundant and has been removed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Required field parameter</Topic>
<Text>A field parameter has been added for fields that are required to be filled. Fields with this parameter set are marked with an asterisk in the data editor view.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Hidden field parameter</Topic>
<Text>Another field parameter has been added to allow certain fields to be hidden in the data editor view.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Code clean-up</Topic>
<Text>A fair amount of TreeLine code has been rewritten to improve efficiency and to ease future changes. Users should see improved speed with large files, especially noticeable when repainting during editing.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Python version</Topic>
<Text>TreeLine now requires Python Version 2.3 or higher on Linux systems. The previous version of TreeLine will remain available for those stuck with older versions of Python.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Hide HTML tags in titles</Topic>
<Text>HTML tags are now stripped from node titles in the left-hand tree view if the fields are set to output HTML rich text.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugin Extension Interface</Topic>
<Text>The plugin extension module interface has been expanded. Several added functions deal with node and field formatting. There is also a new callback trigger called whenever a node's data is modified.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>User plugin directory</Topic>
<Text>A user plugin directory can now be specified in the configuration file. This allows plugins to be installed without root/administrator access.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Linux installer</Topic>
<Text>An option has been added to the Linux installer to allow a different documentation directory to be specified.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Drag-and-drop</Topic>
<Text>Fixed a drag-and-drop bug that wouldn't allow nodes to be moved instead of copied in the Linux version.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Special field name characters</Topic>
<Text>Fixed the output of fields that include dashes and periods in their names.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Edit view font setting</Topic>
<Text>A problem retaining the font setting for edit views has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Startup failure</Topic>
<Text>A rare startup failure due to problems with the encryption engine has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Encodings</Topic>
<Text>A rare problem with foreign language encodings has been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 8, 2004 - Release 0.10.2</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Node creation</Topic>
<Text>Fixed a major bug that could prevent new nodes that contain date or time fields from being created.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>October 28, 2004 - Release 0.10.1</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Recent files</Topic>
<Text>Fixed a major bug that caused TreeLine to hang when attempting to open a recent file that no longer exists. This bug also caused startup failures if automatic opening was enabled with nonexistent files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugin interface function</Topic>
<Text>A bug in the plugin interface's getRootNode function was fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>File encryption</Topic>
<Text>Fixed a problem with file encryption on 64-bit systems.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>October 15, 2004 - Release 0.10.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Reference fields</Topic>
<Text>One of the fields in a data type can be tagged as a reference field in the field-type dialog box.  It defaults to the first field.  This field is now used as the reference for the arrange and flatten by reference commands.  It is also used by the new internal link feature, described below.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Internal link fields</Topic>
<Text>There is a new internal link field type.  It creates a clickable link in the Data Output window that selects the next node with matching text in its reference field.  If link or reference fields contain multiple lines, each line is treated as a separate link or reference, respectively.  If desired, the same field can be used as both the link and reference fields, so that clicking on a keyword in one node's field selects the next node that also has that keyword.  If exported to HTML, the internal links function as links to page anchors, but, in cases with duplicate references, they only find the uppermost reference on the page instead of the next one.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>File encryption</Topic>
<Text>File encryption has been added as an option to password protect TreeLine files. Individual files can be set to encrypted mode from either &quot;Tools-&amp;gt;File Options&quot; or from the save-as dialog. There is also a general option to set the default for new files. The encryption uses the SHA hash function as a stream cipher - it should be fairly secure.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Initial field values</Topic>
<Text>A default initial field value can now be specified for a field type. Any new nodes get this value for the given data field when they are created. Also, in a date or time field, an initial value of &quot;Now&quot; can be used to get a time-stamp of node creation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Plugins</Topic>
<Text>An interface to plugin extension modules has been added to TreeLine. This allows extensions to be written by various coders that provide functionality needed by a few users without adding bloat to the main application. Currently available plugins are listed on the &quot;Downloads&quot; page of the TreeLine web site. The plugins are installed by copying their Python file (*.py) to the plugins directory (&quot;&amp;lt;prefix&amp;gt;/lib/treeline/plugins/&quot; on Linux or &quot;TreeLine\lib\plugins\&quot; on Windows). A list of loaded plugins can be found using the &quot;Help-&amp;gt;About Plugins&quot; command. Information about writing plugins can be found in the &quot;plugininterface.py&quot; file in the TreeLine source code.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Tree and editor fonts</Topic>
<Text>Options have been added under &quot;Tools-&amp;gt;General Options&quot; to set the fonts used for the tree view and for the right-pane editor views.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Page breaks</Topic>
<Text>When printing, TreeLine will now avoid breaking pages between a parent and its first child.  This behavior can be disabled by changing the &quot;Keep first child with parent&quot; print option.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Unicode</Topic>
<Text>Unicode text handling has been improved.  Unicode can now be used in TreeLine file names, node data type names and field names.  Also, imported and exported text files now use the proper encoding based on the system's locale settings.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Internal link sample</Topic>
<Text>A new sample TreeLine file with internal link fields has been added to the documentation.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>File-info field dialog</Topic>
<Text>An occasional problem bringing up the field-type dialog for file-info fields was fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>File-info data type</Topic>
<Text>Avoid showing an oddly-named internal file-info data type in the dialogs after the file-info formatting is changed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>View states</Topic>
<Text>The option to restore the view state when opening recently used files now works more consistently.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>September 16, 2004 - Release 0.9.1</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Unicode update</Topic>
<Text>Unicode text is now supported without requiring modifications of the Python sitecustomize file. The sitecustomize change has been eliminated from the installer.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Open file filter</Topic>
<Text>The compressed &quot;.trl.gz&quot; extension has been added to the file open filter.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Mailing list</Topic>
<Text>Information about the new TreeLine mailing list has been added to the documentation.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>XSLT export</Topic>
<Text>A bug that prevented XSLT file export under Linux has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XBEL export</Topic>
<Text>Special characters in bookmark URL's are now properly escaped during export to XBEL format.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>September 9, 2004 - New Mailing List</Name>
<TEXT_HEAD item="y">
<Topic>List Information</Topic>
<Text>A mailing list has been created for users to discuss anything and everything about TreeLine. This is the place for development discussions (from roadmaps to feature suggestions to beta testing), release announcements, bug reports, and general user discussions (from new uses to tips &amp;amp; tricks to configuration samples).&lt;br /&gt;&lt;br /&gt;

To subscribe, go to &amp;lt;http://bellz.org/mailman/listinfo/treeline&amp;gt;. I expect this to be a low-volume mailing list.</Text>
</TEXT_HEAD>
</HEADING3>
<HEADING3 item="y">
<Name>September 1, 2004 - Release 0.9.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Bookmark import/export</Topic>
<Text>Import and export of bookmarks in both the Mozilla HTML format (Mozilla, Firefox and Netscape browsers) and the XBEL format (Konqueror, Galeon and Elinks browsers) have been added.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Sub-tree export</Topic>
<Text>An new option exports a portion of a tree to another TreeLine file.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Command line import/export</Topic>
<Text>Command line options have been added to allow non-interactive file importing and exporting. This allows automated runs to be scheduled. For more details, run &quot;treeline -h&quot; from the command line.  If using a windows binary, output is supressed, so it must be directed to a log file (&quot;treeline -h &amp;gt; log.txt&quot;).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>File compression</Topic>
<Text>Options have been added to work with compressed TreeLine files. Individual files can be set to compressed mode from either &quot;Tools-&amp;gt;File Options&quot; or from the save-as dialog. There is also a general option to set the default for new files. Thanks to Mathieu Girard for contributing code.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Ancestor field references</Topic>
<Text>A field reference to show data from any ancestor node has been added. The closest one with a matching field is used.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>File info fields</Topic>
<Text>Fields containing file meta-data have been added. These include file name, path, size, and modified time.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Headers and footers</Topic>
<Text>Headers and footers for printing have been added. They can contain the file meta-data mentioned above. The headers and footers can also be shown in exported HTML files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Character formatting</Topic>
<Text>HTML character formatting tags can be automatically added to text using a new data editor context menu. Available tags include bold, italics, underline, size and color. Note that the fields must be set to display HTML content for this to be effective.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML content option</Topic>
<Text>A new general option makes new fields default to HTML content. This allows for easier display of HTML formatting. This option is not enabled by default, since it does not preserve carriage returns and does not show non-escaped &quot;&amp;lt;&quot;, &quot;&amp;gt;&quot; and &quot;&amp;amp;&quot; symbols.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Saving tree states</Topic>
<Text>When opening a recently used file, TreeLine will now restore the states of open and selected nodes. If desired, this feature can be disabled with a new general option. Thanks to Jan Hustak for contributing this code.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Toolbar split</Topic>
<Text>The toolbar has been split into two separate bars (general commands and node commands) that can be shown and moved independently. Again, thanks to Jan Hustak for contributing this code.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Auto-save</Topic>
<Text>A new auto-save feature stores unsaved files with a &quot;~&quot; appended to the name. The backup files are automatically removed when the file is saved or TreeLine exits cleanly. The auto-save time interval is set in the general options.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Scroll key bindings</Topic>
<Text>New key bindings, set to Shift+Page-Up and Shift+Page-Down by default, scroll the current right-hand child view.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XSL style sheet</Topic>
<Text>The XSL export command now prompts for the name of an optional style sheet (css). This name is stored in the TreeLine file as the default for future exports.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Import/export improvements</Topic>
<Text>There have been some general improvements to the handling of imported and exported files.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Undo/redo</Topic>
<Text>File option settings can now be restored with undo/redo commands.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Documentation</Topic>
<Text>The README documentation files have been revised to be more organized and readable.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Sample files</Topic>
<Text>More sample files are provided.  See the &quot;sample_*.trl&quot; files in the &quot;doc&quot; directory of the installation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Linux installer option</Topic>
<Text>The Linux install script now includes an option for a temporary build root directory.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Up key binding</Topic>
<Text>The up-arrow key binding did not work as expected in a deeply nested tree.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Combo boxes</Topic>
<Text>Some problems with auto-completion on data editor combo boxes have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spin boxes</Topic>
<Text>Problems in windows with some option spin boxes accepting new values have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Python compatibility</Topic>
<Text>Fixed a compatibility issue with older versions of Python.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>June 23, 2004 - Release 0.8.1</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Node renaming crash</Topic>
<Text>Fixed crashes that sometimes occurred when switching focus or views after renaming a new or existing node.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Compatibility with older versions of Qt</Topic>
<Text>Fixed a compatibility issue with older versions of Qt (3.0.x).</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>June 3, 2004 - Release 0.8.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Undo/redo</Topic>
<Text>Added undo and redo commands and an option for the number of undo levels that are stored.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Parent field display</Topic>
<Text>Added the ability to show parent and grandparent data within a node's formatted output.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Node type menu</Topic>
<Text>When changing node types with the menu, check marks now show the current type(s).</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Node renaming</Topic>
<Text>Fixed crashes caused by right-clicking in the edit area or using the Alt-Tab key combination when renaming a node title.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data type names</Topic>
<Text>Fixed problems occurring when several similar data type names were defined.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Installation script</Topic>
<Text>A rare problem with the installation script choking on image thumbnail directories was fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 18, 2004 - Release 0.7.3</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Spell check</Topic>
<Text>Spell checking of the tree data has been implemented.  This feature requires an external program, either aspell or ispell (see the System Requirements section).</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Print preview size</Topic>
<Text>The size and position of the print preview window are now
 saved.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Export open text</Topic>
<Text>Added an option for including only open descendants when exporting tabbed title text.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>April 1, 2004 - Release 0.7.2</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Keyboard navigation</Topic>
<Text>For faster keyboard navigation, the left arrow key now closes the selected node's parent if the selected node has no children or is already closed.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Drag-and-drop</Topic>
<Text>Some tree item drag-and-drop bugs have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Dialog closing</Topic>
<Text>Problems when some dialogs were closed using the escape key have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Install script</Topic>
<Text>Fixed some rare Linux install script problems with some systems.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>March 9, 2004 - Release 0.7.1</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>File open default</Topic>
<Text>The open file dialog now uses the directory of the most recently opened file as its initial directory.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Right-hand view</Topic>
<Text>To improve performance, some unnecessary refreshes of the right-hand view were eliminated.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Search and change type commands</Topic>
<Text>Fixed problems with repeated uses of the search dialog command and the command to set the types of descendants.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Data editor view</Topic>
<Text>Fixed problems with the data editor view in the mode that does not show children.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>March 2, 2004 - Release 0.7.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Prefix and suffix tags</Topic>
<Text>Added prefix and suffix tag formatting for groups of siblings.  These tags allow output to be formatted in tables or with bullets. See the &quot;sample_table.trl&quot; file for an example of table formatting.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Save window geometry</Topic>
<Text>The size and position of the window and its splitters are now saved at exit.  A new option will disable this feature if desired.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Treepad import filter</Topic>
<Text>An import filter has been added to open Treepad files (text nodes only).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows installer</Topic>
<Text>An install program has been added for windows.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Linux install script</Topic>
<Text>Fixed Linux install script problems with certain versions of Python.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Export end-of line</Topic>
<Text>Fixed some text exports where improper end-of-line characters were used on windows.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 19, 2003 - Release 0.6.2</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Wait cursor</Topic>
<Text>Cursor changes were added to indicate time-consuming operations.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Tree scrolling</Topic>
<Text>Eliminated inadvertent scrolling of the tree view when editing in the right-hand view.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Install script</Topic>
<Text>Fixed problems encountered when the Linux install script attempted to delete old TreeLine directories under certain versions of Python.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 7, 2003 - Release 0.6.1</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Incremental search</Topic>
<Text>Incremental searching has been improved by adding keyboard commands to repeat the search forward (F3 by default) and backward (Shift-F3 by default).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Sorting</Topic>
<Text>The sorting commands now contain options for reverse sorting.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Text imports</Topic>
<Text>The importing of text files has been improved.  Imports of plain text were added, with items for each line or each paragraph.  A prompt for the type of text file was also added.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Title rename option</Topic>
<Text>A new option setting avoids going into title renaming mode when adding a new node.  This also keeps the selection unchanged as nodes are added.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Drag files</Topic>
<Text>Dragging files to the TreeLine window in order to open them is now supported.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Context menu rename</Topic>
<Text>The rename command was added to the tree context menu.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Right view scrolling</Topic>
<Text>The right view now scrolls to the top when the item selected in the tree view changes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Initial configure type</Topic>
<Text>When opening the configure types dialog, the current tree item's type is initially selected.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>ReadMe file</Topic>
<Text>A TreeLine formatted version of the ReadMe file has been added.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Linux install</Topic>
<Text>An install script was added for Linux and Unix systems.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Windows build</Topic>
<Text>The windows build now uses Python version 2.3 and PyQt version 3.8.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Rename issues</Topic>
<Text>Keyboard commands are disabled during tree rename operations to avoid unpredictable results.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>View updates</Topic>
<Text>The right views now update properly when the parent of the selected tree item is closed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Multiple copies</Topic>
<Text>Problems involving copying with multiple nodes selected were fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Drag-and-drop</Topic>
<Text>Problems with drag-and-drop on some Linux systems were fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>September 16, 2003 - Release 0.6.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Split views</Topic>
<Text>The three right views are now divided into upper sections for the selection's data and lower sections for the data from the selection's children. View commands can be used to hide the display of children if desired.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Customized shortcut keys</Topic>
<Text>Keyboard shortcuts can be customized by editing the TreeLine configuration file (&quot;~/.treeline&quot; on Linux, &quot;treeline.ini&quot; on windows). Any configuration files from previous versions should be deleted when installing TreeLine 0.6.0.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Easily set type</Topic>
<Text>A new command will quickly set a node's data type.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Automatic open on search</Topic>
<Text>Parent nodes will automatically open and close when found with the two search methods, by typing the first letter and with the &quot;next sibling&quot; keyboard command. This behavior can be disabled with a new general option.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>First letter navigation</Topic>
<Text>Typing a lowercase letter will move forward through the visible tree items that start with that letter. An uppercase letter will move backward.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Incremental search</Topic>
<Text>Tree items (including those not visible) can be incrementally searched by typing &quot;/&quot; followed by the search string.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Modeless find dialog</Topic>
<Text>The Find dialog box is now modeless (the program may be operated while the dialog is open).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>New choice type</Topic>
<Text>A &quot;Choice&quot; field type has been added that allows selection from a user-defined list of strings.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>New combination type</Topic>
<Text>A &quot;Combination&quot; field type has been added that allows selection of several items from a user-defined list of strings.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Linking types</Topic>
<Text>Several linking field types have been added, including &quot;URL&quot;, &quot;Path&quot;, &quot;Email&quot;, and &quot;Picture&quot;. Clicking on a &quot;URL&quot; or &quot;Path&quot; in the output window will open the link in an external browser. The &quot;Picture&quot; fields are shown on in the output window for certain image formats.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Pull-down editors</Topic>
<Text>Pull-down editors have been added for the &quot;Choice&quot;, &quot;Combination&quot;, &quot;Date&quot;, &quot;Time&quot;, and &quot;Boolean&quot; field types.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Output font selection</Topic>
<Text>A font selection for the data output view has been added to the general options.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>New printing options</Topic>
<Text>New printing options include setting the print font and setting a default page size.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Save unused configurations</Topic>
<Text>Configuration information is properly saved for unused node data types.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>More keyboard friendly</Topic>
<Text>TreeLine is now more keyboard-friendly in many ways.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Arrange window captions</Topic>
<Text>Window captions now put the file name first.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Data edit resizing</Topic>
<Text>Fixed problems with data edit view resizing (on Qt3 only).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML in prefix/suffix</Topic>
<Text>Fixed file corruption problems caused by the use of HTML characters in the field format's prefix and suffix areas.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>March 14, 2003 - Release 0.5.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Default child types</Topic>
<Text>When configuring node data types, a default type for that type's new children can be set.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Multiple page HTML export</Topic>
<Text>An added form of HTML export creates a directory structure with a separate page for each parent node.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>New sibling shortcut</Topic>
<Text>A shortcut (Ctrl-B) has been added to the command to insert a sibling node.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>New icon files</Topic>
<Text>Icon files have been added to the distribution files.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>August 26, 2002 - Release 0.4.2</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Fixed Python 2.1 issue</Topic>
<Text>Fixed another (oops) incompatibility problem with Python 2.1.x. This change is also not needed when using Python 2.2 or higher.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>August 23, 2002 - Release 0.4.1</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Fixed Python 2.1 issue</Topic>
<Text>Fixed an incompatibility problem with Python versions 2.1.x. This change is not needed when using Python 2.2 or higher.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>August 22, 2002 - Release 0.4.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Field types</Topic>
<Text>Data fields can be formatted as specific types, including short and long text, numbers, dates, times, and boolean values.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML or plain text fields</Topic>
<Text>Individual fields can be specified as plain text or HTML. Line breaks are preserved in plain text mode.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Field prefixes &amp; suffixes</Topic>
<Text>Text prefixes and suffixes can be assigned to fields. The extra text does not display for blank fields.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Spaces between nodes</Topic>
<Text>Options for spaces between nodes and allowing HTML in formats are saved with the file instead of being global options.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Truncated node titles</Topic>
<Text>Node titles are truncated after the first line of text data.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Conditional type setting</Topic>
<Text>Node types can be set conditionally.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Variable text length</Topic>
<Text>A new option allows the number of lines in a long text edit field to be set.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Update missing fields</Topic>
<Text>Missing fields can be updated from a separate file by matching unique values of the first data field.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Title rename</Topic>
<Text>Clicking on an unselected current item no longer initiates title renaming.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Paste fix</Topic>
<Text>Rare problems with opening or pasting content with complex text strings were fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 28, 2002 - Release 0.3.4a</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Windows library issue</Topic>
<Text>A fix of the Windows binary only. Fixes major problems by upgrading the library version to PyQt 3.2.4.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>May 15, 2002 - Release 0.3.4</Name>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Ported to Qt 3</Topic>
<Text>TreeLine has been ported to Qt 3.x. It now works with both Qt 2.x and 3.x using the same source code.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Binaries updated</Topic>
<Text>The binaries for windows have been updated to Python 2.2 and PyQt 3.2 (but are still using Qt 2.3 Non-commercial).</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Selection bug</Topic>
<Text>A selection bug that caused problems with the up/down and indent/unindent commands has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Preference fix</Topic>
<Text>Errors in the initial user preference file were fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>March 6, 2002 - Release 0.3.3</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Multiple selection</Topic>
<Text>Multiple nodes in the tree can now be selected using the shift and control keys - most commands will operate on multiple nodes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Copy node text</Topic>
<Text>A new command will copy node titles as text, not just as XML.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Print and export open</Topic>
<Text>Options have been added to print and export only nodes which are open in the tree.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Numbering start</Topic>
<Text>A new option allows the numbering command to start with a number greater than one.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XSLT reference tool</Topic>
<Text>A tool to remove the XSLT reference from a file has been added.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Arrange by reference</Topic>
<Text>The command to arrange a tree by reference has been made more robust.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Opening error handling</Topic>
<Text>Errors when opening files are now handled better.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Export of unicode</Topic>
<Text>The export of Unicode characters to HTML has been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Set types dialog</Topic>
<Text>A problem with the set data types dialog under Python 2.2 has been fixed.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>January 7, 2002 - Release 0.3.2</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Unicode support</Topic>
<Text>Unicode is now supported in both data and format strings, allowing the entry of foreign text and symbols (note that there is an extra step in the Linux installation to enable this feature).</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Sort all nodes</Topic>
<Text>A new sort command allows all nodes of a given type to be sorted.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Right view preference</Topic>
<Text>A preference setting now controls the initial state of the right-hand view.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Tool-bar during rename</Topic>
<Text>Fixed crashes caused by tool-bar use while renaming a node.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Deleting &amp; renaming nodes</Topic>
<Text>Occasional problems with deleting or renaming fields have been fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Large edit views</Topic>
<Text>Fixed crashes resulting from very large data edit views.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>December 12, 2001 - Release 0.3.1</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Print lines</Topic>
<Text>Parent/child lines can now be added to printouts for better tree visualization.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Compress format</Topic>
<Text>An option was added to compress the format into a single line of output.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>Sort full branches</Topic>
<Text>Problems with sorting full branches were fixed.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML indenting</Topic>
<Text>Fixed improper indentation on an HTML export file.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>November 27, 2001 - Release 0.3.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Filtering</Topic>
<Text>Added filtering of descendant nodes.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Numbering</Topic>
<Text>Added a data node numbering feature with both outline and section styles.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Export XSLT</Topic>
<Text>Added a feature to export the format to an XSLT file.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Help links</Topic>
<Text>Added table of contents links to the help file.</Text>
</TEXT_BULLETS>
</HEADING4>
<HEADING4 item="y">
<Name>Updates:</Name>
<TEXT_BULLETS item="y">
<Topic>Long strings</Topic>
<Text>Improved the handling and editing of long data strings.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>HTML tags</Topic>
<Text>Improved the handling of HTML tags in data formats.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XML parser</Topic>
<Text>Improved XML parser error handling.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>October 23, 2001 - Release 0.2.1</Name>
<HEADING4 item="y">
<Name>Bug Fixes:</Name>
<TEXT_BULLETS item="y">
<Topic>New node types</Topic>
<Text>Fixed a major bug that caused errors when new node types were created.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
<HEADING3 item="y">
<Name>October 17, 2001 - Release 0.2.0</Name>
<HEADING4 item="y">
<Name>New Features:</Name>
<TEXT_BULLETS item="y">
<Topic>Rewrite</Topic>
<Text>TreeLine has been extensively rewritten to include database field information in each node.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>XML format</Topic>
<Text>The file format is now XML.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Right-hand views</Topic>
<Text>Added additional views in the right-hand pane.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Formatting</Topic>
<Text>Added options for data formatting and manipulation.</Text>
</TEXT_BULLETS>
<TEXT_BULLETS item="y">
<Topic>Import &amp; export options</Topic>
<Text>Added more file import and export options, including HTML export.</Text>
</TEXT_BULLETS>
</HEADING4>
</HEADING3>
</HEADING2>
<HEADING2 item="y">
<Name>Questions, Comments, Criticisms?</Name>
<Ref>contact</Ref>
<TEXT_PARA item="y">
<Topic>Mailing list</Topic>
<Text>There is a mailing list for users to discuss anything and everything about TreeLine. This is the place for development discussions (from roadmaps to feature suggestions to beta testing), release announcements, bug reports, and general user discussions (from new uses to tips &amp;amp; tricks to configuration samples).&lt;br /&gt;&lt;br /&gt;

To subscribe, go to &lt;a href=&quot;https://lists.berlios.de/mailman/listinfo/treeline-users&quot;&gt; lists.berlios.de/mailman/listinfo/treeline-users&lt;/a&gt;. I expect this to be a low-volume mailing list.</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Email</Topic>
<Text>If you do not wish to subscribe to the mailing list, I can be contacted by email at: doug101 AT bellz DOT org</Text>
</TEXT_PARA>
<TEXT_PARA item="y">
<Topic>Updates</Topic>
<Text>I welcome any feedback, including reports of any bugs you find. Also, you can periodically check back to &lt;a href=&quot;http://treeline.bellz.org&quot;&gt;treeline.bellz.org&lt;/a&gt; for any updates.</Text>
</TEXT_PARA>
</HEADING2>
<TEXT_CNTR_TODO item="n"
line0="{*Name_en*}"
line1="&lt;center&gt;{*Name_en*}&lt;/center&gt;"
generic="TEXT_CNTR"
icon="bullet_1">
<Name type="Text"></Name>
<Ref type="Text" ref="y"></Ref>
</TEXT_CNTR_TODO>
<CONTENTS_LINK_INDENT_TODO item="n"
line0="{*Name_en*}"
line1="&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{*Link*}&lt;br /&gt;"
generic="CONTENTS_LINK_INDENT"
icon="bullet_1">
<Name type="Text"></Name>
<Link type="InternalLink" html="y" linkalt="Name_en"></Link>
<Ref type="Text" ref="y"></Ref>
</CONTENTS_LINK_INDENT_TODO>
<TEXT_BULLETS_TODO item="n"
line0="{*Topic_en*}"
line1="&lt;li&gt;{*Text_en*}&lt;/li&gt;"
generic="TEXT_BULLETS"
sibprefix="&lt;ul&gt;"
sibsuffix="&lt;/ul&gt;"
icon="bullet_1">
<Topic type="Text"></Topic>
<Text type="Text" html="y" lines="7"></Text>
<Ref type="Text" ref="y"></Ref>
</TEXT_BULLETS_TODO>
<HEADING4_TODO item="n"
line0="{*Name_en*}"
line1="&lt;h4&gt;{*Name_en*}&lt;/h4&gt;"
childtype="TEXT_PARA"
generic="HEADING4"
icon="bullet_1">
<Name type="Text"></Name>
<Ref type="Text" ref="y"></Ref>
</HEADING4_TODO>
<TEXT_PARA_TODO item="n"
line0="{*Topic_en*}"
line1="&lt;p&gt;{*Text_en*}&lt;/p&gt;"
generic="TEXT_PARA"
icon="bullet_1">
<Topic type="Text"></Topic>
<Text type="Text" html="y" lines="12"></Text>
<Ref type="Text" ref="y"></Ref>
</TEXT_PARA_TODO>
<TEXT_HEAD_TODO item="n"
line0="{*Topic_en*}"
line1="&lt;h4&gt;{*Topic_en*}&lt;/h4&gt;"
line2="&lt;p&gt;{*Text_en*}&lt;/p&gt;"
generic="TEXT_HEAD"
icon="bullet_1">
<Topic type="Text"></Topic>
<Text type="Text" html="y" lines="12"></Text>
<Ref type="Text" ref="y"></Ref>
</TEXT_HEAD_TODO>
<FIGURE_TODO item="n"
line0="{*Topic_en*}"
line1="&lt;p&gt;{*Picture_en*}&lt;/p&gt;"
line2="&lt;p&gt;&lt;b&gt;{*Caption_en*}&lt;/b&gt;&lt;/p&gt;"
generic="FIGURE"
icon="bullet_1">
<Topic type="Text"></Topic>
<Caption type="Text" html="y" lines="2"></Caption>
<Picture type="Picture" html="y"></Picture>
<Ref type="Text" ref="y"></Ref>
</FIGURE_TODO>
<HEADING3_TODO item="n"
line0="{*Name_en*}"
line1="&lt;hr /&gt;&lt;h3&gt;{*Name_en*}&lt;/h3&gt;"
childtype="HEADING4"
generic="HEADING3"
icon="bullet_1">
<Name type="Text"></Name>
<Ref type="Text" ref="y"></Ref>
</HEADING3_TODO>
<HEADING_CNTR_TODO item="n"
line0="{*Name_en*}"
line1="&lt;center&gt;&lt;h2&gt;{*Name_en*}&lt;/h2&gt;&lt;/center&gt;"
childtype="TEXT_PARA"
generic="HEADING_CNTR"
icon="bullet_1">
<Name type="Text"></Name>
<Ref type="Text" ref="y"></Ref>
</HEADING_CNTR_TODO>
<HEADING1_TODO item="n"
line0="{*Name_en*}"
line1="&lt;center&gt;&lt;h1&gt;{*Name_en*}&lt;/h1&gt;&lt;/center&gt;"
childtype="HEADING2"
generic="HEADING1"
icon="bullet_1">
<Name type="Text"></Name>
<Ref type="Text" ref="y"></Ref>
</HEADING1_TODO>
<CONTENTS_LINK_TODO item="n"
line0="{*Name_en*}"
line1="&lt;br /&gt;{*Link*}&lt;br /&gt;"
generic="CONTENTS_LINK"
icon="bullet_1">
<Name type="Text"></Name>
<Link type="InternalLink" html="y" linkalt="Name_en"></Link>
<Ref type="Text" ref="y"></Ref>
</CONTENTS_LINK_TODO>
<HEADING2_TODO item="n"
line0="{*Name_en*}"
line1="&lt;hr /&gt;&lt;h2&gt;{*Name_en*}&lt;/h2&gt;"
childtype="HEADING3"
generic="HEADING2"
icon="bullet_1">
<Name type="Text"></Name>
<Ref type="Text" ref="y"></Ref>
</HEADING2_TODO>
</HEADING1>