Code Type:
Code Scope of Action:
Code First Added:
Code Altered:
^outboundBasicLinks( [start, list-item-prefix, list-item-suffix, end, type] )^
returns an unordered list, excluding prototype links, to all of the notes to which the current note has basic (note-level) links.
The optional parameters allow you to format the group of links as an HTML list or table in the exact format you want, where start is text that will be inserted before all of the links, end is text that will be inserted after all of the links, list-item-prefix is text that will be inserted before each link, and list-item-suffix is text that will be inserted after each link. The type parameter restricts the scope of link inclusion and is discussed separately below.
If start, list-item-prefix, list-item-suffix, end are omitted then the default values of <ul>, <li>, </li>, </ul> are used.
The optional fifth argument, type, lets you restrict exported lists to specific link types, as in the named types seen in the TBX's Link Types palette. type my be omitted but if you do wish to use it, the preceding 4 parameters must all be specified. For example:
^outboundBasicLinks(<ul>,<li>,</li>,</ul>,example)^
will list only inbound links of type "example". As the type argument is a regular expression, besides specifying a particular link type name, you can specify wildcard characters or lists of eligible link types, etc.
^outboundBasicLinks(<ul>,<li>,</li>,</ul>,(example|untitled))^
will list links of the types "untitled" and "example".
Also see ^outboundTextLinks^, ^outboundWebLinks^. The logical opposite of this code is ^inboundBasicLinks^.
This code exports CSS class and target based on their underlying Tinderbox link values - assuming these are actually completed; the link type value is not picked up as a class name.
New item objects source and destination may be used to indicate from where data used within the arguments is drawn.