WTL 新参考：http://www.cnblogs.com/procoder/archive/2009/06/03/1495002.html
WTL 参考：http://dev.csdn.net/develop/article/74/74004.shtm
http://www.cnblogs.com/kylindai/archive/2007/11/28/974797.html(WTL8.0 调用 ActiveX 控件)
http://blog.csdn.net/xiangxiangouhongyuan/archive/2007/11/01/1862009.aspx(环境配置)
1.WTL 8.0 SDK下载：http://www.microsoft.com/downloads/thankyou.aspx?familyId=e5ba5ba4-6e6b-462a-b24c-61115e846f0c&displayLang=en
原作者姓名 采访：myan，翻译：cber
介绍
每一个，正在使用C++或者准备使用C++的朋友都应该仔细的读读这篇文章。
读者评分 10 评分次数 2
正文
WTL之父Nenad Stefanovic访谈录
采访：myan，翻译：cber
myan引介
作 为现代C++最重要的特色技术，template正在各个传统领域攻城略地。从基本算法与数据结构，到正则表达式与XML解析，从高性能数学计算，到资源 的分配与管理，从网络分布式计算环境，到组件模型创建，从静态多态性的维度扩展，到设计模式的自动生成，神奇的template显示出其令人叹为观止的强 劲实力，如果不是有一个隐隐的痛处，template爱好者简直可以去狂欢了。
这个隐隐的痛处，就是在GUI编程领域。
现 有的大部分成熟GUI框架和工具库，其定型时间都在90年代早期，不管是因为什么原因，总之我们根本看不到template技术在这些环境中的任何重要运 用。无论是专有MFC和OWL，还是开源的wxWindow和Mozilla, 以至于是专有还是开源都说不清楚的Qt，它们在其他方面有着诸多不同，偏偏倒是在对待模板技术上空前一致：严格限制在底层的数据结构领域内，抵制模板技术 流入GUI主体结构。最过分的wxWindow和Mozilla，在代码编写规范里严厉禁止使用1990年之后发展出来的任何C++特性，模板、异常、多 继承、STL等等，均在黑名单上。诸位有兴趣，不妨去看看，那与其说是一份C++代码编写规范，倒不如说是对C++现代特性在GUI领域应用的一份不公正 的判决书。
难道模板技术真的在GUI领域无用武之地吗？
WTL给出了一个响亮的回答。
WTL是微软 ATL开发组成员Nenad Stefanovic先生在ATL Windowing机制上发展起来的一整套GUI框架，运用template技术组织和创建GUI对象，构筑了精致的面向对象框架（没错，在这里 object oriented与template达成了精致的融合）。虽然没有获得微软的官方支持，虽然其使用者人数很少，但是确实是“用过的都说好”，有位微软 MVP人士甚至说，这是微软有史以来推出的最优秀的一个framework。真是一个有趣的讽刺，最好的东西居然不被官方支持。有关于WTL的流言不少， 比如这东西原本是微软内部专用，只是因为不小心才被泄漏出来等等，这更加剧它的神秘色彩。相信大家对它一定有不少问题。我们特别邀请到了WTL之父 Nenad Stefanovic先生，进行了一次网上的访谈，希望能帮助大家了解WTL的真面目。
【C++ View】：I think most of our readers are not very familiar with you, so would you please tell us your story here? We are very fond of that. What do you think about China and Chinese people?
【C++ View】：我想，可能我们的读者中有很多人对您还不是很熟悉，您能不能在此给我们简单介绍一下您自己呢？我们将非常乐意听到您的自述。还有，您能不能也对我们讲述一下您对于中国以及中国人民的基本看法呢？
【Nenad】: I am a software developer at Microsoft. Your readers will probably know me as a creator of Windows Template Library, WTL. I am from former Yugoslavia, where I finished school and started working on software development. I've been living in US for 10 years now.
I am intrigued and impressed by the Chinese culture and tradition. I think that China is now in a great position of progress as a country and a nation. I discovered that, being from former Yugoslavia, I already know many things about China, and getting to know people from China gave me a bit of the "everyday" life perspective as well. I'd like to learn more, so I hope to visit China one day.
【Nenad】：好的。我现在在Microsoft工 作，是它里面的一个软件开发人员。你们杂志的读者中可能有人知道，我就是Windows Template Library （WTL）的创作者。我来自于前南斯拉夫，在那我完成了我的学业并开始了我作为软件开发人员的工作生涯。现在，我在美国居住的时间已经超过了10年了。
中 国的文化以及传统给我留下了极为深刻的印象，我对此十分感兴趣。我想，作为一个国家以及民族，中国已经处于一个伟大并且不断在成长中的位置上。作为一个从 前南斯拉夫来的人，我早就了解到关于中国的很多事情。在与来自中国的人民的接触过程中，我还了解到了你们日常生活的一些状况。我还想了解更多（有关中国的 事情），希望有一天我可以到中国来游览。
【C++ View】：When and why did you first think about WTL? What's its original purpose? How do you see its future?
【C++ View】：您是什么时候开始想起要开发WTL呢？为什么？您在开发它时的最初目的是什么？您又是如何地看待它未来的发展呢？
【Nenad】：WTL was born while I was working on ATL (Active Template Library). We were extending ATL to support ActiveX controls, and I was working on the windowing support. I started thinking that the same techniques can be applied to much broader windowing support, for the much richer UI for controls, components, and also applications. So, WTL was created as a part of ATL that would extend ATL to support any kind of UI related component or application. It did not ship with ATL in Visual Studio, however, so I decided to ship it as a standalone library that extends ATL.
I think that WTL will continue to be a great option for developers writing Windows applications and components. I don't see big changes or additions to WTL, because one of the design principles for WTL was to follow the Win32 UI API and design. It will continue to do so.
【Nenad】：WTL是我在从事ATL （Active Template Library）开发工作时的产物。那时我们正在扩展ATL，使之得以支持ActiveX control，而我负责的就是其中对于窗口机制部分的支持。这时，我就开始想，是不是可以把同样的技术应用到更为广泛的窗口机制中，以获得更丰富的UI 控制、组件、以至于应用程序呢？于是，作为ATL的一部分，WTL被开发出来了。它将ATL进行了扩展，以使得它可以支持各种类型的与UI相关的组件或者 应用程序。然而，它并没有随着ATL一同集成在Visual Studio中被发布，于是我就决定将它作为一个单独的ATL扩展库发布出去。
我认为WTL将一直是那些在Windows下开发应用程序以及组件的开发者的一个很好的选择。我并不认为在以后，我们会对WTL有一个大的改动（或者增添），因为WTL的一个设计宗旨就是“遵循Win32 UI的API及其设计”。现在如此，将来还是会如此下去。
【C++ View】：I first heard about WTL in July, 2000. At that time, I thought: "No official support, no documentation, no commercial hype, it will die in 6 months." Now, fifteen months passed, it spreads wider and be more vigorous. Lots of C++ programmers, esp. the ones we regard them as "gurus and masters" involved in WTL. I know it's surely because WTL is a wonderful library, but it must be more than a wonderful library to gain such attentions without official force.What do you think WTL's relative success? What's the reason?
【C++ View】：我第一次接触WTL是在2000年7月。在那时，我就想：“没有官方的支持，没有文档，也没有商业吹捧，它最多只能够存活6个月。”但现在 15个月过去了，它反而流传得更为广泛，更加的生机勃勃。许多C++程序员，尤其是一些我们所认知的“专家”以及“大师”，都在使用WTL。我当然知道这 主要是因为WTL的出色，但我想，能够在没有官方的力量牵涉的情况下吸引如此多的注意，WTL一定还有更出色的东西，请问您是如何看待WTL的成功呢？它 成功的原因又是什么？
【Nenad】： I think that the main reason of WTL's success is that it did fit the need of developers at the right time. More and more developers started using ATL, and it was natural for them to start using WTL when they needed more UI support. It seems that WTL was perceived as a more open project than others, judging by the support provided by other parties in the development community. Many people did a wonderful job of creating samples, documentation and support for WTL. The support from the programming community is very important part of the acceptance and success of WTL.
【Nenad】：我认为 WTL成功的最主要原因就是，它确实而且及时地满足了开发者的需求。越来越多的开发人员开始使用ATL，当他们需要更多的UI支持时，他们很自然的就会开 始使用WTL。 从其他的开发团队所提供支持来看，WTL看起来似乎要比其他的项目更加开放。许许多多人为WTL做了大量工作，如：创建示例代码，撰写文档等。WTL之所 以能够被广为接受并获得如此大的成功，来自于这些开发团队的支持绝对是一个重要的因素。
【C++ View】：What do you think about MFC? Do you like it? If you don't, why? And the most confusing thing is Managed C++, is it C++? Do the leaders of MC++ really think some C++ users will go to learn it? Do you believe?
【C++ View】：请问您对于MFC是怎么看的？您喜欢它吗？如果不，为什么呢？还有，最让人迷惑不解的就是Managed C++了，它是不是C++呢？MC++的提倡者是不是真的认为会有一些C++的用户转而去学习它呢？您的看法又是如何呢？
【Nenad】： I think that MFC is a great framework library. Don't forget that MFC was designed at the time that C++ compiler was rather limited, and the main platform was 16-bit Windows. Unfortunately, because MFC was designed as a framework, it was really hard to evolve it to use better C++ support in newer compilers, and to add support for new features added to Windows in the meantime. What I don't like about MFC is the DLL approach, which causes many compatibility problems, and framework design, which dictates too many things about app design.
Managed C++ is an extension to C++ which allows C++ programs to use managed code. It is very important to understand that you can compile your existing C++ code using MC++ without any changes. MC++ allows developers to use both familiar non-managed C++ and managed code in the same module. That provides an excellent way to extend existing code to interact with managed code, as well to create new projects that can use both managed and traditional C++.
【Nenad】：我认为MFC是一个了不起的框架库。请不要忘了， 在MFC被设计出来初期，那时的C++编译器还具有很多的限制，并且那时主要的平台还只是16位的Windows。不幸的是，由于MFC被设计成为一个框 架，使得我们很难利用新编译器中那些更好的C++特性来改进它，也很难将Windows中的很多新特性添加到MFC中。我不喜欢MFC的地方是它高度依赖 DLL的特性——因为它将导致许多兼容性方面的问题；还有就是MFC的整个框架设计——它在应用程序的设计中限定了太多东西。
Managed C++是C++的一个扩展，它允许C++程序得以使用受管（managed）代码。我们需要了解的一个很重要的特性就是，我们可以使用MC++来编译已有 的C++代码而无需对它们进行任何改动。MC++允许开发者同时使用他们所熟悉的非受管代码以及受管代码来开发同一个模块。这就提供了一个非常好的途径， 使已有的代码与新的受管代码相互作用，并也可使得我们创建一个项目，同时使用受管的和传统的C++代码。
【C++ View】：In the past 15 years or more, C and C++ is the base of almost all Microsoft's technologies(OS, COM, etc.). We C++ user paid a lot of hard work to catch them, because we felt what we paid was worthy(?). Now, it seems the climate changed. .NET is coming, the world is going to be full of CLRs and/or JVMs. There has been a decampment from C++. So what do you think about the future of C++ (not MC++) in Mircosoft technologies? Will it go away? Will it become a marginal language?
【C++ View】：在过去的15年中（甚至更长的一段时间内），C以及C++构成了几乎所有Microsoft技术的基础（如：OS，COM等）。我们这些 C++用户花费了大量的时间来熟悉并掌握它们（C以及C++），因为我们相信我们所付出的一定会有回报（?）。但现在的风向好像有了很大的改变。.NET 出现了，世界似乎就要充斥CLR （Common Language Runtime，公共语言运行库）以及／或JVM （Java Virtual Machine，Java虚拟机）。现在C++已经出现了退潮的迹象。那么，请问您对于C++（不是MC++）在Microsoft技术中的前景如何看 待？它是否会由此消亡？还是就此沦落为一门边缘语言？
【Nenad】：Well, the world is changing too. The new type of development for Web services and connected applications is on the horizon. I think that new languages, like Java, C#, and VB.NET, were developed to address two main issues - to simplify software development and to provide better support for Internet development. Simplifying software development allows more developers to write good applications and cuts down on time needed to finish a project. Supporting Internet development is obviously very important in this time when Internet is used more and more in every part of everyday life.
I think that C++ will continue to be an important language, especially for ISV's and for system development. On the other hand, I believe that .NET will be very important platform soon. .NET has the potential to be the main programming platform for the future, but it is reasonable to expect that the transition will take some time.
【Nenad】： 是的，世界也已经发生了变化。对于网络服务以及连接这样的新型应用程序的开发已经浮上了水面。我认为那些新的编程语言（如Java，C#，以及 VB.NET）都是针对以下两个主要的问题而开发出来的——简化软件的开发过程以及对于Internet应用程序开发提供更好的的支持。简化软件的开发过 程使得更多的开发者可以写出更多更好的应用程序并减少完成开发项目所需要的时间。而支持Internet的开发，对于这个Internet越来越深入到我 们的日常生活中的时代来说，毫无疑问是一件非常重要的事情。
我认为C++会继续作为一门重要的编程语言发挥作用，尤其是对那些独立软件开 发商和那些系统级开发来说更是如此。从另一方面来说，我相信.NET将会在不久以后成为另外一个非常重要的开发平台。对于未来来说，.NET拥有成为主流 编程平台的潜力，但我们必须认识到，这样的过渡阶段肯定要持续一段时间。
【C++ View】：There a lots of beginners in our readers, after they learn (standard) C++, they want to seek a path to master enought Microsoft technologies to be practical and proficient programmers. Could you recommend such a path? Should they learn Win32 API programming? Is it worthy of studying MFC? Is WTL/ATL/STL a reliable solution? Or goto C# directly? Many many people will thank you if you give them frank advice.
【C++ View】：我们的读者中有很多是初学者，在他们学习完（标准）C++后，他们希望能够找到一条道路，掌握到足够多的Microsoft的技术使自己成为 经验丰富的、熟练的程序员。您能不能给我们指出这样的一条道路来呢？我们是不是应该学习Win32 API编程？学习MFC是否是值得的？WTL/ATL/STL算得上是一个可靠的解决方案吗？又或是我们应该直接学习C#？如果您能够给我们一些建议，相 信会有很多的人为此而感激您的。
【Nenad】：I think that depends on their plans and ambitions. The more of those things you do, the better you are off in the long run. But, you also have to balance that with the practical issues. So, I think that people who see their future in the Internet development can go directly to C# or VB.NET, and study .NET platform. Those who would like to have more knowledge of the Windows platform and services it provides should certainly learn more about Win32 API and libraries that support Windows programming.
【Nenad】：我认为这主要取决于他们的计 划以及雄心。你所做的越多，在长时间竞争中你就越占据优势。不过你也要注意保持与实际问题的平衡。我建议那些决心以后只做Internet相关开发的人可 以直接去学习C#或者VB.NET，同时学习.NET平台。而那些更多地了解Windows平台以及它所提供的服务方面知识的人，当然就必须需要更多地了 解有关Win32 API以及那些支持Windows编程的库相关的知识。
【C++ View】：Soon after I began to learn WTL, a warm-hearted man posted me a email. He wrote: "You won't be a good WTL programmer if not a good ATL programmer, you won't be a good ATL programmer if not a COM programmer. And once you decide to learn COM, you are beginning your travel to hell." Is COM so difficult to learn? How to study WTL? We must learn API, COM, ATL and WTL in sequence, do we? And what about COM, will it remain to be the core technology of Microsoft, or just be substituted by .NET and dismiss?
【C++ View】：在我刚开始学习WTL后不久，有一位热心人给我发了份邮件。他写道：“如果你不是一个好的ATL程序员的话，你就不可能成为一个好的WTL程 序员；如果你不会COM编程的话，你就不可能成为一个好的ATL程序员；但一旦你决定开始学习COM，你就迈出了踏向地狱的第一步。”COM是不是真的那 么难学？我们应该如何地来学习WTL呢？我们是不是应该按照这样的顺序学下来呢，API->COM->ATL->WTL？还有，COM 将会变得如何？他是不是还能够保持Microsoft的核心技术这一头衔，抑或是被.NET给替换掉然后就此消失？
【Nenad】：I don't think it is necessary to master COM to use and understand WTL. Win32 UI knowledge is more important than COM to understand WTL. But it is true that knowledge of ATL is required, and ATL mainly supports COM. So, COM knowledge is desirable, but not required.
I don't think that COM is hell, but it sure does require a lot to learn to be an expert. Keep in mind that many people don't have to be COM experts to use COM, or to use WTL. Just understanding basic principles of COM is enough to use it, and then people can learn more when needed.
【Nenad】： 我不认为使用和理解WTL就一定要掌握COM。相比于COM来说，Win32 UI的知识对于理解WTL显得更为重要。但毫无疑问的是，ATL的相关知识是必不可少的。由于ATL主要任务就是支持COM，所以，有COM的知识只是会 更好一些而已，但它们并不是必需的。
我也不认为COM是一个噩梦，但毫无疑问的是，想要成为一个COM专家，要学的东西实在是太多了。但 请记住一件事情，很多使用COM或者WTL的人并不都是COM方面的专家。要想使用它们，人们所需了解的只是一些COM的基本原理就够了，其他的相关的知 识则可以在需要时再去学习。
【C++ View】：What do you think about Generic Programming? Is it a whole different paradigm from OOP, or just OOP's supplemental facility? Can we combine GP and OOP? In the hard work of design and implement WTL, you must had got an insight about the relationship between OOP and GP, what's it?
【C++ View】：请问您对于泛型程序设计是如何看待的？它到底是OOP的一个补充呢，还是完全不同于OOP的另外一个程序设计范型呢？我们是否可以将GP以及 OOP一同联合使用？我想，在设计和实作出WTL的艰苦过程中，对于OOP以及GP之间的关系，您一定有了自己的看法，您能不能给我们说一下呢？
【Nenad】：Generic Programming and OOP are very different, mostly because Generic Programming doesn't explicitly express relationships between design elements. They can, however, be used together very efficiently.
WTL uses a combination of Generic Programming and OOP design. Templates are mostly used to implement traditional OOP classes. I'd like to point out that WTL doesn't use any "pure" design, and it doesn't strictly follow any design guidelines or styles. I do think, though, that WTL does use one of the main strengths of the C++ language - it uses appropriate paradigm that is the most suitable for a particular problem.
【Nenad】：GP和OOP非常不同，这主要是由于GP从不显式地表达出设计元素之间的关联来。然而，它们也可以被非常高效地组合运用。
WTL 中使用了一种GP连同OOP的设计。我在其中大量使用了模板来实作出传统的OOP中的类。我很乐意指出的是，WTL中并没有使用一种“纯”设计，它也没有 遵循任何的设计指导方针或者设计规格。可是，我还是认为WTL使用到了C++语言中的最主要的精髓处——对于一个特定的问题使用一种最适合它的适当典范。
【C++ View】：Recently, the famous C++ pioneer Stanley Lippman joined Microsoft and became a member of Visual C++.NET group. How do you think about this? What message do you think your company like to pass to public? Does this mean Microsoft want to make VC.NET a full-standardized C++ compiler and hold C++ as your core system language?
【C++ View】：最近，著名的C++元老级大师Stanley Lippman加入了Microsoft并成为其VC.NET开发小组中的一员。请问您对于此事是如何看待的？您认为Microsoft试图向公众传播一 种什么样的信息呢？这是否也意味着Microsoft希望VC.NET成为一个完全标准化的C++编译器，并继续保持C++的核心系统语言地位呢？
【Nenad】：I think that shows that Microsoft is committed to advance the C++ compiler and language, and ready to get the best people to help. I am sure that VC++.NET will continue to be powerful tool for developing applications, and that it will also include additional capabilities for the .NET development. Compliance with the C++ Standard is an ongoing work, and we will see further improvements there, too.
【Nenad】：我认 为这显示了Microsoft对于促进C++编译器以及语言继续发展的决心，并为此找到了最佳人选来获取帮助。我确信VC.NET将会继续是开发应用程序 的强有力工具，并且它同时还将包含有.NET开发能力。目前我们正在进行兼容C++标准方面的工作，不久我们就会看到成效。
【C++ View】：I'm learning WTL and ATL, since you are the author of WTL and a member of ATL group, can you give me some advice?
【C++ View】：我现在正在学习WTL以及ATL，既然您是WTL的作者，同时又是ATL开发小组中的一员，您能不能给我一些建议呢？
【Nenad】：There are several areas of programming that are very important for WTL and ATL: knowledge of the C++ language in general, understanding of templates, COM for ATL, and Windows UI programming for WTL. Solid knowledge in these areas is very beneficial for WTL and ATL developers, and it also helps to understand the source code for both libraries.
I would also like to encourage everybody to write programs. That is the best way to learn how to use any library, or a programming language or operating system. Writing programs often brings problems that must be solved that are not addressed in books. Reading about something is very useful to start learning, writing programs is the best next step.
【Nenad】： 对于WTL和ATL来说，有好几个编程方面的领域是十分重要的：大体上的C++语言知识，了解模板，COM（对ATL而言），以及Windows UI编程（对WTL而言）。在这些领域有着坚实的基础对于WTL以及ATL开发人员来说有着很大的好处，同时对于理解这两个的源代码也能够起到帮助作用。
我同样也很乐意去鼓励大家多写程序。这也是学习如何使用一个程序库，或者一门编程语言，或者一个操作系统的一个最好的方法。在写程序的过程中经常会出现一些书本上没有提及但又必须被解决的问题。在开始学习时读一些东西是很有用的，而写程序则是向纵深发展的最佳方式。
【C++ View】：They say we are in the gate of Post-PC times, it will be a embedded world, and there will be embedded smart device everywhere, and the embedded industry will build a far large market compare to PC's. Do you believe it? Do you think WTL and other C++ template libraries are available and appropriate for embedded development? Are there available for Internet development?
【C++ View】：有人说，我们现在已经处于后PC时代的门口，未来将会是一个嵌入系统的世界，嵌入式的智能设备将会无所不在，并且对比PC来说，嵌入系统的产 业将会是一个更大的市场。您是否相信这些呢？您是否认为WTL以及其他的一些C++模板库对于嵌入式开发也适用呢？它们是否适合Internet开发？
【Nenad】：Yes, I think that large number of various devices that we use everyday will become small, specialized computers. That doesn't mean that the number and importance of PCs will go down, just that there are many other devices that will be enhanced to be programmable and connected. Those new devices will provide a great opportunity for software developers, because they will all have software and somebody has to write it.
Many of the C++ libraries are quite appropriate for embedded development, and WTL would also be in cases where Windows based user interface is important (for example, Pocket PC platform). Great flexibility and small footprint are always very important features for embedded development, so template libraries are in the very good position there.
【Nenad】： 是的，我认为我们现今所使用的各种设备中的大部分在以后都将会演变成为一些小的，具有专门用途的计算机。但这并不意味着PC的数目以及重要性将会由此降 低，只不过是表明还有着许多其他的设备需要被加强以使得我们可以对其进行编程并且连接。由于必须需要有软件的支持，而软件又需要有人来写，这些新的设备将 会给软件开发人员带来极大的机遇。
有许多的C++函数库都可用于嵌入系统的开发，WTL也将会在那些Windows用户界面较为重要的开 发中（例如，在Pocket PC平台上面开发）占有一席之地。对于嵌入式开发来说，良好的弹性，微小的内存耗用永远都会是很重要的特性，而模板库在这方面占据了一个非常好的地位。
【C++ View】：In the past 7 years or more, COM is Microsoft's core technology. And we now can see that in the next decade, the core role may be .NET. My question is, what's wrong with COM? Where will COM be? Will it disappear? Will it be substituted by something else? What's the relationship between COM and .NET? Is .NET based on COM? Is it worthy of learning COM now?
【C++ View】：在过去的7年（甚至更长的一段时间）内，COM都是Microsoft中的核心技术。现在我们可以预见到，在下一个十年间，这个核心将会变 为.NET。我的问题就是，COM有什么过错？COM将何去何从？它是否会逐渐消失呢，还是会被其他的一些技术给替代？COM和.NET之间的关系是什么 样的情况？.NET是否是基于COM之上呢？现在学习COM是不是还值得？
【Nenad】：Maybe you shouldn't ask what is wrong with COM, but just think of .NET as the evolution of COM. .NET extends what was started with COM- creating reusable binary components - and brings additional important features: rich metadata, great run-time, built-in security, versioning, etc. All of these new features are important for development today, and it is really great that .NET has extensive support for them. Interoperability between .NET and COM is also provided, so that the previously developed COM components can still be used in the .NET environment.
I still think that it is a good idea to learn COM - it is a great first step even for people who want to learn .NET, and it also provides better understanding of the design and implementation of .NET itself.
【Nenad】： 或许你不应该问COM有什么过错，而是应该把.NET看成COM的进化。.NET扩展了COM最初的目的——创建可重用的二进制程序组件——并向其中添加 了很多重要的特性：丰富的元数据，了不起的运行库，内建的安全机制，版本机制等。对于现今的软件开发来说，所有的这些新的特性都非常重要，所以.NET能 够广泛地支持它们，是一件很伟大的产品。Microsoft同时也提供了在.NET和COM之间进行互操作的能力，这使得以前所开发出来的COM组件 在.NET环境中同样也能够得到使用。
我仍然认为学习COM是一个很好的主意——它甚至对于那些希望学习.NET的人们来说也是一个很好的开端，学习COM同时也有助于我们更深入地理解 .NET本身的设计和实现。
【C++ View】：I know you must be a C++ fan. Now the language is facing lots of challenges. To counterattack, Dr. Stroustrup suggest to develop many useful libraries, and teach the programmers to use C++ as a high level language. Now there are several wonderful modern C++ libraries. Aside of ATL, WTL and STL, there are still Boost library, MTL, ACE/TAO, DTL, etc. It seems the C++ community is preparing a movement. Do you think the movement will success? Why? What are your colleagues'(in Microsoft VC.NET group) attitude towards such a movement?
【C++ View】：我猜想您肯定是一个C++爱好者。现在这门语言面对着许多的挑战。作为反击措施，Stroustrup博士提议开发许多有用的库，并引导 C++程序员把C++当作一门高级语言来使用。现在我们已经可以得到好几个极好的现代的C++库，除去ATL、WTL以及STL之外，还有Boost库、 MTL、ACE/TAO、DTL等。一切都显示着C++社区正在酝酿着一次变革。请问您觉得这场变革能否成功？为什么？您的那些Microsoft中的 VC.NET开发小组中的同事对于此态度是怎样的？
【Nenad】：C++ is a great language and its importance remains high, even with the new challenges. Libraries are an excellent addition to the language itself, as they provide very useful reusable code for developers. The existence of many great C++ libraries shows the size and strength of the C++ community. I think that is already a success, and that it will continue. You can be sure that the VC++.NET group is aware of the existing libraries, and I expect them to continue to enhance the support for them.
【Nenad】：C++是一门伟大的语言，即便遇 到了新的挑战，它仍然将是非常重要的。程序库对于语言本身是极好的补充，它们为开发者提供了一些十分有用的可重用代码。存在如此众多的、了不起C++程序 库，这件事情本身就表明了C++社区的庞大和强大。我认为这场变革已经成功了，并且会一直成功下去。你们可以放心，VC.NET开发组是不会对这些已有的 程序库熟视无睹的，我预期他们会不断地加强对于这些库的支持。
【C++ View】：The last question. Since lots of people don’t acquaint themselves with WTL, now we have a chance for you, the father of WTL, to introduce WTL in a short speech here. What would you like to speak?
【C++ View】：最后一个问题。既然许多人并不了解WTL，作为WTL之父，您现在有机会在这里做一个演讲，请简短地介绍一下WTL。
【Nenad】：WTL is a template based library for user interface development. It extends ATL to provide classes for implementing user interface for applications, components, and controls. It provides classes for various user interface elements: top-level windows, MDI, standard and common controls, common dialogs, property sheets and pages, GDI objects, UI updating, scrollable windows, splitter windows, command bars, etc.
WTL is implemented using the same template architecture as ATL, so it is a natural fit for ATL developers. It also doesn't alter or hide Windows specific constructs, thus allowing Windows programmers to use WTL without surprises. The important design goal of WTL was to avoid inter-dependencies - classes themselves do not reference other WTL classes. That means that your program will contain just the code that you actually use, and nothing else. Coupled with the use of templates, this allows creation of very small programs without run-time dependencies.
WTL delivers the object oriented way to program for the Windows user interface, while keeping the code size small. It also provides a great foundation that developers can extend with their own classes.
And finally - WTL was written with a hope that developers will enjoy using it. I hope you will use it and enjoy it, too.
WTL 是一个基于模板的、专为开发用户界面的程序库。它扩展了ATL，并提供了一些类用来实现应用程序的用户界面、组件和控件。它提供了各种类来支持各种各样的 用户界面元素：顶级窗口、MDI、标准控件和通用控件、通用的对话框、属性表以及属性页、GDI对象、UI更新、可卷动的窗口、分割窗口、命令条等等……
WTL 的实现使用了和ATL一样的模板架构，所以对于ATL开发者显得很自然。同时它并没有改变或者是隐藏那些Windows相关结构，那些Windows程序 员在使用WTL时也不会感到很吃惊。WTL的一个主要设计原则就是避免在没有引用到其他WTL类时，出现不必要的内部依赖。这意味着我们的程序将只包含有 我们实际上所使用的代码，除此之外再无其他的东西。加上了模板的使用后，这样做得到的结果就是一些非常小的，不依赖于运行库的程序。
WTL专注于用面向对象的方法来编写Windows的用户界面程序，同时保持代码的尺寸很小。同时，它也为开发者提供了一个很好的基础，可以写新的类来扩展WTL。
最后，我在编写WTL时就希望开发者能够喜欢在开发中使用它。我同样也希望您能够使用它并喜欢上它。
正文完
WTL疑点分析
1.配置WLT环境后，打开smaple中的例子 调试的的时候发现有编译错误：
用VS2005新建一个WTL dialog工程，建好后直接变异会出现下面这2个错误，是什么原因，如何解决？
CVTRES : fatal error CVT1100: duplicate resource. type:MANIFEST, name:1, language:0x0409
LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt
解决办法：找到工程对应的rc文件,将
CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST
这句注视掉即可.
CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST
这个语句有2个地方，一个是
BEGIN
"CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST ""res\\\\WTLClock2.exe.manifest""\r\n"
"\0"
END
另外一个地方是：
CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST "res\\WTLClock2.exe.manifest"
我注释掉第二句就可以了，
但是其实我还不是很明白意思
我只是知道这么做可以通过
而且我自己新建的工程不会有这个问题，我用的是 WTL8+Vista，拿别人的Sample Code会出现这个问题
具体可以参考http://www.polsnet.com/home/html/tech171_189899.html
2.MSG_WM_TIMER(OnTimer) 编译报错：e:\program files\wtl80\wtlproject\wtl sample from mike\wtl4mfc2_demo\wtlclock\wtlclockview.h(26) : error C2660: 'CWTLClockView::OnTimer' : function does not take 1 arguments
void OnTimer ( UINT uTimerID/*, TIMERPROC pTimerProc*/ )屏蔽掉第2个参数就可以了估计版本不一样吧。高版本的为1个参数了。
http://flipcode.spaces.live.com/blog/cns!8e578e7901a88369!932.entry
http://www.cnblogs.com/cxun/archive/2007/07/10/731470.html
2.关于WTL插入对话框资源后如何新建类的问题
自己通过添加C++类然后，
class CUrlDlg :
public CStdDialogResizeImpl<CUrlDlg>,
public CWinDataExchange<CUrlDlg>
{
public:
///CUrlDlg(void);
//~CUrlDlg(void);
enum { IDD = IDD_URL };
BEGIN_MSG_MAP(CUrlDlg)
CHAIN_MSG_MAP(CStdDialogResizeImpl<CUrlDlg>)
END_MSG_MAP()
};
像这样子。
编译后出现问题：
------ Build started: Project: MoibleIE, Configuration: Debug Windows Mobile 5.0 Pocket PC SDK (ARMV4I) ------
Compiling...
UrlDlg.cpp
E:\Program Files\WTL80\include\atlframe.h(3121) : error C2039: 'GetDlgResizeMap' : is not a member of 'CUrlDlg'
c:\documents and settings\administrator.microsof-4e75bb\桌面\moibleie\moibleie\UrlDlg.h(9) : see declaration of 'CUrlDlg'
E:\Program Files\WTL80\include\atlframe.h(3028) : while compiling class template member function 'void WTL::CDialogResize<T>::DlgResize_Init(bool,bool,DWORD)'
with
[
T=CUrlDlg
]
E:\Program Files\WTL80\include\atlwince.h(669) : see reference to class template instantiation 'WTL::CDialogResize<T>' being compiled
with
[
T=CUrlDlg
]
E:\Program Files\WTL80\include\atlwince.h(704) : see reference to class template instantiation 'WTL::CStdDialogResizeImplBase<T,t_shidiFlags,t_bModal>' being compiled
with
[
T=CUrlDlg,
t_shidiFlags=13,
t_bModal=true
]
c:\documents and settings\administrator.microsof-4e75bb\桌面\moibleie\moibleie\UrlDlg.h(10) : see reference to class template instantiation 'WTL::CStdDialogResizeImpl<T>' being compiled
with
[
T=CUrlDlg
]
Build log was saved at "file://c:\Documents and Settings\Administrator.MICROSOF-4E75BB\桌面\MoibleIE\MoibleIE\Windows Mobile 5.0 Pocket PC SDK (ARMV4I)\Debug\BuildLog.htm"
MoibleIE - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
经过分析发现加上下面的映射宏
BEGIN_DLGRESIZE_MAP(CUrlDlg)
END_DLGRESIZE_MAP()
发现问题就解决了,编译成功了。
然后这个时候我们跑到对话框上去看一下 用鼠标点右键发现可以添加变量了 这个时候说明我们的类建立成功了。
那为什么我们自己手动的建立的类能够跟我们的对话框对应起来了。
其中enum { IDD = IDD_URL };才是真正的罪魁祸首，IDD_URL这里是你插入的对话框的ID，通过这个就可以对应起来。
也许你不信这样一些就可以了吗？不过的确是这样。不信的话，你可以把这个enum注释掉，然后再去重新rebuild下，发现虽然没有错误
但是，跑到对话框上去的时候发现不能添加变量。所以敢肯定这个的确是这么回事！
然后我们可以通过
FSDoModal（窗口对象）这样就可以打开我们所创建的窗口了。
然后这个时候我们需要对窗口进行初始化。比如我们可以插入菜单之类的东东。
头文件：
BEGIN_MSG_MAP(CUrlDlg)
MESSAGE_HANDLER(WM_INITDIALOG,OnInitDialog)
CHAIN_MSG_MAP(CStdDialogResizeImpl<CUrlDlg>)
END_MSG_MAP()
LRESULT OnInitDialog(UINT uMsg, WPARAM wParam, LPARAM lParam, BOOL& bHandled);
实现文件：
然后我们需要完LRESULT成OnInitDialog()的编写.
LRESULT CUrlDlg::OnInitDialog(UINT uMsg, WPARAM wParam, LPARAM lParam, BOOL& bHandled)
{ //这里可以添加自己想添加的初始化代码
return bHandled = FALSE;
}
这里有点体会：关于复制别人的菜单问题。比如copy menu到自己的资源的时候发现压根儿不能paste，最好只好自己直接插入菜单，命个一样ID的名字，然后在把别人的菜单最上面那个menucopy过 来paste上去发现整个都贴上上去了，今天才发现的。偷懒的做法。
然后初始化部分插入菜单：
CreateMenuBar(IDM_EDIT);
这个时候运行下发现出错误了：Line:172 ::SHCreateMenuBar(&mbi)!=0 这样的Debug Assertion Failed。
进一步分析：我们需要在.rc2文件里面加入
IDM_EDIT SHMENUBAR DISCARDABLE
BEGIN
IDM_EDIT, 2,
I_IMAGENONE, ID_MENU_OK, TBSTATE_ENABLED, TBSTYLE_AUTOSIZE, ID_MENU_OK, 0, NOMENU,
I_IMAGENONE, ID_MENU, TBSTATE_ENABLED, TBSTYLE_DROPDOWN | TBSTYLE_AUTOSIZE, ID_MENU, 0, 0,
END
这个就可以成功插入我们的菜单了 ok，继续吧。IDM_EDIT 我们自己的菜单ID。
3.WTL中可以通过宏进行设置edit控件自动调节大小。
BEGIN_DLGRESIZE_MAP(CUrlDlg)
DLGRESIZE_CONTROL(IDC_EDIT_URL, DLSZ_SIZE_X | DLSZ_SIZE_Y)
END_DLGRESIZE_MAP()
其中。IDC_EDIT_URL 是编辑控件的ID
其中DLSZ_SIZE_X 表示以右对齐的意思。同理DLSZ_SIZE_Y以底部对齐
这个编辑控件位于我们刚刚插入的对话框上面。无论我们怎么样在编辑的时候弄成什么样子，该控件都会根据窗口大小而自动调整。
不过，有点要注意的是，你的控件Y或X位置的不能太靠近对话框的边缘，否则会出现被覆盖的问题。至少要保留默认距离。
4.WTL关于IDR_MAINFRAME菜单的修改
如果该菜单需要分版本的话,比如SP 或PPC菜单需要设置成不一样
我们也可以采用预编译的方式来做
ATL_IDW_MENU_BAR SHMENUBAR
BEGIN
#ifdef WIN32_PLATFORM_PSPC
IDM_MAINFRAME_PPC,//以前系统这里是IDR_MAINFRAME 其实这个与类里面那个IDR_MAINFRAME没有什么关系，这里本身就//只是一个系统菜单而已。
#else
IDM_MAINFRAME_SP,
#endif
2,
I_IMAGENONE, ID_ACTION, TBSTATE_ENABLED, TBSTYLE_AUTOSIZE, ID_ACTION, 0, NOMENU,
I_IMAGENONE, ID_MENU, TBSTATE_ENABLED, TBSTYLE_DROPDOWN | TBSTYLE_AUTOSIZE, ID_MENU, 0, 0,
END
其中我们这需要在PPC sdk进行设置：Resouces->General ->Preprocessor Definitions ->WIN32_PLATFORM_PSPC(添加该宏,其中这里的宏可以是自己随便定义的我们这里顺便就直接使用系统自己的宏了),这样就可以选 择性的加入菜单。IDR_MAINFRAME了其他地方不需要做任何修改。
4.调试WTL中的MTPadCE,出现link错误：MTPad.obj : error LNK2019: unresolved external symbol GetOpenFileNameEx referenced in function "public: int __cdecl WTL::CFileDialogImpl<class WTL::CFileDialog>::DoModal(struct HWND__ *)" (?DoModal@?$CFileDialogImpl@VCFileDialog@WTL@@@WTL@@QAAHPAUHWND__@@@Z)
解决方法是在头文件中加入 comment(lib,"aygshell.lib")便可以解决了。
5.编译GuidGenCE 的时候出现的错误：E:\Program Files\WTL80\include/atlres.h(15) : error RC2188: e:\Program Files\WTL80\Samples\GuidGen\Pocket PC 2003 (ARMV4)\Debug\RCa02380(197) : fatal error RC1116: RC terminating after preprocessor errors
解决方法是：编辑.rc文件 用#include "atlresce.h" 替换#include "atlres.h"就可以了。
6.运行WTL8.0里面的ImageView的时候,出现问题：
ATLASSERT(!"Floating point (%%e, %%E, %%f, %%g, and %%G) is not supported by the WTL::CString class.");
解决方法：在头文件中加入 #define _ATL_USE_CSTRING_FLOAT就好了。
转之
