I've heard nothing but good things about wxWidgets since I first found out about it. I decided to try it for the first time last night around 9:00 P.M. central timezone USA. It is 5:40 A.M. at the time of posting this and I have yet to get it do to compile anything. I've been through so many errors in the past 8, almost 9 hours I can't remember which one came first. So, as a result I've decided to forgo any more wxWidgeting until a further point in time. Preferably one where I'm not about to snap from frustration and begin killing small animals.
Anyways, can some one tell me if they too had a similar experience with wxWidgets?
I'll be sure to look into it. How big is the memory footprint for a Qt program in comparison to an equivalent program with it's gui programed using wxWidgets? I'm going to be using what ever I use to build the Gui of a program I will be distributing among my friends, one of which is an ultra minimalist. Because of him I'm trying to keep the memory usage low.
Well, first I tried installing it under slackware. When that didn't work out I booted into Ubuntu, and made my first wxWidgets project, upon compiling it gave me a deceivingly simple error that when fixed lead to another, and then another, and then I gave up and booted into windows 7. I ran the installer for windows, and then read the install.txt file only to find that it references an included setup program that doesn't exist. (They said it was there, it was not there.) I tried manually compiling the source via Visual Studio 2010, but that just wasn't working out. Arund that time I said "To hell with it all" and posted here.
in defense of wxWidgets I had no problems setting it up in xp, windows7, unbuntu, or debian. I only played with it but setting it up was straight forward. I always work with vim and makefile because because like the simplicity; sometimes when I hear people complaining about a new library I wonder if their real problem might not be with the library but with the overly complex set-ups these IDEs require.
Setting up with a generic makefile is as simple as listing the correct libraries and includes.
Actually, wxWidgets is probably the easier toolkit I've found to work with. Also, it's currently *the only one* that uses native widgets. GTK+, Qt, whatever do not. They generally use native windowing but not native widgets.
However, as far as I know, there is usually just a slight efficiency gain in this but supposedly the most important feature is that it's *native* if you care at all about that. This is generally difficult to implement as well (especially cross platform wise). wxWidgets has multiple implementations that uses various libraries. For instance, wxWidgets can sit on top of X directly or it can use the GTK+ library. For Windows, it can use the WinAPI directly. There's also various micro devices implementations supposedly as well as various community based widgets such as wxSkin, etc.
Even then, wxWidgets does indeed need a makeover but it's easily usable now and I've never had a problem with it.
On a side note, if you want an application as small as uTorrent, then use the native windowing toolkit directly. I'd like to see this done with Xorg :P