Introduction to WTL - Part 1

I want to implement a dialog box that contains a list box. Does anyone have sample WTL code that shows how to use CListBox?

look this template that you can use to implement Any standard control that you want Wink | ;)

, also you can take a look on the first lines of Atlctrls.h.

CDDXControl<ccombobox> m_Combo;
CDDXControl<clistbox> m_ListBox;

template <class tcontroltype="">
class CDDXControl :public CWindowImpl<cddxcontrol,tcontroltype>
{...}

// Dialog.h: interface for the CDialog class.
//
//////////////////////////////////////////////////////////////////////

#if !defined(AFX_DIALOG_H__BA6F9366_51A8_40EE_8B49_02EFF9943BBB__INCLUDED_)
#define AFX_DIALOG_H__BA6F9366_51A8_40EE_8B49_02EFF9943BBB__INCLUDED_

#if _MSC_VER > 1000
#pragma once
#endif // _MSC_VER > 1000
#include "Atlctrls.h"
#include "AtlDdx.h"
#include "AtlMisc.h"
#include "resource.h"

template <class tcontroltype="">
class CDDXControl :public CWindowImpl<cddxcontrol,tcontroltype>
{
public:
BEGIN_MSG_MAP(CDDXControl)
// put your message handler entries here
END_MSG_MAP()
};

class CDialog : public CAxDialogImpl<cdialog>,
public CWinDataExchange<cdialog>

{
public:
enum { IDD = IDD_DIALOG1};
CDDXControl<ccombobox> m_Combo;

BEGIN_MSG_MAP(CDialog)
MESSAGE_HANDLER(WM_INITDIALOG, OnInitDialog)
MESSAGE_HANDLER(WM_CLOSE, OnClose)
COMMAND_HANDLER(IDOK, BN_CLICKED, OnOK)
COMMAND_HANDLER(IDCANCEL, BN_CLICKED, OnCancel)
END_MSG_MAP()

BEGIN_DDX_MAP( CDialog )
DDX_CONTROL(IDC_COMBO1, m_Combo)
END_DDX_MAP()

LRESULT OnInitDialog(UINT uMsg, WPARAM wParam, LPARAM lParam, BOOL& bHandled)
{
DoDataExchange();
return 1; // Let the system set the focus
}

CDialog();
virtual ~CDialog();

LRESULT OnClose(UINT uMsg, WPARAM wParam, LPARAM lParam, BOOL& bHandled)
{
// TODO : Add Code for message handler. Call DefWindowProc if necessary.
EndDialog(0);
return 0;
}
LRESULT OnOK(WORD wNotifyCode, WORD wID, HWND hWndCtl, BOOL& bHandled)
{
// TODO : Add Code for control notification handler.
m_Combo.AddString("Otraaaaa");
return 0;
}

LRESULT OnCancel(WORD wNotifyCode, WORD wID, HWND hWndCtl, BOOL& bHandled)
{
// TODO : Add Code for control notification handler.
char buff[1024]="";
m_Combo.GetLBText( m_Combo.GetCurSel(), buff );
MessageBox( buff );
return 0;
}

};

#endif // !defined(AFX_DIALOG_H__BA6F9366_51A8_40EE_8B49_02EFF9943BBB__INCLUDED_) Big Grin | :-D

Damn html code!!!

template <class TControlType>
class CDDXControl :public CWindowImpl<cddxcontrol,tcontroltype>
{
public:
BEGIN_MSG_MAP(CDDXControl)
// put your message handler entries here
END_MSG_MAP()
};

CDDXControl<CComboBox> m_Combo; Big Grin | :-D

It seems that many people are able to download WTL from the Microsoft Platform SDK except for myself.
I keep getting an error message.

Does anyone have a tip on how to get WTL

Hi
As I am connected to Internet via somethink like 20kb modem, the
official fancy installer of Platform SDK is very unfriendly for me.
Because of that I perfectly understand those who are asking
questions like ascet even when they know that it is in Platform SDK.

Unfortunately, the WTL is probably not available separately (it
would be something like 162KB zip file).

Fortunately, it is possible to download a single cabinet file
(approximately 800KB) to install WTL (only the .h files).

