Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!hplabs!hpl-opus!hpnmdla!joeb From: joeb@hpnmdla.hp.com (Joe Barnhart) Newsgroups: comp.os.os2.programmer Subject: Re: PM Tools & Training Message-ID: <11560002@hpnmdla.hp.com> Date: 6 Mar 91 18:43:28 GMT References: <17310@crdgw1.crd.ge.com> Organization: HP Network Measurements Div, Santa Rosa, CA Lines: 19 For what it's worth, I've found the best tools for PM development are the IBM Developer's Kit (not the MS one) and Smalltalk/V PM. I prefer the IBM developer's kit because it contains more information than the MS one, combining what MS calls the "Developer's Kit" and the "Device Driver Kit." Plus, it has the docs on OS/2 v. 1.3, which MS doesn't offer. Last, IBM is more religious about updating their kit and making that update available to developers at low cost. Smalltalk/V PM is a fantastic environment for "interactively" testing PM programs. You can sit at the keyboard and find out how each PM function works by invoking it and inspecting the results. This is better than Codeview 'cause you don't have to go through the edit/ compile/link phase every time you want to try something different. Smalltalk/V PM does NOT replace the need for an SDK, however. -- Joe B. #include