To store some additional data, which need not to be displayed, but may be useful for some client side operations - userdata sections can be used.

Because there may be many userdata tags per item, they differ by name attribute. Value of name attribute used on client side to get related tag content.

tag represent start point of path route

Mandatory attributes

id - id of path, must has pathend tag with equal value

Optional attributes

color - color of route line

mode - used line type

width - width of route line

tag represent start end of path route

Mandatory attributes

id - id of path

id of path ,
must has pathend tag with equal value
must be unique per tree

id of path ,
must has pathstart tag with equal value
must be unique per tree

Color of line

Width of line,
integer expected

Mode of line : solid, dashed, etc ( any value of css "border-type" can be used )

tree

tag represent the whole tree, or some branch inside it

Mandatory attributes

id - id of related parent element

Optional attributes

radio - switch checkboxes to radios for all tree

order - sort items after loading

id of related parent element
by default tree has global root item with ID = 0, it can be redefined inside tree constructor
in case of dynamical loading attribute must point to related parent ID

if checkboxes enabled in tree, and such attribute present in XML - all checkboxes it tree will be replaced with radio buttons ( with appropriate change in checking logic )

if attribute present , the sorting functionality will be called on load ( separate extension! )
none - ignored
1 - ascendant sorting
other value - descedent sorting

item

tag represent element of tree, the result tree will have same hierarchy as tags in XML

Mandatory attributes

id - id of element

Optional attributes

text - label of item

tooltip - tooltip of item

im0,im1,im2 - custom images

imwidth, imheight - size of image

style - css text

topoffset - vertical space

checked - state of checkbox

radio - radio button flag

nocheckbox - remove checkbox from item

disabled - disable related checkbox

selected - item will be selected

call - onSelect action will be called on load

child - not loaded child mark

aCol,sCol - colors of item

closeable - allows|deny closing of item

locked - block any actions against item

identificator of item
must be unique per tree
can contain any combination of chars|letters

label which will be rendered on page, text by default, but can contain any combination of HTML tags if them correctly escaped
if attribute skipped - label can be set by itemtext tag

tooltip text used by value ( need to be enabled by JS api )
if missed - item text used as tooltip

Image of item - "leaf item" ( 18x18px by default ), if missed default image from applied skin will be used

Image of item - "folder in open state" ( 18x18px by default ), if missed default image from applied skin will be used

Image of item - "folder in closed state" ( 18x18px by default ), if missed default image from applied skin will be used

set width of image for current item
expect integer value
if you need to set new size for all tree - you can use JS API

set height of image for current item
expect integer value
if you need to set new size for all tree - you can use JS API

any css text here, it will be applied to label of item

allow to set custom space size between current item and previous one
it allow to separate solid tree in few visual groups
component expect that value will be integer ( size in pixels )

if checkboxes enable in tree, based on attribute value checkbox state will be set

0 or absent - unchecked

1 - checked

-1 - third state ( for 3-state checkboxes )

if checkboxes enabled then checkbox for item in question will be converted to radio button

even if checkboxes enabled, item with such attribute will not have checkbox
if you not using checkboxes - attribute not necessary

after loading item with such attribute will be preselected

if checkboxes used, item will have disabled checkbox

after loading, onSelect handler will be called for item in question
independent form selection in tree

attribute has sense only for dynamical loading
in case of dynamical loading - it state that item has sub-items which need to be loaded
tree expect that attribute will have value > 0 ( specifying exact value of sub-items not necessary, but can be useful in some scenarios )

item text in normal state

item text in selected state

if this attribute set to 0 then item will not react on any closing|opening attempts by user action ( it will be possible to change its state by JS API )

items which such attribute not respond on any user actions ( item can be unlocked by JS API)

really strange attribute
item with such attribute will be rendered as top one in related branch
it will be better to use it with caution