Firstly, get the following cabinet file (you can just copy
the following line to the Internet Explorer, or you can use some
ftp client to do that):

ftp://ftp.microsoft.com/developr/PlatformSDK/Oct2000/psdk-common.48.cab

The size of the cabinet for Oct2000 is 893058 bytes.

Then create, let's say, WTLextract.bat file and copy the following
lines into it:

----------------------------------------------------------------
mkdir WTL
extract /L WTL psdk-common.48.cab Atl*.*

cd WTL
rename AtlApp_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlApp.h
rename AtlCrack_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCrack.h
rename AtlCtrls_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCtrls.h
rename AtlCtrlw_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCtrlw.h
rename AtlCtrlx_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCtrlx.h
rename AtlDdx_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlDdx.h
rename AtlDlgs_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlDlgs.h
rename AtlFrame_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlFrame.h
rename AtlGdi_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlGdi.h
rename AtlMisc_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlMisc.h
rename AtlPrint_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlPrint.h
rename AtlRes_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlRes.h
rename AtlScrl_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlScrl.h
rename AtlSplit_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlSplit.h
rename AtlUser_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlUser.h
----------------------------------------------------------------

Then run this batch in the directory where the cabinet file
is stored. The WTL subdirectory is created and filled with the
files. Copy the content to your "WTL/Include" subdirectory.

Notice: the previous version of WTL was placed in the cabinet
file of the same name. It is likely that the next version
will be inside of the cabinet with the same name.

Warning: AtlGdi.h still contains a bug in the
CDCT<>::GetTabbedTextExtent(). See the message
with subject "WTL 3.1: bug in AtlGdi.h (repost from 6 Oct)"

Enjoy,
Petr

P.S. The psdk-common.48.cab apparently contains also WTL examples.
If anybody knows more details on which files should be extracted, where
they should be placed, or whether other cabinets contains parts of WTL,
please post some hints.

--
Petr Prikryl, SKIL s.r.o.

Thanks for your great solution. After trying several times to run the Windows Installer, I did it your way and finally I have WTL 3.1 Big Grin | :-D

Hi,

Just found out where the other files are:

ReadMe_Txt.1BACAA38_9B60_4B39_9854_B7F2382B1334
contains the Readme.txt for WTL 3.1,

and if you download
psdk-x86.48.cab
from the same site, it contains the app wizard atlapp60.awx

bye
Michael

(Thanks, Michael, for new information.)

Here is updated version of the WTLextract.bat
batch file for instalation of WTL from two plain cab
files. New version of the batch extracts also examples
and ATL/WTL wizard. If you have any suggestion, share it!

Enjoy,
Petr Wink | ;)

file WTLextract.bat
-------------------------------------------------------------------
echo off
cls
set psdk=Oct2000
set scommon=893058
set swizard=39162
set log=extract.log

echo WTL instalation
echo ---------------
rem Petr Prikryl (prikrylp@skil.cz), March 2001

if exist psdk-common.48.cab goto OKcommon
echo Firstly, copy this batch to some working directory.
echo Get the following cabinet file (you can just copy the following line
echo to the Internet Explorer, or you can use some ftp client to do that):
echo .
echo . ftp://ftp.microsoft.com/developr/PlatformSDK/%psdk%/psdk-common.48.cab
echo .
echo The size of the cabinet for %psdk% is %scommon% bytes.
echo If you want to install also the WTL wizard, download also
echo .
echo . ftp://ftp.microsoft.com/developr/PlatformSDK/%psdk%/psdk-x86.48.cab
echo .
echo The size of the cabinet for %psdk% is %swizard% bytes.
echo Place the cabinet(s) to the same directory where this batch is and
echo run the batch again. It creates ./WTL subdirectory with extracted files.
goto END

:OKcommon
echo Extracting headers and readme...

if exist %log% del %log%

extract /L WTL/Include psdk-common.48.cab *.A1000D79* >>%log%
extract /L WTL psdk-common.48.cab *.1BACAA38* >>%log%

