WTL for MFC Programmers Guide: The Chinese version of the preface: Orbit (www.winmsg.com)
I have been looking for such a class library: His provides an object-oriented package, a flexible message response mechanism and a more complete interface framework solution, providing a concise and practical package for standard controls, supporting the new features of the operating system. Support function expansion and secondary development, code automatic generation wizard mechanism, generated program uses fewer system resources, and finally there is full code support and document support. You will say that you use the MFC! Yes, I have been using MFC, but I have been getting tired of MFC. The old class library makes it unable to support the new features of the operating system (the MFC class library is not updated after the version 4.21 version, and then in 1998, people use Windows 95 and Windows NT4), bloated message mapping mechanisms and for Compatibility reserved code makes the program efficiency, and the frame structure of the face has enabled the generated application and occupies too much system resources. When a functionally simple program uses dynamic links, it is more than 200K, and when using 3% -4% system resources, I decided to give up the MFC and find a new function similar class library. I have studied a lot of similar code, not too simple, unable to use the development of the application is the lack of code and documentation. There is a class library named ClassProject, I also studied it, has the basic interface framework, which has a simple package for the control, but it is not practical, the huge virtual function mechanism makes the object very bloated, can't Reduce the occupation of resources. I even made a simple class MINIGUI, formed a basic framework solution, but finally gave up, the reason is simple: I can't use the development of the application. An application interface frame is complicated, and there are too many things to consider, and developers cannot fight two lines in the application and interface framework. Just when I was about to be desperate, I met WTL. Since the needs of work often develop some COM components, the occasion that cannot use MFC is use ATL. ATL provides an object-oriented package and simple message mapping mechanism for the window, but ATL is too simple to develop applications. It is almost impossible. To make the ability of the ATL to have an interface framework solution, you need to do a lot, fortunately, WTL has done these things. WTL is a very strange thing. It is maintained by a team of enthusiastic programmers in Microsoft. It has never appeared on Microsoft's official product list, but you can download the latest WTL from Microsoft's official website. It does not have formal document support, use WTL to do keywords to retrieve only 0 results in MSDN, but the world's development website has a list of WTL discussion groups and mailing lists, any problem will be passionate. I have compared MFC and WTL, find that there are many incisions, and the functionality of MFC can be implemented in WTL, but the method is different. I have almost impressed the power of the power to rewrite the WTL of the previously written MFC program. The WTL program using a static link is smaller than the MFC program that uses dynamic links. The resource takes only half of the MFC program. But the warmth of enthusiasm can solve the lack of documentation, although there are many examples of using WTL and instructions on the Internet, almost all of the sharp effects of MFC can achieve, but they are all rebellious grafts.饩觯 狈 ο 低 厝 樯踬 樯踬 文 文 文. At this time I saw Michael Dunn's "WTL for MFC Program" series, my feelings and in 1995 I saw MSDN for the first time, almost can't wait to finish it, at the same time Also germination translated it into a Chinese impulse. So I wrote an email to Michael, I hope to be authorized to translate his article into Chinese (in fact before this, I have translated two chapters).
