Please tell me that Borland, and Microsoft and GUI developer interfaces
do not create any code for you when you build a GUI based application.
OK then, "Borland do not create any code for you when you build a GUI
based application."
OK, to be strictly accurate let's tighten that into, "Borland do not
_need_ to create any code for you when you build a GUI based
application, and they generally don't do it.."
I haven't written any C++ in years. I used to write Turbo Pascal (DOS
& Windows, but before Delphi), then I wrote VB, now I write Java. But
back in the day, the first real Borland Windows class library had a
minimal "Hello World" that was something like this:
function main ()
{
var app CWinApp;
app.init ();
app.print ('Hello World');
app.terminate ();
}
This gave you a one window program with some ugly static text on it.
There were no buttons, but the windows control buttons worked and it
would respond to a WM_CLOSE message. Anything else you needed, you
started subclassing things and over-riding the virtual methods that
were already hooked into the message handling loop.
The equivalent with VC++ was to knob around with a GUI wizard for a
bit, then press the button and have it spew out 20 pages of
unintelligible code.
Incidentally, my first Windows 3.0 programs were written under
extremely flakey early betas of TPW (Turbo Pascal) and pre-dated both
the OOP extensions to TP/DOS and any form of class library. I _have_
written enormous message handling loops in Notepad, because it's all
we had. It was horrible, and I'm not doing it again. But the solution
is to have a decent class library that's easy to use, not to build a
wizard that understands how to clean-slate the awkward stuff, but does
nothing to help maintenance.