cd WTL\Include
rename AtlApp_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlApp.h
rename AtlCrack_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCrack.h
rename AtlCtrls_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCtrls.h
rename AtlCtrlw_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCtrlw.h
rename AtlCtrlx_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlCtrlx.h
rename AtlDdx_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlDdx.h
rename AtlDlgs_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlDlgs.h
rename AtlFrame_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlFrame.h
rename AtlGdi_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlGdi.h
rename AtlMisc_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlMisc.h
rename AtlPrint_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlPrint.h
rename AtlRes_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlRes.h
rename AtlScrl_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlScrl.h
rename AtlSplit_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlSplit.h
rename AtlUser_h.A1000D79_C485_4CB3_8AB0_B6D38ED2B38C AtlUser.h

cd ..
rename ReadMe_Txt.1BACAA38_9B60_4B39_9854_B7F2382B1334 ReadMe.txt

cd ..

:EXexamples
rem Extract examples from the same cabinet.
echo Extracting the GuidGen example...

extract /L WTL/Examples/GuidGen psdk-common.48.cab *.755E56A7* >>%log%
extract /L WTL/Examples/GuidGen/Res psdk-common.48.cab *.59DE9FFA* >>%log%

cd WTL\Examples\GuidGen

rename AboutDlg_h.755E56A7_E652_46B4_A6D7_0CCF315D2624 AboutDlg.h
rename GuidGen_Cpp.755E56A7_E652_46B4_A6D7_0CCF315D2624 GuidGen.Cpp
rename GuidGen_Dsp.755E56A7_E652_46B4_A6D7_0CCF315D2624 GuidGen.Dsp
rename GuidGen_Dsw.755E56A7_E652_46B4_A6D7_0CCF315D2624 GuidGen.Dsw
rename GuidGen_Rc.755E56A7_E652_46B4_A6D7_0CCF315D2624 GuidGen.Rc
rename MainDlg_h.755E56A7_E652_46B4_A6D7_0CCF315D2624 MainDlg.h
rename Resource_h.755E56A7_E652_46B4_A6D7_0CCF315D2624 Resource.h
rename StdAtl_Cpp.755E56A7_E652_46B4_A6D7_0CCF315D2624 StdAtl.Cpp
rename StdAtl_h.755E56A7_E652_46B4_A6D7_0CCF315D2624 StdAtl.h

cd Res

rename GuidGen_Ico.59DE9FFA_8157_4709_B094_5F2969E49B32 GuidGen.Ico

cd ..\..\..\..

echo Extracting the MdiDocVw example...
extract /L WTL/Examples/MdiDocVw psdk-common.48.cab *.53855E45* >>%log%
extract /L WTL/Examples/MdiDocVw/Res psdk-common.48.cab *.D0BD03AE* >>%log%

cd WTL\Examples\MdiDocVw

rename Hello_Ico.53855E45_E9A1_4D6D_A016_C86B55004781 Hello.Ico
rename MainFrm_h.53855E45_E9A1_4D6D_A016_C86B55004781 MainFrm.h
rename MDI_Cpp.53855E45_E9A1_4D6D_A016_C86B55004781 MDI.Cpp
rename MDI_Dsp.53855E45_E9A1_4D6D_A016_C86B55004781 MDI.Dsp
rename MDI_Dsw.53855E45_E9A1_4D6D_A016_C86B55004781 MDI.Dsw
rename MDI_Ico.53855E45_E9A1_4D6D_A016_C86B55004781 MDI.Ico
rename MDI_Rc.53855E45_E9A1_4D6D_A016_C86B55004781 MDI.Rc
rename Resource_h.53855E45_E9A1_4D6D_A016_C86B55004781 Resource.h
rename StdAfx_Cpp.53855E45_E9A1_4D6D_A016_C86B55004781 StdAfx.Cpp
rename StdAfx_h.53855E45_E9A1_4D6D_A016_C86B55004781 StdAfx.h

cd Res

rename HelloDoc_Ico.D0BD03AE_627D_487E_8F51_77F78E270524 HelloDoc.Ico
rename Idr_Boun_Ico.D0BD03AE_627D_487E_8F51_77F78E270524 Idr_Boun.Ico
rename MDI_Ico.D0BD03AE_627D_487E_8F51_77F78E270524 MDI.Ico
rename MDI_Rc2.D0BD03AE_627D_487E_8F51_77F78E270524 MDI.Rc2
rename Toolbar_Bmp.D0BD03AE_627D_487E_8F51_77F78E270524 Toolbar.Bmp

