This version is out of date, covering development from v4.6.0 to v4.7.1. It is maintained here only for inbound reference links from elsewhere.
Jump to the current version of aTbRef.
|A Tinderbox Reference File : Import/Export/Formatting : Notes can be export templates||aTbRef Site Map|
Notes can be export templates
Export templates can be stored in a Tinderbox note.
The note Create/Rename dialog has an check-box, Can be a template. If this is checked, the note's path appears in the template menu, and the note may be used as an export template. (N.B. this option applies only to proper notes and not agents).
In HTML & Text Export views, the Template pop-up list contains up to three sections:
Template notes appear in the menu by their complete path. For example, if the template Book Template is a note inside the root-level container named "Templates", it appears in the menu as
If a note's name (or path/name) is identical to the name of a template file, the note template will be used rather than the file.
To avoid unwanted name conflicts, it is suggested to store templates in a dedicated container, perhaps using a self-evident name like "Templates".
A note's availability as a template is stored in attribute IsTemplate.
The HTML and Text Export Preferences selector for the default template has changed. This is a pop-up list allowing a choice from one of 3 sections:
Note templates can be selected from HTML/Text Export Preferences, HTML View and Nakakoji view. Editing a template attribute in Info view will only show a file chooser dialog. A template key attribute displayed in a note text windows can be edited but no menu is created.
|Previous: Invoke command line scripts in action code||Next: OPML Import|
Licensed under Creative Commons Attribution-Noncommercial-Share Alike 3.0 License
[See aTbRef CC licence Attribution/Waiver info info]