Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!cs.tcd.ie!tcdmath!gwills
From: gwills@maths.tcd.ie (Graham Wills)
Newsgroups: comp.sys.mac.programmer
Subject: Re: File management
Message-ID: <128@maths.tcd.ie>
Date: 10 Nov 88 10:24:40 GMT
References: <6337@csli.STANFORD.EDU>
Reply-To: gwills@maths.tcd.ie (Graham Wills)
Organization: Maths Dept., Trinity College, Dublin
Lines: 31

I am working on a statistical graphics package featuring new styles of
dynamic interaction. I write in MacApp/MPW, but have also written a BIG
program in pure MPW (final debugging & marketing it now). I use Pascal only
so far, but some 68000 is bound to creep in soon...

Here is a rough tree for the MPW program

			   MAIN

                       EVENT_HANDLER

    MOUSEDOWNS   WINDOW_HANDLER  MENU_HANDLER  FILER  HELP_HANDLER

    ( extra )    FOR_WIND DRAWER  ( extra )    
    ( files )                     ( files )

The extra files are totally application specific. There are about 6 of them,
each between 20-40K. Also all global variables go into a seperate file, and
I have a MESSAGES ( for general info giving ) CURSOR and some others all
the units use.

These 'just grew'. I tried to put everything that was logically connected into
the one UNIT (Rule: 1 unit 1 file of same name), but if it got too big - if
compile times were too slow - I split it. hence I have several mousedown
blockbusters - including MOUSEDOWNINGRAPH AND OPTMDOWNINGRAPH - each 30K

The one thing I was carefull about was that if I wanted to work on one part
of the program, such as a new menu item, an about window, whatever, I did
not need to use more than one or two units.

Hope that helps - if you want more detail, such as exact sizes etc- Mail me.