23 replies to this topic

[mdwh]

I too think Qt is great, and use it for Windows, Linux and Symbian. (Have no experience of WxWidgets to compare though.) You can even use it for game programming, which I'm doing for my current Nokia project (though for desktops, things like SDL seem more commonly used).

Isn't MFC about a decade out of date? Well personally I think it was dreadful even back then, but even if you want to do it the "Microsoft official" way, they've moved on to newer APIs (presumably with the recommendation of using C#).

It's true that Qt works with a modified C++, but it works well I find (and Microsoft have made their own modifications to C++ to get it working with managed code for their more recent APIs anyway, which in my opinion looks messier than what's done in Qt).

I have a GUI system in place for my own app that I am working on. Rolled it in less than a day. There is nothing that I can't do with it. So, it is good for what I want (currently games programming).

Nothing? I'm not convinced you have anything near the full functionality of a UI toolkit in a day Though it is indeed possible to roll something good enough for a simple game.

It depends what the OP is asking for. If he wants to make graphical games, then the next stop is not a GUI toolkit - or indeed, a GUI at all. He's better off learning writing simple games before worrying about that. If he is asking about non-game applications, then he is certainly better off learning to use a standard GUI toolkit.

[jrdmellow]

I never coded a single bit of C# in my life, however I do have quite some experience with GUI coding (in C++) using wxWidgets, which I think totally rocks. But since I can't compare from own experience: what makes coding GUIs in C# a better choice over C++ with wxWidgets?

A bit off topic but I've coded quite a bit in both and I prefer C++ (I'm an engine programmer). I can say from experience that trying to bridge between an engine in C++ and an editor in C# is more work than I'm interested in doing. I was looking at QT for my editor, but after reading your comment about wxWidgets I am definitely going that route. Thanks for opening my eyes to more options

[lonewolff]

I have a GUI system in place for my own app that I am working on. Rolled it in less than a day. There is nothing that I can't do with it. So, it is good for what I want (currently games programming).

Nothing? I'm not convinced you have anything near the full functionality of a UI toolkit in a day Though it is indeed possible to roll something good enough for a simple game.

Thats fine to go negative rep me mdwh. But, as I said, (for the reading impaired) there is nothing I can not do with it.

So, I would not have a clue what 'UI Toolkit' can do, as thus far, I have not needed a 3rd party GUI.

Its a GUI for F*#K sake, it is not that hard.

Either that or that fact that I have been coding for 23 years and trivial stuff doesn't phase me.

[mdwh]

I have a GUI system in place for my own app that I am working on. Rolled it in less than a day. There is nothing that I can't do with it. So, it is good for what I want (currently games programming).

Nothing? I'm not convinced you have anything near the full functionality of a UI toolkit in a day Though it is indeed possible to roll something good enough for a simple game.

Thats fine to go negative rep me mdwh. But, as I said, (for the reading impaired) there is nothing I can not do with it.

That wasn't me. It was already negative when I read your post.

So, I would not have a clue what 'UI Toolkit' can do, as thus far, I have not needed a 3rd party GUI.

Its a GUI for F*#K sake, it is not that hard.

Either that or that fact that I have been coding for 23 years and trivial stuff doesn't phase me.

A UI toolkit will do whatever you see in Windows, basically. Listboxes, text areas (with scrolling and editing)? Tabs? A UI that dynamically positions and sizes the elements for you? Drag and drop from the OS? Multiple movable windows? I'm impressed Given that the OP is a beginner, I'm not sure implementing a whole UI will be quite so easy as it is for you though. And how do you make it work so your application plays nicely with Windows (i.e., appearing and behaving as a native application)?