[comp.windows.ms.programmer] Windows 3.0 Developer's Guidebook

ebergman@isis.cs.du.edu (Eric Bergman-Terrell) (04/14/91)

I called the Microsoft main 1-800 number (which I don't have at the moment)
asking about the document describing how Windows applications should work
and look.

The document is called something like "Windows Developer's Guidebook".
It's free - so BC++ 2.0 users like me may want to get hold of it...


Terrell

drift@qut.edu.au (Glenn Wallace) (04/14/91)

In article <1991Apr13.235057.2871@mnemosyne.cs.du.edu>, ebergman@isis.cs.du.edu (Eric Bergman-Terrell) writes:
> 
> I called the Microsoft main 1-800 number (which I don't have at the moment)
> asking about the document describing how Windows applications should work
> and look.
> 
> The document is called something like "Windows Developer's Guidebook".
> It's free - so BC++ 2.0 users like me may want to get hold of it...

Is that a finished version produced by their User Interface Task Force?

We have a pre-release one of those but it had ridiculous things like 
Help NOT on the right hand side. I hope they fixed _that_.

+-------------------+-----------------------------------------+
| Glenn Wallace     | Net: drift@qut.edu.au                   |
| Drift Project     | Fone: +61 7 837-7126 Fax: +61 7 221-0173|
| Telecom Australia | Snail: 11th Flr 144 Edward St.,         |
+-------------------+        Brisbane, Q4000 Australia        |
|                                                             |
| Disclaimer - The opinions expressed must be my own, because |
|              Telecom is a statuatory authority and as such, |
|              is not capable of having opinions.             |
+-------------------------------------------------------------+

ebergman@isis.cs.du.edu (Eric Bergman-Terrell) (04/14/91)

Don't know if it's pre-release or finished or what.  However they're out of
stock (they still take orders, but it may be a long wait for it).

Terrell

ronb@burklabs (Ron Burk ) (04/16/91)

ebergman@isis.cs.du.edu (Eric Bergman-Terrell) writes:

 ... /* some stuff about a "Windows 3.0 Developer's Guide" */ ...

I called (800) 426-9400 and they didn't seem to know about any such
thing, unless you are just referring to one of the manuals that you can
buy with or without the SDK.  Can you post the precise name and/or
part number of what you are talking about?

keithp@nwnexus.WA.COM (Keith Pleas) (04/17/91)

In article <Doqg11w163w@burklabs> ronb@burklabs (Ron Burk       ) writes:
>ebergman@isis.cs.du.edu (Eric Bergman-Terrell) writes:
>
> ... /* some stuff about a "Windows 3.0 Developer's Guide" */ ...
>
>I called (800) 426-9400 and they didn't seem to know about any such
>thing, unless you are just referring to one of the manuals that you can
>buy with or without the SDK.  Can you post the precise name and/or
>part number of what you are talking about?

I found this book at Tower last night.  It's called "Windows 3: A Developer's
Guide" by Jeffrey M. Richter, and is published by M&T Books (800)533-4372.
List price is $39.95, ISBN is 1-55851-164-4; includes 3 source code disks.
It is written for "experienced" Windows programmers, with these chapters:
     1. Anatomy of a Window
     2. Subclassing and Superclassing Windows
     3. Dialog-Box Techniques
     4. Designing custom Child Controls
     5. Setting Up Printers
     6. Tasks, Queues, and Hooks
     7. MDI Application Techniques
     8. Installing Commercial Applications
     A. The NOWINDOWS.H File
     B. Windows Bitmaps
     C. Accessing Class and Window Extra Bytes

ebergman@isis.cs.du.edu (Eric Bergman-Terrell) (04/17/91)

Don't have the part # for the "Windows Developer's Guidebook" or whatever
it's called.  It's not one of the 3 big books that come with the SDK -
more of a short booklet I suppose.  I'll post the part # when I get it
unless one of the SDK users posts it first...

Terrell

ebergman@isis.cs.du.edu (Eric Bergman-Terrell) (04/17/91)

The book you mention has a similar title but is a different book.  The 
booklet I mentioned is simply a short tretise on how to make Windows
programs behave and appear (i.e. look-and-feel)...

Terrell

bchin@umd5.umd.edu (Bill Chin) (04/17/91)

In article <1991Apr13.235057.2871@mnemosyne.cs.du.edu> ebergman@isis.cs.du.edu (Eric Bergman-Terrell) writes:
>I called the Microsoft main 1-800 number (which I don't have at the moment)
>asking about the document describing how Windows applications should work
>and look.
>The document is called something like "Windows Developer's Guidebook".
>Terrell

We tried calling MS's main number, but they didn't seem to know anything
about it.  Could you post a part number or something more definite?
Thanks a bunch.
--
Bill Chin			internet:bchin@umd5.umd.edu
PC/IP, Computer Science Center	NeXTmail:bchin@is-next.umd.edu
University of Maryland,		CompuServe:74130,2714
College Park			*Standard Disclaimers Apply*

fredf@microsoft.UUCP (Fred FREELAND) (04/18/91)

In article <1991Apr17.135504.28228@mnemosyne.cs.du.edu> ebergman@isis.UUCP (Eric Bergman-Terrell) writes:
>
>The book you mention has a similar title but is a different book.  The 
>booklet I mentioned is simply a short tretise on how to make Windows
>programs behave and appear (i.e. look-and-feel)...
>
>Terrell

There is a book included with the Microsoft Windows 3.0 SDK that explains a
standardized way of creating Windows applications.  The name of the book is
"Common User Access Advanced Interface Design Guide". It's not from Microsoft,
but from IBM. It describes their Systems Application Architecture.  The IBM
number on this book is SC26-4582-0.

The title that you mention may have been included in earlier (pre-Win 3.0)
versions of the SDK but I suspect that the IBM SAA book now replaces it.

Hope this helps.


-- 
Frederick F. Freeland Jr.                        "Of all the things I've lost,  Microsoft Corporation                               I miss my mind the most!"   One Microsoft Way  
Redmond, WA 98052 (206) 882-8080                                                                                                                                internet: fredf@microsoft.beaver.washington.EDU                                 arpanet:  fredf%microsoft@uw-beaver.ARPA
uucp:     uunet!microsoft!fredf                                                                                                                                 Opinions expressed over this signature are my OWN and not those of my employer!