Difference between revisions of "Property Element"
m
no edit summary
imported>JRoush (Rebranding XML "traits" as "attributes"; minor wording changes) |
imported>JRoush m |
||
Line 1: | Line 1: | ||
Property Elements are a subgroup of the elements in the [[:Category: Oblivion XML|Oblivion XML]] schema, always found as children of [[Object Element]]s. They define the properties of their parent element - position on the screen, color, texture, etc. In this sense they are similar to traditional xml '''traits'''. | Property Elements are a subgroup of the elements in the [[:Category: Oblivion XML|Oblivion XML]] schema, always found as children of [[Object Element]]s. They define the properties of their parent element - position on the screen, color, texture, etc. In this sense they are similar to traditional xml '''traits'''. | ||
A '''Note''' on the name - Bethesda apparently referred to these elements as "Traits" internally. Likewise, they are called "traits" in the OBSE documentation and several script functions. As noted above, this makes sense given their purpose. However, strictly speaking they are ''elements'' | A '''Note''' on the name - Bethesda apparently referred to these elements as "Traits" internally. Likewise, they are called "traits" in the OBSE documentation and several script functions. As noted above, this makes sense given their purpose. However, strictly speaking they are ''elements'', and in XML "trait" is often used synonymously with [[XML Attribute|"attribute"]]. For the purposes of this wiki, the name "Property Element" was chosen to be clear and unambiguous. | ||
There are two basic data types for properties - numeric and string. A number of Oblivion-specific XML entities are defined for commonly used constants of both types. Particularly useful are the numeric entities "&true;" (numeric value 2) and "&false;" (1), used to with boolean properties like Visible or Targetable. | There are two basic data types for properties - numeric and string. A number of Oblivion-specific XML entities are defined for commonly used constants of both types. Particularly useful are the numeric entities "&true;" (numeric value 2) and "&false;" (1), used to with boolean properties like Visible or Targetable. |