SystemChangeNotification and Packages

Avi Bryant avi.bryant at gmail.com
Mon Feb 28 15:16:34 UTC 2005


On Sun, 27 Feb 2005 09:53:05 +0100, stéphane ducasse
<ducasse at iam.unibe.ch> wrote:
> Hi avi
> 
> While I agree on your analysis of our intuition with SCN, I disagree
> with your conclusion.
> My impression is that if you consider package as first class category,
> then package changes
> should be using SCN and seaside and connector should not.  Because soon
> we will want to have
> package changes, package list in changesorter.. I think that packages
> are about code entities and
> we designed SCN with that vision in mind (package, traits...) should
> use it else this will be the mess later.

Ok, fair enough.  So in answer to Alex's original question, it sounds
like probably we do want the first set of events he mentions:

> >> I was wondering what is the impact of adding packages on the system
> >> change notification mechanism. I added some events for creating a new
> >> package, renaming one, deleting move, moving one method from one
> >> packate to another, ...

But not the second set:

> >> What about adding a new repository to a package? What about saving a
> >> package?

Right?

Avi



More information about the Squeak-dev mailing list