Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornell!travelers.mail.cornell.edu!news.kei.com!news.mathworks.com!newshost.marcam.com!zip.eecs.umich.edu!umn.edu!vm1.spcs.umn.edu!JCOLTEN
From: JCOLTEN@vm1.spcs.umn.edu (Jim Colten)
Subject: newbie question, MY classes in the hierarchy
Message-ID: <1734FCBC5S86.JCOLTEN@vm1.spcs.umn.edu>
Sender: news@news.cis.umn.edu (Usenet News Administration)
Nntp-Posting-Host: vm1.spcs.umn.edu
Organization: SPCS - University of Minnesota
Date: Fri, 24 Feb 1995 20:29:24 GMT
Lines: 20

 
This is a question about style and general practice in placing an application's
classes in the hierarchy.  (ST/V here).
 
It seems that very often, most or all of a project's domain classes are
subclasses of Object.  Is it reasonable to try to group these under a single
Abstract Class (prossibly containing no instance or class vars and no methods)
just for the convenience of keeping them together in the browser's class pane
and to be able to FileOut the whole package with one operation?
 
For Example:
 
Object
 AnApplication \
  AppClass1     \
  AppClass2      >  My application's domain classes (or most of them)
     .          /
     .         /
 AnimatedObject
 Behavior
