   MFC Alternative (winapi in classes)
  Greatings!I was wondering whenever there is an TINY MFC Alternative, somekind of WINAPI wrapper in classes? I have seen something like that in ATL (CWindow) but I do not want to use ATL in my project. Is there something like that allready existing? Perhaps in boots or anywhere else? Sourceforge?Something like that:cWindow* pWin = new cWindow(320,240, "Caption");cButton* pButton = new cButton(pWin, 50, 50, 100, 100, "Exit");I could do it myself, but perhaps I could save some time? I have also some design problems, I do not want to have too many virtual functions and some easy way to provide listeners etc...Thank you in advance.   
  I know you didn't ask for something platform-independent, but did you check out wxWidgets or QT? Both are object-oriented GUI programming libraries which are supported on Windows, Linux/UNIX and Mac. Neither is exactly tiny, so this may not be what you want but I thought I'd bring it up just in case you aren't aware of these options.   ;  WTL may be what you're looking for...Try a google search on it.   ;  WTL: http://wtl.sourceforge.net/if you're using msvs2005, get version 8.0And for your information, the entire WTL is only a series of header files, no .cpp, .lib to link to. The only thing that you have to link it to is the ATL libs... which is pretty lightweight and could be statically linked without any heavy consequences. Some comparisons of WTL vs. MFC: http://www.endurasoft.com/vcd/mfcwtl.htmThough it still have those idiosyncracies of MFC like those BEGIN_MESSAGE_MAP() and message reflections...and alternative is wxwidgets: www.wxwidgets.orgor if you want a little more .net-ish: http://upp.sourceforge.net/   ;  If you want to play around,http://www.codeproject.com/useritems/DWinLib2Overview.asphttp://www.codeproject.com/useritems/DWinLib2BareWrapper.asp   ;  Thank you guys!I'll check all the alternatives to see what they offer. Most probably I will go for the WTL altough I do not like that MACRO stuff in the wdiget declarations. But anyway I believe it is still better that hundreds of virtual functions that might be overridden but in fact they newer are, so they just retud DefaultWindowProc.Thank you very much.   