tree

• tree_macros.vm, xwiki-platform: the defaults of the tree options, the boolean options read as true only for the value "true", the parameters only passed to a dynamic tree source, and the Class parameter replacing the default xtree class.
• TreeTranslations.xml: the name, description and parameter texts; exclusions has no translation key, so its name is its ID in every language.
• Uses in XWiki Standard: only dynamic trees, {{tree reference="XWiki.DocumentTree"/}} in the macro page and the VFS tree macro; the Page Tree macro uses the tree Velocity macro instead.
• documentTree audit: the Page Tree macro, built on the same tree widget, shares root, openTo, finder, showRoot, limit and exclusions.

C1: the description "You can use nested HTML unordered lists to describe the tree structure. See http://www.jstree.com/docs/html/ for more information." speaks of HTML and of the jsTree library, while the user types a wiki syntax bulleted list, and does not say that anything other than a bulleted list, like a paragraph, a table or a numbered list, is dropped, see E2.

C4: edited only in the plain text area of the Edit Macro dialog, recorded under E6.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C1: "Reference" does not say that it is the page providing a dynamic tree, and the description uses technical terms, "resource", "URL/path", without saying that a URL needs the "path:" prefix, which only the documentation gives.

C4: a plain text field for a page reference, where a page picker could be used.

C7: an alternative to the content, a dynamic tree instead of a static one: only parameters can be part of a feature, see the Cross-macro findings.

C13: the accepted format depends on the tree source, a page reference or a "path:" URL for Reference, a node id like document:xwiki:Main.WebHome for Root and Open to, and the macro declares none: the wiki macro parameters cannot declare a format, see XWIKI-25197 in the Cross-macro findings. A format that changes with the use case hints that the static and dynamic trees could be two macros.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C1: "root node id" is technical, and the description does not give the format of a node id, like document:xwiki:Main.WebHome, nor that it only works with a dynamic tree. It also says the root node is not displayed, while showRoot can display it.

C4: a plain text field for a node id, where a node picker, like the Root field of Page Tree, could be used. The picker would depend on the tree source, another hint that the static and dynamic trees could be two macros.

C13: the accepted format depends on the tree source, a page reference or a "path:" URL for Reference, a node id like document:xwiki:Main.WebHome for Root and Open to, and the macro declares none: the wiki macro parameters cannot declare a format, see XWIKI-25197 in the Cross-macro findings. A format that changes with the use case hints that the static and dynamic trees could be two macros.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C1: the parameter looks like the cssClass of other macros, such as box, container or code, but it is named differently and does something different: the description says the classes are added, while they replace the default xtree class, so {{tree class="foo"}}* A ** B{{/tree}} renders a plain bulleted list instead of a tree, see tree_macros.vm. Name and behavior should be aligned with cssClass.

C8: a styling parameter that most trees do not set, not marked as advanced.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C1: "The id of the node" is technical, and the description does not give the format of a node id nor how to give one to a node of a static tree.

C4: a plain text field for a node id, where a node picker, like the Open to field of Page Tree, could be used. The picker would depend on the tree source, another hint that the static and dynamic trees could be two macros.

C13: the accepted format depends on the tree source, a page reference or a "path:" URL for Reference, a node id like document:xwiki:Main.WebHome for Root and Open to, and the macro declares none: the wiki macro parameters cannot declare a format, see XWIKI-25197 in the Cross-macro findings. A format that changes with the use case hints that the static and dynamic trees could be two macros.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C4: a plain text field where any text can be typed, while the value is a number of child nodes, which a number field would fit.

C13: the macro is a wiki macro, whose parameters cannot declare a range or a format, see XWIKI-25197 in the Cross-macro findings.

C5: the only group, Optional parameters, holds the 15 fields of the dialog, content included, above 7 ± 2, in alphabetical order, mixing the display options of every tree with the parameters that only work with a dynamic tree.

C1: the name is the parameter ID, "exclusions", in every language, since the parameter has no translation key, and the description, left in English, does not give the format of a node id.

C4: a plain text field for a list of node ids, where a node picker with several values could be used. The picker would depend on the tree source, another hint that the static and dynamic trees could be two macros.

C13: the macro is a wiki macro, whose parameters cannot declare a range or a format, see XWIKI-25197 in the Cross-macro findings.