Approx. 22 year ago, I created simple GUI. http://uloz.to/xbdamBRj/scantybasic-zip

Yes, I know what it is. On the other hand. GUI is useful

Yes it seems a lot more complicated than mine. However, if I were to create a level editor (not applicable to my game) I think I would use an already existing GUI, it's not so easy to find a OpenGL or DirectX GUI, though. Because since the editor is ¨not part¨ of the game it wouldn't matter if the GUI is ugly and already used in other projects, that could actually be a point in your favor because people may be already used to that aspect or feeling of the GUI. But... I don't know, I guess that if you implemented your own XML parser is because you're using it as a learning process so it's better to do everything by yourself.

Yes it seems a lot more complicated than mine. However, if I were to create a level editor (not applicable to my game) I think I would use an already existing GUI, it's not so easy to find a OpenGL or DirectX GUI, though. Because since the editor is ¨not part¨ of the game it wouldn't matter if the GUI is ugly and already used in other projects, that could actually be a point in your favor because people may be already used to that aspect or feeling of the GUI. But... I don't know, I guess that if you implemented your own XML parser is because you're using it as a learning process so it's better to do everything by yourself. biggrin.png

Yeah, if I were to go back and start over I would probably use an existing gui system too. Not to say that I can't work with my own gui and that there isn't some neat stuff that probably ties in better to my overall system than an external libary would, but there is almost at least one "WTF? why is it doing that (again)???" every day . But you said it right, its all part of a giant learning process, for that reason I've decided to enroll almost everything on my own. But it really paid off, I've been learning so much let alone via the gui system about decoupling systems, and (ironically, looking at my first post) writing cleaner and more maintainably code. My old projects always died after a few months because the code became too messy for me to work with, this engine I'm working on for about 1 1/2 years, and still going. So people are right in a way that writing your own big guid lib for something like editor is a waste of time, but only unless for the learning experience, that is.

Eh, your code actually looks pretty slick, considering you're doing GUI programming. Also, the "established libraries" for GUIs are notoriously bulky, so hand-rolling a solution is actually a viable option in this case.

In my own table-driven programming language (Steamroller), I would just put all the values and method pointers in a table and read it from a tiny loop. I just haven't been able to connect the language to a graphics API yet.