Hello Jerry.
07 Apr 97 12:09, Jerry Coffin wrote to David Torrez:
 JC> Personally, I wore straight hair and blue jeans, even when an afro and
 JC> a leisure suit was "the future."  I may not have been the height
 JC> of fashion, but nobody laughs when they look at old pictures of me
 JC> either.
:-D
 JC> Chase "RAD" that's fashionable this month, and whatever becomes
Let's not forget what RAD means: Rapid Application Development. Why is it, 
that a RAD tool absolutely have to wrap the code into a beefed up drag'n drop 
userinterface? Everybody knows that, the most time, in a programming project 
is spend with some problems concerning, usually, very few lines of code, that 
just /wont/ behave. It is not the userinterface design, that eats your time.
For me MFC was the natural RAD tool, not in spite of, but because, it is a 
relatively thin wrapper around the API code. Almost everything I know from 
API programming I can use in MFC. Often the MFC wrappers use the same syntax 
as the API equivalent, and if not: I just call the function I know.
Most people starts with programming to the Windows API, because it is 
important to know what is behind the fancy OOP libraries. It is not often you 
want to use a callback in MFC, but when you need it - you REALLY need it!
Christian
--- GoldED 2.50 UNREG
---------------