XML

[Xothin]

CE,

After digging around and trying out a few things, I've come to the realization that the easiest way to create a GUI that's going to be easily customizable by the user is to do it in XML...

My question, do you have any samples or do any of your samples include XML layouts? Or maybe is there a tutorial on how to code up the XML files so that they are in a compatible format for CEGUI to read?

[Xothin]

Ok.. did some checking, found out demo 8 uses XML..

Guess I'll start poring over Demo 8 files and see what I can come up with.

[CrazyEddie]

In may ways, I feel that Demo 8 is a shining example of what can be done with the system. Not only does it use the XML files for loading everything, it also uses the (aborted) luabind scripting module to do everything else. Apart from some initialisation (for Ogre) and instantiating the Renderer and System objects, none of what you see in demo 8 is done in C++, it's all scripted in Lua

There's a ReadMe.txt file in cegui_mk2\XMLRefSchema that describes all the various elements and attributes that can be used in the XML files - it may be of use to you, especially if you look over it while reading the xml files from demo 8

CE.

[Xothin]

I was checking over the schema last night and think that I have a good handle on the XML system, but I feel that most of my issue is going to lie in scripting the button events.

Checking over demo 8, I noticed a lot of difference between 7 and 8, mostly in the way that things were handled.

I need a way to make it so that the functions can't be altered, but the interface can be, I think that's where my problem is going to be.

[gcarlton]

I've just had a look at the .lua in demo8, and I'm impressed. Is there any expected date for lua support? Perhaps even in optional form so the early adopters can compile and try it out before the main release turns it on?

I've been using CEGUI a fair bit, and I normally make up a wrapper class for each gui screen that does all the loading (using that layout), manipulating, etc of the widgets. The lua script seems a perfect replacement for all that stuff.

You know, once CEGUI gets data driven styles (widget appearances) in xml, and with the xml layout, xml imagesets, and lua script, its going to be pretty damn cool.

[Xothin]

I've done the same thing myself.

I make a wrapper base class, then create child instances of that wrapper that does each of my screens. Seems to work fairly well, and I can get access to all the variables I need and they're stored in one neat little package. ^.^

[CrazyEddie]

I've just had a look at the .lua in demo8, and I'm impressed. Is there any expected date for lua support? Perhaps even in optional form so the early adopters can compile and try it out before the main release turns it on?

For an ETA on the Lua support, I can only say Q1 2005. I have still to make a final decision on which binding technology to use; the only thing I can say on this at the moment is that it will almost certainly not be luabind (far too many compatability issues).

The Lua/luabind module that I was working on, and that was used in demo 8, is now completely ouf of sync with the current code (it doesn't compile atm). I may revisit this to get it to work, and release it as an 'unsupported' extension, though this would not be for a little while, as I have other priorities at the moment.

You know, once CEGUI gets data driven styles (widget appearances) in xml, and with the xml layout, xml imagesets, and lua script, its going to be pretty damn cool.

Hehe What you describe is effectively my vision of things, and when done will form the big 1.0.0 release. Demo 8 provided a tiny glimpse of what will ultimately be possible. Much of the work on the system has taken longer than anticipated for various reasons, though I am happy with the overall results so far

CE.