juan@rose.ACA.MCC.COM (John Reynolds) (04/03/91)
Thrilled that Microsoft had finally fixed Windows to the point where people would really use it, I ran out last May and bought the Micro- soft SDK. You can do anything you want to with it, but it is far from being a coherent development system. Hoping for better, I just bought Bourland C++, better than the SDK in some respects, but loaded with generic DOS libraries and tools (How do you use Profiler on a Windows app anyway?) The _focus_ of Bourland C++ is not Windows, you can access all of the Windows functions, but the documentation is primarilly for good old character mode programming with the Bourland BGI thrown in for laughs. Along with my Bourland C++ came bundled Glockenspeel's CommonView2, a really nice class library for user interface stuff. Without this library, I think that most people will be simply compiling their C Windows code with a C++ compiler. CommonView develops a hierarchical class library for the most common windows and controls. Unfortunately, it is designed to span Windows, the Mac, and Motif, so it doesn't directly support some of the Windows specific stuff (like combo-boxes). My problem now is how to best utilize this plethora of goodies. The strain on my hard disk is not a pretty sight. I am _only_ interested in Windows, so what parts of the Bourland C++ can I safely nuke? What parts of the Windows SDK should I keep? Is Turbo Profiler any use for Windows apps? If you have already gone through this, I'd appreciate hearing from you. I'd also like to hear from people who have used CommonView2 with Windows 3.0. Please reply via email, I'll summarize if anything of common interest emerges. John Reynolds juan@mcc.com