cd ..\..\..\..

echo Extracting the MTPad example...
extract /L WTL/Examples/MTPad psdk-common.48.cab *.DF8CBE9B* >>%log%
extract /L WTL/Examples/MTPad/Res psdk-common.48.cab *.07DB2F17* >>%log%

cd WTL\Examples\MTPad

rename AboutDlg_h.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 AboutDlg.h
rename MainFrm_h.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 MainFrm.h
rename MTPad_Cpp.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 MTPad.Cpp
rename MTPad_Dsp.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 MTPad.Dsp
rename MTPad_Dsw.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 MTPad.Dsw
rename MTPad_h.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 MTPad.h
rename MTPad_Rc.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 MTPad.Rc
rename Resource_h.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 Resource.h
rename StdAtl_Cpp.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 StdAtl.Cpp
rename StdAtl_h.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 StdAtl.h
rename View_h.DF8CBE9B_82F3_4DCB_AC8E_F6DEA2C503F3 View.h

cd Res

rename MTPadDoc_Ico.07DB2F17_27FF_442C_98E1_6D2B292E9F49 MTPadDoc.Ico
rename MTPad_Ico.07DB2F17_27FF_442C_98E1_6D2B292E9F49 MTPad.Ico
rename printpre_bmp.07DB2F17_27FF_442C_98E1_6D2B292E9F49 printpre.bmp
rename Toolbar_Bmp.07DB2F17_27FF_442C_98E1_6D2B292E9F49 Toolbar.Bmp

cd ..\..\..\..

:EXwizard
rem Extract wizard if the cabinet was downloaded

if exist psdk-x86.48.cab goto OKwizard
echo
echo WTL wizard cannot be extracted -- cabinet file not present.
echo To extract WTL wizard get the cabinet file:
echo .
echo . ftp://ftp.microsoft.com/developr/PlatformSDK/%psdk%/psdk-x86.48.cab
echo .
echo The size of the cabinet for %psdk% is %swizard% bytes.
echo Place the cabinet to the same directory where this batch is and
echo run this batch again.
echo .
goto END

:OKwizard
echo Extracting WTL wizard...
extract /L WTL/AppWiz psdk-x86.48.cab /E >>%log%

cd WTL\AppWiz

rename AtlApp60_Awx.5500ABCF_72E4_45D7_BE1E_CF3394B98733 AtlApp60.Awx

cd ..\..

:END
echo
pause
set psdk=
set scommon=
set swizard=
-------------------------------------------------------------------
(end of file)

--
Petr Prikryl, SKIL s.r.o.

All this fuss about WTL just make me furious another time.
Well the code is pretty brilliant (as usual) with those cute hungarian notation conventions to make the code more readable and huge use of comment to balance the lack of documentation but, seriously, do we really need it? Do we need to always rely on "mom" Microsoft to make our job a little bit easier? Really, my impression is that we are loyal dogs just waiting for bones from time to time. MFC was not good for COM? It doesn't matter we did not use COM at all. Simply we did not need it!!! Now, there is ATL and COM is the present and the future! We must use it everywhere! And the library is so nice and efficient and then MFC is so heavy! We surely are not going to use it anymore! But one moment! Where is support for all those always readjusted common controls and common dialogs I was used to use? And document/view architecture? It was so brilliant! And CString!!! I cannot live without CString! So it comes WTL as a lifebelt really for those who were lost along the way asking "What should I do to remain in fashion and still work?". I think is really time for Windows programmers to show they are not eunuchs. I think we can really write a framework better than WTL instead of those gradient filled menus which are SOOOOO CUTE and skill probing but useless at all! We have a lot to learn from Linux programmers and from KDE developers in particular which are so organized and really doing something great. They have Konqueror but we have sidebar-gradient-filled menus! How skilled we are! In years we were not able to write an OLE control container on our own or some libraries to manage widely used image formats. It's a shame! Simply they are alive, we are quite DEAD

