|A Tinderbox Reference File : Export Codes : Export Code Arguments|
Export Code Arguments
The argument action refers to a statement that can be evaluated as if an Action or Rule.
The arguments argument and anotherArgument refer to text or code supplied as macro arguments.
The argument attribute refers to an explicit attribute name.
The argument count refers to a number, in figures, e.g. 5 not five.
The argument css class is the (text) name of a CSS mark up class.
The argument data (data1, data2, etc.) refer to either:
The argument date refers to either:
The argument expression refers to a statement that can be evaluated and assigned to an attribute.
The argument format refers to either:
The argument group is either:
The argument item is either:
The argument N refers to a number, in figures, e.g. 5 not five.
The argument precision refers to the number of decimal points that are exported.
The argument path refers to the path to a note or agent (including the latter's Name).
The arguments start, list-item-prefix, list-item-suffix, start, list-item-prefix, list-item-suffix, end refer to optional alternate HTML mark up and text for a list of links.
The argument target refers to either:
The argument template refers to a template file name either:
Export argument value may be enclosed in double quotes. The quotes will be ignored, but doing so can help avoid parsing difficulties. Use of quotes for string values is recommended. This is because many new operators have been added and the scope for misinterpretation of string literals as code has increased. For example, if a note is named ...
... the comma would confused the parser in expressions like:
^linkTo(she, shyly)^ <- won't work
... so this may (optionally) be written with double quotes:
Link lists can use two new references in their optional mark-up arguments:
|Up: Export Codes|
|Previous: Export Code Scope||Next: Group Codes|
Licensed under Creative Commons Attribution-Noncommercial-Share Alike 3.0 License
[See aTbRef CC licence Attribution/Waiver info info]