🚀 go-pugleaf

Mark Framness (framness@EMIRATES.NET.AE) wrote:

: Hey Phreaks!

: What is a good book on using Visual Age C++ for OS/2?  The manuals and online
: help restrict their attentions to functionality only.  I mean they tell you
: how to use something but very little on why to use something.  An example of
: this is in the compile settings.  You click on help and it just says click on
: the desired option to activate or deactivate it.  It assumes you already know
: exactly what the setting does (good for veterans of the OS/2 Wars, but for
: rookies not good at all).

: I see for any sort of OS/2 PM/WPS project you should be working with make
: files, rc files, h files, lib files, hpp files (oh yeah and isn't there
: something called a cpp file?) etc.  I understand the concept of these files
: but can find little information that can help me understand how make files are
: created in VA C++.  Sure there is makemake but I look at the options and no
: comprendho.

Well, nmake is a reasonably standard if limited make.  But on the general
topic of OS2 and VAC books, check EDM's reviews.  I use the books from
the IBM Technical Library published by QUE (for 2.1), some of which are
reproduced in the VAC .inf files, and the books by Burge and Celi,
Advanced OS/2 Presentation Manager Programming (a good introduction),
Stern and Morrow, OS/2 Warp PM Programming for Power Programmers, and
Knight and Ryan, Programming the OS/2 Warp Version 3 GPI.
I've got various other books, but those are the ones I tend to use.

For the Open Class Library the best bet seems to be Tsuji, Love, Law
and Olson, Power GUI Programming with VAC++, and for multimedia,
Lawton, Noe, and Lopez, Developing Multimedia Applications under OS/2.
But I haven't used these last two much.


Will
cwr@crash.cts.com

Mark Framness wrote:
> 
> Hey Phreaks!
> 
> What is a good book on using Visual Age C++ for OS/2?  The manuals and online
> help restrict their attentions to functionality only.  I mean they tell you
> how to use something but very little on why to use something.  An example of
> this is in the compile settings.  You click on help and it just says click on
> the desired option to activate or deactivate it.  It assumes you already know
> exactly what the setting does (good for veterans of the OS/2 Wars, but for
> rookies not good at all).
> 
> I see for any sort of OS/2 PM/WPS project you should be working with make
> files, rc files, h files, lib files, hpp files (oh yeah and isn't there
> something called a cpp file?) etc.  I understand the concept of these files
> but can find little information that can help me understand how make files are
> created in VA C++.  Sure there is makemake but I look at the options and no
> comprendho.
> 
> I look at the hello world examples included with the package but I can find
> very little information about what they are doing.  An example of this is in
> the third version of the Hello World application.  They have the rc file with
> the strings and then the string references are macro defined to hex numbers in
> an h file.
> 
> #define STR_HELLO   0x1200  //Hello World string ID               V2
> #define STR_INFO    0x1220  //Inactive text string ID             V2
> #define STR_CENTER  0x1230  //Center alignment status string ID   V3
> #define STR_LEFT    0x1231  //Left alignment status string ID     V3
> #define STR_RIGHT   0x1232  //Right alignment status string ID    V3
> 
> Now what are the hex numbers?  I added another menu to this app and figured
> out that I had to define the references to the menu items in a similar fashion
> and all I did was to add 1 to the previous number.  When I made the file the
> menu I added came up nicely (though it had no functionality to it).
> 
> If I were to author an application from scratch how would I come up with the
> numbers?
> 
> e.g.
> #define STR_BOLD   0x4242    //whatever
> 
> Would the above be acceptable?  I just dreamt up the number from 42 the
> answer!  ;-)
> 
> Thanks
> 
> Take Care!
> 
> postmaster@[127.0.0.1]
> Spam booby trap!!!
> 
> FROM:  Mark Allen Framness
> HOME:  framness@.NO_SPAM.EMIRATES.NET.AE
> WORK:  m477@NO_SPAM.ugru.uaeu.ac.ae
> HTTP:  http://netnet.net/~farmer/index.html
> 
> URL for comp.lang.c NG:  http://www.eskimo.com/~scs/C-faq/top.html
> 
> To reply via e-mail, delete the given reply to address and delete the NO_SPAM
> from the above addresses.
>                                         &
> All standard disclaimers apply.  Anyone who says otherwise is itching for a
> fight.

An excellent text with real world examples and many "tricks of the
trade" is:

"Visual Age for C++" , Nilsson and Jakab, Prentice Hall 1996, ISBN
0-13-614322-9

Covers OS/2 and WinNT versions of VAC++.

Bruce Lontka
Senior Technical Fellow
Cerberus Pyrotronics

Will Rose schrieb:
> 
> Mark Framness (framness@EMIRATES.NET.AE) wrote:
> 
> : Hey Phreaks!
> 
> : What is a good book on using Visual Age C++ for OS/2?  
There is a.. well.. german book about VAC++ called Visual Age C++f�r
OS/2 (Tewi, author is Ilias Posukidis)

M