poor c++ programmers? -

typedef std::basic_string<tchar> CString;

i like an easy life & i like wtl

can you really get that to compile? <shakes head=""> I don't think so.

class CString : public std::basic_string<tchar> {
...
};

you both make valid points.

um okay, let that be

class CString : public std::basic_string<tchar> {
...

nevermind!!! arggghh

// StringsOfLife.cpp
//
// the point i was trying to make is that you don't
// have to use additional libraries to enjoy an
// easy life !!
// :-

#include <tchar.h>
#include <string>
#include <iostream>

typedef std::basic_string<tchar> CString;

int main(int argc, TCHAR* argv[])
{
CString strVal("Look no non-standard libraries!");

std::cout << strVal;

return 0;
}

Seems to me you should go get hang out with the Linux programmers and other raw-meat eaters. You opbviously have nothing to contribute here.

You surely can't contribute everywhere...

Your pretty funny. Why attack to promote innovation... although really it seems more like an attack on window's programmers vs linux.

Heh.. I agree that we could use some more creativity in Windows, but why slam an article
pointing out something useful to get it?

Some of us have to work in the real world, and when the guy driving the paycheck says to
use atl, then information like this is useful.. wtl is a nice lightweight alternative to
mfc. A little change won't hurt.. and really, I think a lot of people are using
std::string anyway.. kinda hard not too if your already using the rest of the library.

These holy wars between linux and windows are funny. Windows programmers I think are
rarely religious about the platform. . . most of that is in defense and rebuttal to some
troll attempting to trash the evil empire.

Whatever.. I like Linux. But I'm paid to program in windows. And a library like WTL and ATL currently make my job easier so I have more time to work on things I like, like
games and linux.

If people really think there is no pre-made code on Linux or FreeBSD or something, they are really wrong. Never heard of G++, QT, or things like that?

Wink | ;)

LPCSTR Dutch = "Double Dutch Smile | :)

"

Why do you go here for such topics, try industry-strong linux news (if they exists?)

1 => template it's really useful&powerful: since C++ is avalaible it's the only (important) change in ISO (iso96) it ocurs for stream now C# stream are usefull for inet (thanks) and it's better than php + perl + jsp. second consider STL, FTL, VTL, MTL boosts, leda thanks

2 => com is really amizing in any part and with dcom is egal to corba. don't you neither like corba or rpc ?

3 => what have you really done with linux so great for industry where integration remains a pity and where java is SOOOOOOOOOO slow (i believe licence of cache page is at least same cost than ms complete suite, am i wrong?)

4=> gradientcome froms with gtk (not kde sorry) before windows it isn't a tip1

5=> for history you're wrong the deadlock is that bedore NT3.51 things are like DOS
After egal to unix. the problem is not enhancement is to always deal with dde or GDI16
so C# is really a promess

we host 7000 post on our DB and never stop it with NT+SQL server, consider also this.
PHP+XML+COM+PERL+C++ +awk+yacc+ada+java2+uml+ado+atl+js+flash+XHTML programmer's thinking
ciao Rose | [Rose]

but bad point to cl bugs Cry | :((

Sigh...Yet another programming Primadonna. Look, if you wanna wave your linux distro around like it was a nine foot pleasuring device, go over to the *BSD forums and see if they care--because I don't. I only care about getting the answers I need, and to be honest I could care less about which platform is better than the other because frankly, I (unlike SOME OTHER PEOPLE) just don't have that much time on my hands. No matter what tool you use the question must always be two things: 1) Can this get the job done by meeting my requirements, and 2) How much time will it take me to implement it. Thats it. That's the bottom line. The client doesn't care whether I use MFC/ATL/WTL or KDE, they just ask me this very simple question: Can this get the job done for me?

Its a simple yes or no question that requires a damn good yes or no answer.

So go play with yourself and your distro. Go ahead. But while your there still contemplating as to why windowing system (insert whatever you want here) is better then windows, I'll be making money while you continue to work your job flipping burgers.

I'll see you at the drive thru. And don't forget my fries next time.

