There's confusion and transition in C++ GUI programming right now: let's discuss

I don't know what's up with C++ GUI platforms, but everything seems to be in transition. The state of C++ GUI development right now runs from the confused (the recent Qt handoff between Nokia and Microsoft), the bizarre (trying to integrate Qt and Code::Blocks, for example), and the downright comical (take a look at SmartWin's home page outside of sourceforge: smartwinlib.org. Really.) My sense in the past has been that this meetup group doesn't focus a great deal on GUI stuff, but I think it's time for a meeting to try and sort this all out. Since things are a little up in the air -- (for example if an opensource foundation "forks" Qt, as some have suggested, will they rethink the whole moc and Signal/Slots mechanisms since Signal/Slots can be implemented with C++11 templates, as some have noted? Or will wxWidgets take the initiative to build their "ecosystem" to rival the range of Qt modules and fill a potential void left by Qt confusion?) -- this at least gives developers and companies a chance to influence what comes next. Like say, for example, 10gen starts to get really active in either Qt or WxW and cooks up new markets for MongoDB. (Maybe a Mongo plugin for Code::Blocks which could merge with the buggy Qt one and also improve it by using an embedded Mongo database for build and source info.)