This version is out of date, covering development from v8.0.0 to v8.x.x. It is maintained here only for inbound reference links from elsewhere. It is no longer actively updated.

Jump to the current version of aTbRef

Tinderbox v8 Icon

Built-in Prototypes

The File menu has a sub-menu listing built-in prototypes. These are a series of prototypes pre-configured for quick use. On first addition of one or more of these predefined prototypes to a TBX, Tinderbox adds a root-level container called 'Prototypes'. After the first addition, any other built-in prototypes added are put in the same container.

The built-in types only use system attributes for their customisations, though the user can further customise the basic prototype with user attribute once added to a TBX. The sub-menu is disabled in read-only documents.

Note that a prototype that is also an export template (e.g. 'HTML Template', below) will not be listed in the Template pop-up menu. This is so that a note can inherit template status via a template without cluttering the template listing with prototypes.

The offered prototypes are:

The prototypes of watched notes specify that watched notes are imported with a $TextBackgroundColor of white, even if using dark styles in Tinderbox, since external documents are most likely compatible with light background colours.

There is nothing stopping the user from further modifying these prototypes once they are in a TBX, for instance by adding user attributes to the Displayed Attributes, etc.

The TB-default-created "Prototypes" container is set with $OnAdd of $IsPrototype=true to ensure that any child notes added by the user as automatically set as prototypes. The container is also set with $HTMLDontExport as true and $HTMLExportChildren as false. That change ensures that neither the container or its content get exported as this is usually the desired condition.

To store user defined prototypes for easy re-use, the best method is to make a TBX holding just the prototypes (and any necessary user attributes). Place this file in the Templates folder. From there the document can easily be opened to copy across individual prototype notes. Note however, that if the prototype uses any user attributes these must exist in the file to which the note is being copied (the built-in prototypes use only system attributes in their customisation).

Adding a built-in Template will cause this container to be added, in order to hold the HTML Template prototype needed for the templates.