About GUI

Well, we need more informations about what language are you using, what environment, what do you call a simple example, what do you want to (write a GUI system or use one) and so on.

Regards,

er...
Basically it will be used for a PC platform game.
Using C++ and DirectX...
My friends are writing the game engine and we hope to make a simple GUI system if possible or we can use other useful middleware...
The needs of GUI is like common PC games' but it's better to support 3D objects as buttons or sth...
So I want to find some examples with source codes and learn how to write or how to use...

Go to the top of the page where it says Resources and click on 'Articles & Resources' and then 'DirectX'. There's a pretty nice set of tutorials in there for creating your own directX gui. If you dont want to start from scratch though you could always use the gui stuff that comes with DXUT. Check out the directX SDK documentation for more info.

In the future, for in game guis, I will use imgui (clicky), for applications, editors etc I will use wx.

I second IMGUI. It's really intuitive, and although there's a bit of boilerplate that can be dealt with with some up-front design, it's surprisingly powerful.

Thank you all!
I have gone through IMGUI
I found it's really neat =)
But I don't understand more about that...
In my opinion,it uses a process-orientat way to deal with UI and you should render every widge by its state in every frame...
Is that right???

I want to know wether it is more useful than traditional ways...
DX's UI system is not suitable for me because it's too complicated...

As far as I can tell, IMGUI is a good option. I recently watched the online lecture from Molly Rocket and read through the SDL tutorial online. I was just starting the GUI for my demo the old way (iWidget<-cBaseWidget<-cButton, etc). Then I quickly reimplemented a couple of widgets using an IMGUI approach and it's going quite well. It seems to take less time and because it doesn't really follow OOD, you aren't worrying about changing something in a unified base class/interface that will propagate down and cause mischief. Although, it definitely feels a bit unusual to be storing a widget's state in 'client' code, but the results are positive so far.

I'd recommend taking a look at IMGUI as an approach, but as with everything in programming, there's more than one way to solve a problem.