A page level unique name identifying a control.

A human readable comment.

Determines whether a control is initially visible. True by default. Could be data-bound to an SQL expression.

Determines whether a control is visible. True by default. Could be data-bound to an SQL expression.

Determines whether a control instantiates its children. It is true by default. It could be data-bound to an SQL expression. Unlike most of calculable attributes, the value of this attribute for a control is calculated before calling 'on-init' event handler of the control; other values are calculated before calling 'before-data-bind' event handler.

At run time every control is represented as an instance of some user-defined type (UDT). VSPX compiles and selects the UDT to use depending on name of the XML element that represents the control and maybe some of its attributes. In some specific cases the application developer may instruct VSPX compiler to use some other UDT, e.g. an application-specific UDT that is derived from the preset one. If specified, the value of 'control-udt' attribute should be equal to the name of the desired target UDT.

This attribute is for internal use only. It has no effect if added to the source VSPX file.

Visible width of the control when it is displayed in WYSIWYG tools when the source VSPX text is edited. The value of this attribute will not be used when the resulting HTML is rendered.

Visible height of the control when it is displayed in WYSIWYG tools when the source VSPX text is edited. The value of this attribute will not be used when the resulting HTML is rendered.

This attribute is obsolete and has no effect.

This determines whether more than one branches can be open at one time. The values are 0 and 1 (true and false). The default is 0 (false).

This can be 'horizontal' or 'vertical', the default is 'vertical'. The tree can have different styles. The default is a vertical arrangement with open levels indented, the children under the parent node. Each node template is a single line. The horizontal style shows each level on a separate line. In this case it is not allowed multiple open branches. The children of the root will be shown on one line. When one is opened, its children will fill the next line.

This is a SQL expression which produces the root object. This can be of any data type, a file system path is an example.

create procedure root_node (in path varchar)
{
  declare i, l int;
  declare ret, arr any;
  arr :=
    vector_concat (sys_dirlist (path, 0), sys_dirlist (path, 1));
  return arr;
};
          

Given the result of the root expression, this must generate an array of similar elements corresponding to the children of the node in question. This same function should be applicable to each element of the array it returns. If the array is empty then the node in question is a leaf.

-- Example of this function
create procedure child_node (in node_name varchar, in node varchar)
{
  declare i, l int;
  declare ret, arr any;
  declare exit handler for sqlstate '*'
    {
      return vector ();
    };
  if (isstring (file_stat (node_name, 3)))
    return vector ();
  arr :=
    vector_concat (sys_dirlist (node_name, 0), sys_dirlist (node_name, 1));
  return arr;
}
;
          

This is an expression which will be evaluated and passed to the 'root' function as argument.

This is an expression which will be used as XPath expression to designate which branches of the tree are open and which are not initially.

URI of the source document where the tag comes from.

Line number in the source document where the tag comes from.

This defines what sort of data are saved to the debugging log.