Path: utzoo!attcan!uunet!husc6!uwvax!dogie!terranova
From: terranova@vms.macc.wisc.edu
Newsgroups: comp.sys.mac.programmer
Subject: Design Philosophy
Message-ID: <434@dogie.edu>
Date: 4 Jul 88 23:44:58 GMT
Sender: news@dogie.edu
Organization: University of Wisconsin Academic Computing Center
Lines: 30

Greetings,
    A friend of mine recently expressed his disapproval of the standard
Macintosh program design.  Rather than putting windows, menus, icons,
def procs, strings, controls, etc. in resources he would prefer to
hard code everything into the program and make heavy use of #define
statements.  He would change the #defines instead of the resources.
"That's why they made the preprocessor."

    I am interested in other peoples thoughts on this.  Aside from
being able to modify parts of the program without recompilation, what
advantages are there to putting everything into resources?  What
disadvantages are there to having all code with no other resources?  What's
it like in the real world (outside a university)?  Are there any major
trends in this type of design philosophy?

    His method is simpler to get some code running.  In fact, I use
quite regularly for this purpose.  Then, once the code runs the way I want
it, I move data and def/filter procs into a resource and change NewControl()
to GetNewControl() (for example).

Comments, anyone?

------------------------+------------------------------------------------
John C. Terranova       |  I'd start a revolution, but I don't have time.
  CS, BS to be		|      --Billy Joel,  "Close to the Boarderline"
------------------------+------------------------------------------------
I speak for myself and all those listed below.  And no one else.
	1)
	2)
	3)