Difference between revisions of "Category:Oblivion XML"

265 bytes added ,  12:33, 19 December 2009
imported>JRoush
imported>JRoush
Line 27: Line 27:
Property elements can have literal values, written directly into the xml code.   
Property elements can have literal values, written directly into the xml code.   
They can also contain mathematical "formulas" - for example the <width> property of an <image> element might contain a formula to make the image twice as wide as it is tall.  Then, if some code in the game engine (or a mod script) changes the height of the image, the game's parser will automatically use the formula to recalculate the width.  These formulas are expressed as series of [[Operator Element|"Operator" Elements]] - most basic mathematical operators like +, - , *, FLOOR, AND, etc. have a corresponding Operator Element.
They can also contain mathematical "formulas" - for example the <width> property of an <image> element might contain a formula to make the image twice as wide as it is tall.  Then, if some code in the game engine (or a mod script) changes the height of the image, the game's parser will automatically use the formula to recalculate the width.  These formulas are expressed as series of [[Operator Element|"Operator" Elements]] - most basic mathematical operators like +, - , *, FLOOR, AND, etc. have a corresponding Operator Element.
There is one recognized element that does not fit into a category: the [[Include Element]].  It's use is similar to the ''include'' statement in C-style programming language - it allows the menu designer to copy in bits of commonly used xml code from other files.


Elements that aren't part of the Oblivion XML schema are assumed to be Property Elements.  They will be parsed by the game engine, can be referred to by name from Operator elements and OBSE script functions, and may contain Operator Elements as children.  It is common to break up long formulas by inventing an unrecognized element to hold intermediate values.
Elements that aren't part of the Oblivion XML schema are assumed to be Property Elements.  They will be parsed by the game engine, can be referred to by name from Operator elements and OBSE script functions, and may contain Operator Elements as children.  It is common to break up long formulas by inventing an unrecognized element to hold intermediate values.
Anonymous user