Imagine that your company employs you in their sales office, where you manage a team of skilled sales representatives who are on the road most of the time. You would like to issue each of them with a company address book they can call up on their notebook computers, that not only contains pre-entered telephone numbers of company personnel and locations, but also permits them to add contact information for each of their own clients. Since they all like TreePad, you decide to create a special file for the task.
Commencing with a TreePad file empty apart from its Root node, use Insert special to insert a child Business address TreeBook template. Rename it Contacts (Fig. 1a). Now, just as you did in Creating categories, create three categories of contacts, Company, Clients and Personal, with a record or two containing data in the Company section (Fig. 1b).
Now you are ready to present them with this file. Focusing on CONTACTS, Click Main menu ⁄ File ⁄ Export ⁄ Selected subtree ⁄ Export to one file ⁄ TreePad Database and save it as Contacts.hjt. You can now open it as a separate file with CONTACTS as its Root node, and upload it to the company file server.
But wait. The good word has spread around and you are now asked to create a number of these files for international divisions of the company, each with its own local telephone numbers. How you wish you could have the original file close to hand to act as a template when needed, inserting and modifying it as required.
Then you realize that all you have to do is copy contacts.hjt to the \templates folder. When you select Insert special ⁄ TreePad structure ⁄ Contacts ⁄ Insert as child1, the whole book is inserted into your file as a child of the currently selected node. The appearance is again that of Fig. 1b above. Contacts.hjt now functions as a kind of template termed a TreePad structure.
Note that a TreePad structure is always a .hjt file, whether or not its Root node is a standard article, a TreeBook form (unlikely but possibly useful), or a TreeBook template. In general, the term TreePad structure is used to refer to a subtree of nodes containing at least one template node, which is logically located near the top of the tree and may even be the Root node, although this is not obligatory. The template is often a TreeBook template but may also be a standard article template, as we will see later.
TreePad comes with a number of sample TreePad structures preinstalled into the \templates folder and having the same filename as their corresponding TreeBook templates. You can distinguish them in the following ways:
|has .tpt extension
||has .hjt extension
|visible in Insert special window only when TreeBook template or Individual node selected
||visible in Insert special window only when TreePad structure selected
The term TreePad structure is preferred to TreeBook structure, since the template in a TreePad structure does not necessarily have to be a TreeBook template.
- Again, users of TreePad PLUS and SAFE should press Alt+Insert to display this menu.
- The identical filenames used for both TreeBook templates and TreePad structures in the sample files in \templates tends to mask the fact that they are not interchangeable.
- Once inserted, the structure template is treated as any other subtree, but should still be regarded as a structure to signify its origin and internal organization.
- If you save a TreePad structure directly to \templates, this may create a .tps (TreePad State) file in this directory if you enabled this option. Do not confuse .tps files with .tpt (TreeBook template) files.
- Underscores in the structure template filename are translated to spaces when it appears in the Insert special window.
- The file list in the Insert special window is automatically updated each time you reopen the window.
- If you navigate to the \templates folder using Windows Explorer, you can open any of the structure template files directly.