refresh second pass

Phillip Shelton shelton@usq.edu.au
Fri, 1 Dec 2000 16:15:10 +1000


> -----Original Message-----
> Here is a second pass at a refresh design and API. It's similar
> to the first, so I won't repost the intro or diagram. It has two
> major changes:
>
> 1. The CM API has been changed so that components specify which
>    entities they want to watch. Individual entities and whole
>    classes of entities may be watched. Watches are associated
>    with gui components, not with callbacks. This avoids having
>    tons of callbacks for each component.
>
>    Being able to register for classes of entities (i.e., you
>    watch all accounts) makes it easier to start simple and
>    then refine for efficiency later on.

That is for things like, I am looking at last months transactions and
someone else is, or in another window, this months transactions are being
entered. Does my window get updated if none of the transactions in my window
are affected?
sorry about the grammar.

Phill