...so what's the point of this if it depends on a native library? If you could do a minecraft and include it for all platforms and then determine the OS and use the right one, I guess it could be useful.ZephyrMC wrote:lxp is LuaExpat. I don't include it with Gwee because part of it is a native library, and I don't have a good (portable) way to resolve the dependency. This is actually a good time to point out that a link to a pure Lua XML parser would be awesome if anyone knows of a good one
Code: Select all
return {
{ kind="button", id="foo", x="100", y="100", h="100", label="Button!" },
{ kind="textfield", id="field", x="100", y="200", w="100", h="30", label="Text Field:" }
}Code: Select all
<interface>
<button id="foo" x="100" y="100" w="100" h="30" label="Button!" />
<textfield id="field" x="100" y="200" w="100" h="30" label="Text Field:" />
</interface>How do you define "a good one"? Anyways, there are some pointers:ZephyrMC wrote:lxp is LuaExpat. I don't include it with Gwee because part of it is a native library, and I don't have a good (portable) way to resolve the dependency. This is actually a good time to point out that a link to a pure Lua XML parser would be awesome if anyone knows of a good one
It should be reasonably easy to adapt it to use pure lua code in addition to xml.
Fair enough. I will work on a pure Lua version of the layout loader this afternoon.Yeah, the xml lib is stopping me from using. In all honesty, it would make it a lot easier to just define it all in lua, seeing as the people who would use it know lua already.
Also, this intrigues me.automatically generated from the later via xslt
Well, the widget set itself doesn't depend on a native library. The XML layouts module does, though, and the example uses the XML layouts module....so what's the point of this if it depends on a native library?