Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!reed!bowman
From: bowman@reed.UUCP (Eric Bowman)
Newsgroups: comp.lang.c++
Subject: Need help with some class def's
Message-ID: <14646@reed.UUCP>
Date: 7 Apr 90 20:34:27 GMT
Organization: Reed College, Portland OR
Lines: 31

I'm currently teaching myself C++, and would greatly appreciate any responses
to my question:

I'm designing a Macintosh program in C++ to do various population biology
simulations.  I've been trying out different class heirarchies, and I can't
figure out the best way to work this out.

There are four different simulations, say A,B,C and D.  Each simulation has
two windows, a parameters window and a graphics window.  I'd like the user
to be able to maintain all four simulations on the screen at once, if
necessary.

I have an application class already, which handles a document class.  It
seems as though I really ought to have a simulation class, too, but I
can't figure out where to place it in the heirarchy:

1)  Should I derive a new TSimulation class from TDocument, and then from
    that derive two new classes, say TSimParams and TSimGraphics?

2)  Or, would it be better (easier?) to have maintain a document class and
    a simulation class, and have each document point to it's relevant 
    simulation.

I'm really struggling with the best way to link two windows together in this
way, and *any* suggestions/help/sample code (particularly for handling
multiple windows on any system) would be greatly appreciated.

Please email.
Thanks,
BoBo
bowman@reed.{bitnet,UUCP,edu}