Robert,

I've been using a previous version of your code for awhile now, and have
found it invaluable. I've found it especially useful for UI debugging, as it
seems the only sane way to try to figure out where the mouse clicks and
motions are *really* going in the multi-layered morphic world.

Thanks,

Jim


> A while ago I started to work on AspectS, an environment to explore
> aspect-oriented programming (AOP) in dynamic systems like Squeak
> (http://www.prakinf.tu-ilmenau.de/~hirsch/Projects/Squeak/AspectS/).
>
> AspectS can also be used to implement roles/perspectives. One of the
> differences between mixins/MI and aspects is that instead of letting
> a set of classes decide from where to inherit additional behavior,
> the aspect is responsible for adjusting existing behavior in or
> distributing additional behavior to target objects. It is just the
> other way around. Aspect instances in AspectS are regular objects
> that can change the behavior of objects in the image (all instances
> of a class or just specific ones) and revert the effects they caused
> anytime needed.
>
> I've updated a paper that describes AspectS in more detail:
>
http://www.prakinf.tu-ilmenau.de/~hirsch/Projects/Squeak/AspectS/Docs/Aspect
S_20020222.pdf
>
> At http://www.prakinf.tu-ilmenau.de/~hirsch/Projects/Squeak/AspectS/
> there are a change set and a pre-loaded image that might better explain
> what I've tried to describe in the paper...
>
> Best,
> -Robert
>