Last time I looked (latest release), it was working very nicely. There
was some unclear code, but Roel says it is scaffolding for future work.

The implementation plan you suggest seems right to me. It would require
a central listener in PI to parse the changes (#bla moved from category
'a' to '*a') and dispatch the notifications to the appropriate packages.
Then MC would listen to the specific packages, I guess.

I think you can use the latest mailed release, though it would be nicer
if Roel could please release something on SM. Note he might be changing
some class names relative to the latest release, not that's hard to fix
later.

Daniel

Avi Bryant <avi at beta4.com> wrote:
> 
> On Fri, 25 Jul 2003, Daniel Vainsencher wrote:
> 
> > It seems not to notice (no asterisk next to package name) when I -
> > * Change the class comment
> > * Recategorize a method
> >
> > Have you looked at Roels notifications to solve this?
> 
> Yes, I would very much like to use Roel's notifications for this; in the
> long run, I'd like to use them to maintain a cache for PackageInfo as
> well.
> 
> I suppose what's really wanted is something that translates his basic
> notifications into higher level, package-savvy ones, so that you could
> subscribe to a particular package's notification stream.
> 
> I haven't had a chance to look at his more recent releases, yet - is it in
> fairly good shape at this point?