## Ittf document loading
A textual Ittf document is loaded into an mTree object by these modules that are run in sequence.* liner 
* nodifier 
* includer 
* mixer 
* appender 
* evaluator 
## Glossary
|$append [hook-name]|Is an ittf command that declares a node branch thatmust be appended to a related '$hook [hook-name]' command ina mixed mTree brick.|
|$hook [hook-name]|Is an ittf command that declares an insertion point inthe tree structure of a mixed mTree brick. Node branches,children of a 'mix' command, declared with the'$append [hook-name]' command can be appended to the '$hook' node.|
|$include [path]|Is an ittf command that invokes the inclusion of another mTree brick.An include command cannot have children nodes, and it is simplyreplaced by the included brick.|
|ittf document|Ittf, short for Indented Text Tree Format, is the textual notation format of an mTree.An ittf document is a syntax tree, codified in a text document,where child nodes are indented to their parent.Every line is a node consisting of a name-value pair.The name is the first string of chars of the line and is separatedfrom the value by a space or a tab.An ittf document is a template and when loaded for building an mTreewe can pass a context object to the mTree loader.All nodes are templateable and composable. Even the root node may be a command nodethat invokes the mixup of its container.When parsed and nodified an ittf document become an mTree brick.|
|jsWizzi|JsWizzi is a subset of the ECMA-262 javascript standard used by the wizzi factoryfor the buildup of mTrees.It is built on the quite efficent esprima parsing infrastructure and is runby a custom, sandboxed, javascript engine. See jsWizziRunner.|
|jsWizziContext|The evaluation step of an mTree loading uses three types of value contexts.* One global context. 
* One single node structure context, where the mTree is built. 
* One value context for each mTree brick. 
|
|jsWizziRunner|The javascript engine of an mTree buildup. It is run for expressions interpolation,template commands evaluation and mTree final buildup.|
|mix command|Is an ittf command that invokes the mixup of another mTree brick.Every node with the node-name ending with an open paren is a mix command.A mix command may have children nodes, that may declarebranches to be appended to hooks in the mixed mTree brick.See the $append and $hook command nodes.|
|mTree|An in-memory tree data structure of name-valued nodes that is built loading andprocessing an ittf document|
|mTree brick|A nodified ittf document.mTree bricks are the items that compose an mTree.They can mix (or include) other bricks and be mixed (or included).The same brick can be reused in many branches of the mTree,so a brick is loaded once and always cloned.|
|- included mTree brick|An mTree brick included in an including mTree brickusing the command <bold>$include [path]</bold>.Both the tree structure and the value context are included.Context values declared in the included nodes are created inthe scope of the includer.
|
|- mixed mTree brick|An mTree brick mixed in a mixing mTree brickusing the command <bold>[path]([params])</bold>.The tree structure is mixed but the value context remain distinct.Context values declared in the mixed nodes are created inthe scope of the mixed mTree brick and do not interfere with the mixer.
|
|mTree loading|The creation of an mTree from an ittf document.* line parsing (of a source ittf document) 
* nodification (produces one mTree brick from every source ittf document) 
* mix-composition (recursive on mixed and included mTree bricks) 
* include-composition (recursive on mixed and included mTree bricks) 
* append-resolution (on the composed mTree piece) 
* evaluation (on the mixed and appended mTree piece) 
|
|- line parsing|The text of the ittf document is parsed into name-valued lines,eliminating comments, resolving line continuations, detecting indentationand managing chars that interfere with variable interpolation.|
|- nodification|The lines parsed in the previous step are transformed in a treestructure, an mTree brick, respecting the indentation of the source.One root node only is allowed.|
|- mix-composition|The mTree brick, produced by the previous step, is traversed andall the 'mix commands' encountered are recursively resolved.The result is an mTree piece composed by one or many bricks.|
|- include-composition|The mTree piece, produced by the previous step, is traversed andall the '$include [path]' commands encountered are recursively resolved.The recursion manages the mix-composition of included bricks too.|
|- append resolution|The mTree piece resulting from composition is traversed again andchild branches (of mix commands), declared with the '$append [hook-name]'command, are moved, replacing the related '$hook [hook-name]'command of the mixed mTree brick.|
|- evaluation|The last step of an mTree loading. From the mTree piece producedby the previous steps is created a jsWizzi script that evaluatesthe template commands of its nodes and builds the final mTree.|
|mTree buildup script|The jsWizzi script that, once executed, by thejsWizziRunner, will give as result the final mTreeof the source ittf document.|
|mTreeBuildUpScriptCoder|A module of the wizzi.mtree package that generates themTree build up script.|
|path resolution|Include and mix command nodes declare the path of the ittf documentthat must be mixed or included. At first the path to match is builtjoining the current folder path of the calling document and the nameof the callee document. If this match fails, then the 't' folder rule is applied,starting from the current folder path and going up on the folder tree.See 't' folder.|
|'t' folder|Folders named 't' have special rules for the path resolutionof mixed and included ittf documents. In the folder structureof a wizzi factory package, ittf documents contained in a 't' folder,can be referenced with the same rules that apply to nodejs packagesin 'node_modules' folders. They are searched up on the folder tree, until therelative path of the mixin or include call is matched or the path resolution fails.|