Here is MHO, if anyone cares to know it.
Why i dont
1) its too buggy!
lets face it, too many things dont work as expected, some do work, but not all the time, some not at all. i think that the people developing wxWidgets should give top
priority to fixing the bugs on the current features and ports, ----BEFORE----
even thinking about adding more features / ports. I would much prefer it if wxWidgets was only for MSW, Linux & MAC, working 100% in all ports, that the way it is now, ported for god knows how many things, with none
of these ports being reasonably bug free.
As for its features, well, same as with ports, i would prefer it if wxWidgets had fewer features that work
that it having tons of "usefull stuff" that are unreliable (wxGrid anyone????)
2) poorly documented
Yes, i know, "wxWidgets has a very rich documentation", and it does!, the problem here is that it is extremely
messy, in other words poorly organized, and in too many cases, poorly mantained. Heres an example of this: There are probably dozens (if not 100s) of wikis, posts, blogs, readmes, howtos on how to compile the library, Still
check out the formums here, there are probably 1000s of topics on compiling related problems. Why? because for someone attempting to use the library for the first time, there isnt a single
place he can go, and recive full from start to end
instructions on how to do it, instead, he has to read the .txt on the distro to "get started", then check out wxWiki (if for example he wants to know about the issue about linking statically to the CRT), then check out the forum to maybe figure out why his app keeps asking for setup.h, and probably still ask a couple of questions about why he cant get the minimal sample to compile, before he can get the lib working.
3) the devs dont seem to listen to us (the users)
This is probably the reason of most issues in wxWidgets. I dont mean any offense, but It seems that the philosopy of the devs is that they are developing wxWidgets for their own personal use, and are generously "sharing it" with us. If this is in fact the case, then of course there is no point in me still typing this. Buf it it isnt, then listen to us
Want an example of this? see point 2 above. That "small issue" about the need for a single complete (and i mean really complete) guide to building the library has been evident and "mentioned" since i started using wxWidgets, still, no such guide exsists.
4) There are probably other specific things i dont like about wxWidgets, like the "silly" (i say silly cause stupid sounds offensive) idea of passing a wxArrayString to a validator when a simple wxChar* or wxString would do, or the fact that it seems (again) "Silly" to have to include .cpp files, and put 2 macros just to say i want an array of objets, when a simple template would suffice. And some other things i dont remember right now.
i realize that this are not
problems with wxWidgets, the problem here is the fact that it is IMPOSSIBLE
to please everyone, if they would change (for example) the issue with validators i mentioned above, im shure someone would complain, just like i complain about how it is now.
So, if i dont like it, WHY IN GODS NAME DO I USE IT???
The answer to that is actually very very simple.
Even with all its bugs, documentation problems, etc., wxWidgets still is (IMHO) the best library for writting apps using C++ in exsistance today
Example: WTL? (what i used before), its too small, it is strictly GUI without and support for networking, database etc. And there is more to writting apps than just windows & buttons. Plus, it is, 100%, completely undocumented.
MFC? let me put it this way, if MFC were the only option for writting apps in C++, i would quit writting code for ever. Its competely restrictive, it tries to shove its "doc-view" arch. down your throat, and the result is you spend more time "hacking" the damn thing to do what you want, that coding your app.
Qt? I wouldnt mind (too much) dropping $3,000 bucks for it if i liked it, but i dont like the Signal - Slot stuff, and i absolutely
HATE the fact that to compile my apps i need the MOC, POC, PHUK (or whatever is called) "pre procesor" or "compiler" or whatever it is.
Java, .Net, etc? heh, dont get me started...
It would be stupid (not just silly
) of me, to just point out the problems with out sugesting
1) Devs, please
listen to us!, check out the forums more often, hear what we think!
2) Clean up the library, im shure im speaking for most users of wxWidgets when i say, get rid of the bugs before implementing new features or ports
3) Organize, extend & update the documentation. Like i said before, there is a lot of it, but its messy.
4) i also think i speak for most users when i say this:
If you are still using & supporting prehistoric C stuff & compilers because you dont have the time to do a full "overhaul", then we understand, well be patient and help out where we can. BUT
if this philosopy is intentional
loose it!, there is no reason to support some accient relic like Turbo C, at the expense of the library being inefficient and full with arcane code.
Hier Kommt die Sonne...