-
Notifications
You must be signed in to change notification settings - Fork 102
Krona 1.1 XML Specification
ondovb edited this page Mar 16, 2016
·
1 revision
- Initial tags
- Required
-
<magnitude attribute="[attr]"></magnitude>
- This tag specifies that the [attr] attribute of each node should be used for its magnitude.
-
<attributes [attr1]="Attribute 1" [attr2]="Attribute 2"></attributes>
- This tag specifies which node attributes will be displayed when a node is selected and how they will appear.
- Only the attribute used for magnitude is required. Other attributes will only be displayed if they are included in this tag.
-
- Optional
-
<color attribute="[attr]" valueStart="0" valueEnd="40" hueStart="60" hueEnd="360" default="true"></color>
- This tag specifies that the nodes can be colored according to their [attr] attribute. In this example, values of [attr] from 0 to 40 will correspond to a hue gradient from 60 to 360. The
default
value of "true" specifies that this coloring will be enabled each time the chart is opened.
- This tag specifies that the nodes can be colored according to their [attr] attribute. In this example, values of [attr] from 0 to 40 will correspond to a hue gradient from 60 to 360. The
-
<datasets names="Dataset 1, Dataset 2"></datasets>
- Specifies how each dataset should appear in the list.
- Required if there is more than one dataset.
-
- Required
- Node tags
- Nodes should be represented by nested
<node>
tags. The hierarchy should start with a single<node>
to serve as the root. - The only required attributes are
name
and the magnitude attribute (as specified in the<magnitude>
tag). The magnitude of a node has to be at least the sum of the magnitudes of nodes within it. - To create multiple datasets, the value of attributes can be comma-separated lists. Attributes that have a single value will use that value for all datasets.
- Example
<node name="[name]" [attr1]="55,52,..." [attr2]="30,28,..." ...></node>
- Nodes should be represented by nested