XMLGameEngine is a VGDL (video game description language) and an engine for running games completely contained within an XML file.
Status: Built. Reference: the game file.
pong.xml; name and class are HTML’s), validated before the game runs, and transformable (XSLT makes a program of it, generator).<map>; pictures are bitmaps. No level files, XInclude or shared files across games.objectParts), used by objects, groups and map pieces, so they cannot drift apart. Before, four copies had drifted.<active>false</active> is out of play until revealed; <drawn>false</drawn> is in play but unseen; <enabled>false</enabled> in collisions is seen but touches nothing. active was hidden, which read as “not drawn”.<chase object="hero">2</chase>; extras follow as named tags (<jump direction="up">40<seconds>0.3</seconds></jump>). One rule beats remembering which verbs wrap their number.<collisions> is on. No <collisions> still touches nothing.Reached by removing a small scripting language that had grown inside attribute strings (src="shape.circle(r,'color.white')", action="inc('p.score');reset()").
name, class, object, edge, direction, pitch…). Everything else is element content; a command list is an ordered list of tags.; hides sequencing that document order shows.| Option | Verdict |
|---|---|
| Function-call strings | Opaque to XSD and XSLT. Removed |
| One element per call | Verbose |
| Functions become elements and value tags; plain arithmetic stays text | Chosen |
button="space p", keys="a b", number="2 4 6") are now an element each, written first: <button>, <keys>, <number>, <odd />. An attribute is an xs:NMTOKEN, so the schema refuses a space. <button>, not <key>, since it names pad buttons too. Rejected: <key value="s" /> wrappers, repeating the input per key. pitch="F#4" stays: one standard name, like a colour’s.ruleFor), so both agree.<collision> differ by attribute, which XSD 1.0 cannot tell apart; two tags would let the schema check it.