🚀 go-pugleaf

I've been using both class libraries for a bit now, and find it hard to
rate one as clearly superior to another.

OWL
===
	-easy addition of callbacks via DDVTs -BCC only
	-nice high level classes for windows, dialog boxes
	-online help under BCW
	-a small manual
	-I don't know about other platforms as support in the UK is
	 a bit minimalist.
MFC
===
	-message maps are a bit tortuous (can compile under BCC)
	-some high level objects such as CWnd
	-lots of low level classes, especially for GDI
	-bigger manuals but they're better.
	-better debugging functions -VERIFY, Dump()
	-available now for winNT, win32s

I think OWL might be a good starting point for a new programmer on a
new program, although they'll end up learning most of the nitty gritty
windows stuff anyway. quite a lot of the MFC member functions are 
wrappers for windows api calls with the first HWND or HDC argument
inserted automatically. This makes it easier for an experienced 
programmer to migrate to the library.

One thing I do like about MFC is all the small classes for things like 
rectangles, regions, brushes, bitmaps and so on. With OWL you can have
a structured top down decomposition of all your windows callbacks, but
are then left reaching for volume #2 of the win SDK API reference when
you actually want to do anything in the callbacks. The low-level msoft
objects come in handy here, letting you create GDI objects then select 
them into DCs, add in a couple of regions to do your clipping and half
your work's done!

Even these are a bit limited- there's no support for DIBS, the brushes
and pens could easily be extended with a deselect function that selects
a stock object into the DC, saving all that business of remembering what
was there first. Still, I guess no-one is ever satisfied with someone
elses library.

Currently I only use OWL in the top level test harness of a DLL I'm doing.
I chose that one because I'm using BCC and the link to the online help saves
time reading manuals. For the main code I use neither library as this
would affect portability. Having realised how useful GDI classes would be
I just knocked up a set of my own which may not be complete yet but it
meets my needs. If anyone out there wants a copy of this then mail me
(allow 28 days for delivery)

	-Steve