You are missing the whole point. A complete WTL Doc/View app compiled is as small as 30K. You can't write an MFC app for less that 973K( MFC42.dll ) unless you statically link and even then you can't get under 300K. That's 10 times bigger.

if( SmallFastAndFunctional )
{
library = WTL;
}
else if (BigBloatedAndOutdated )
{
library = MFC;
}

Does that make it a little clearer?

There is an old adage about keeping your mouth shut and letting people think you a fool rather than opening your mouth and proving it.

I like this analysis! It's refreshing to know that some dogs don't want the bones tossed now and then! What a great analogy. Anyway, although WTL may be the latest fine fashion (and justifiably appreciated by many), I find it rather obnoxious that it comes with no support. It's like Redmond threw out a worm again, instead of a bone, to see how many fish (not dogs this time) would bite before they would consider supporting their own work. Yuck.

Sleepy | :zzz:

Bill Dickinson

Wouldn't it be easier when you can download just the headerfiles and the examples instead of installing WTL with the Platform SDK ? Or is this not allowed by Microsoft

Thank you for providing good one

I sent an email to microsoft saying they should continue
support for WTL after reading your comment. I include the
text at the end of the message. I urge all you to send
email to managers@microsoft.com to urge them to
continue support for WTL. I have been writing ATL based
controls for about 3 years and I dont use MFC and I
dont like it all that much. So I developed some classes
similiar to WTL, a couple of years ago. If I would have
had the WTL my job would have been alot easier.

here is the text of my email:

I just read an article on www.codeproject.com, about WTL a template library for
interface controls. I was not aware that it existed. I have been developing controls
for quite a while using ATL and had to develop my own library that is functionally
equivalent to ATL, so I was excited to find out about WTL. Then I read the
comments on WTL, one of them was:

I just read this from a comment made to the article:

Here is an exerpt from an interview with Tony Goodhew, Microsoft's Visual C++ 7 Technical Product Manager, and Bill Dunlap, Microsoft's Visual Studio 7 Lead Product Manager by O'Reilly Windows Programming editor John Osborn:

[i]'WTL is code that was released unsupported and we have no intention of updating it. We have no intention of continuing its availability. Frankly, it should never have been released and it will be removed from the platform SDK at the time of the next SDK revision.'[/i]

Read the full interview at http://windows.oreilly.com/news/visualc_0500.html

How foolish of them to spend time and money on something, get people to start using it, and then just dump it! I wonder why they made this decision.

Alvaro

I think it is extremely shortsighted of Mr Goodhew to say that WTL will be dumped. MFC cannot last forever, and just to
let you know I avoid using it except in complex projects. The reason is very simple, size and distribution. If I develop a control
then I don't know if the correct version of MFC will be on the targer platform. You might say I could distribute it and then be
garaunteed that it would be there. But when most modems only deliver less than 56k, delivering a behemoth like the
MFC dlls is riduculous. So I would urge that you continue developement of WTL and put Mr Goodhew in charge
of waste removal. It might be a better fit.

File name	Description

atlapp.h	Message loop, interfaces, general app stuff
atlcrack.h	Message cracker macros atlctrls.h Standard and common control classes
atlctrlw.h	Command bar class atlctrlx.h Bitmap button, check list view, and other controls
atlddx.h	Data exchange for dialogs and windows
atldlgs.h	Common dialog classes, property sheet and page classes
atlframe.h	Frame window classes, MDI, update UI classes
atlgdi.h	DC classes, GDI object classes
atlmisc.h	ATL ports of `CPoint`, `CRect`, `CSize`, `CString`, etc.
atlprint.h	Printing and print preview
atlres.h	Standard resource Ids
atlscrl.h	Scrollable windows
atlsplit.h	Splitter windows
atluser.h	Menu class

Directory	Description

MTPad	Multithreaded notepad sample
MDIDocVw	ATL version of the MDI sample
GuidGen	ATL version of the GuidGen sample

File Name	Description

AtlApp60.Awx	ATL/WTL AppWizard

Introduction to WTL - Part 1

Brief history

Features

Where do you get it?

Method 1

Method 2

What’s in the box?

The Headers

The Samples

The App-Wizard

License

Comments and Discussions