Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!portc02.blue.aol.com!howland.erols.net!news.mathworks.com!uunet!in2.uu.net!165.254.2.53!nonexistent.com!not-for-mail
From: vlad@world2u.com (Vlastimil Adamovsky)
Subject: Re: How to add events to Collections?
X-Newsreader: Forte Free Agent 1.0.82
X-Nntp-Posting-User: (Unauthenticated)
Message-ID: <E2uCJ6.6yr@nonexistent.com>
References: <19961221224300.RAA04169@ladder01.news.aol.com> <32BD669A.59C1@acm.org>
X-Trace: 851301616/9015
X-Nntp-Posting-Host: i123.152.world2u.com
Date: Mon, 23 Dec 1996 00:41:46 GMT
Lines: 28

"Russell T. Vernick" <vernick@acm.org> wrote:

>Generally, a Collection is a subordinate object to an actual domain
>object.

That's why I think the domain object (or whatever we might call it) should
receive events from the Collection object.

>  I would think that the domain object could be made responsible
>for altering the collection, hence being able to signal any changes to it

Why not? If the fired event is application specific then it can be fired 
by  the domain object. 

> Additionally, the changes signaled would be in terms of the domain
>object, not the collection.

The changes in collection should be signaled by the collection, the changes or 
the fact that "something happened, is happening or will happen" would be better
signaled by the model.




 Vlastimil Adamovsky
 ** C++ and Smalltalk consultant **
 * http://www.stepweb.com *

