[Esamynn]

Originally Posted by Rowne In case the point on XML isn't clear; XML only generates extra globals through incorrect use. For example, if you were to use AceGUI and then put all elements in a '$parent' system, then I believe only the main element is global and then the '$parent' name elements are subelements withint he global element's environment. So for example ... BlahFrame BlahFrameText This would be two global elements. BlahFrame $parentText This would be one global element of BlahFrame with a subelement of Text inside it. I need to do more research to provide proof to that however. And with the overall size of XML and the variables within, as I said, Ace and AceGUI cut down on that or make it non-existant.

Sorry, not so. Take the example below.

<Frame name="BlahFrame">
	<Frames>
		<Frame name="$parentText"/>
	</Frames>
</Frame>

This xml code would create two global variables in the Lua namespace. BlahFrame and BlahFrameText. Blizzard would have to shift their parsing of the XML over to an OO style for you to get BlahFrame and BlahFrame.Text.

Edit: The same is true of XML templates.