[Dev] Re: notifications about the collection itself

[John Anderson]

Hi Alec:

I'm a little surpised that you don't already get notified in this case. 
Unfortunately, I don't really understand what determines what 
notifications get sent, since I've been working on the code that uses 
notifications, not the code that generates them. I think we need Ted 
(who will be back on Monday) and Andi in the loop to really understand 
this. Also, I've noticed that there seem to be situations where I would 
have expected a notificaiton of an attribute changing when I don't see 
it -- or at least don't get any information about which attribute was 
involved. I'm going to need this information to eliminate unnecessary 
notifications.

John

Alec Flett wrote:

> John/Ted -
> So right now the way notifications work is if any items in a 
> collection get modified/etc, then a notification goes out to subscribers.
>
> In the case of color, I'm actually interested in getting notified when 
> the 'color' attribute on the collection itself, not a member of the 
> collection, is changed. I can change it via a menu right now, but the 
> calendar code doesn't know the color changed, so it doesn't know to 
> redraw.
>
> what would you guys think about making notifications fire for both the 
> collection items, as well as changes to the collection itself?
>
> Alec

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/dev/attachments/20050909/405dba74/attachment.html