[Adium-devl] Status event wackiness

[Colin Barrett]

I was thinking about why I never ran into this problem before.

I realized in every other situation, I was a listObject observer. I  
didn't use that protocol in this situation because I'm not observing  
changes for all listObjects. I think I might want to use it, now, and  
just filter those against a list of all the contacts  
([observedContacts appendArray:[chat participatingListObjects]]) I'm  
observing. That sends out notifications on the AIListContact level,  
right?

I agree, this is a rather special case, and we definitely don't want  
a string of notifications if say, you sign on all at once with all 10  
of the accounts I have in your meta. That would be a mess. Think of  
the Growl pop ups! Yeesch.

-Colin

On Jun 8, 2006, at 9:21 AM, Evan Schoenberg wrote:

> Well, you're using the AIContentStatus's sending in order to log  
> the event... I'm pretty sure that's not the right level of  
> granularity.  That's a content object, posted for display to a  
> message view in response to a particular status notification... but  
> part of the fun of XML is recording things in a lossless way. We  
> don't want to record the message "Evan went away" or "Evan is not  
> idle" -- what we want to log, as I see it anyways, is the fact that  
> AIM.tekjew had a status event of CONTACT_STATUS_AWAY_YES or  
> CONTACT_STATUS_IDLE_YES. No?  I think our "internal notification  
> system sucks" because you're not using the right part of it.
>
> That said, the current system is perhaps not quite geared for what  
> you want in that it automagically consolidates status changes to  
> make sense at a metacontact level. CONTACT_STATUS_AWAY_YES is not  
> going to be posted if you have me on AIM and MSN, I'm already away  
> on MSN, and I go away on AIM.  Everything about the notification  
> system... at present anyways... says that's redundant information  
> -- no growl notification, no sound, etc.  In the general case, I  
> think this is what should be... because generally people on with  
> multiple services or names go away or idle on all of them at once,  
> and we wouldn't want to display a string of notifications all  
> related to the metacontact Colin, each of which was referring to a  
> different name/service. Thoughts?
>
> -Evan
>
> On Jun 8, 2006, at 12:21 AM, Colin Barrett wrote:
>
>> Recently, while working on XML logging, I ran into a really lame
>> issue/bug. Here's the relevant work around for XML logging, and a
>> ticket which describes some wackiness in the message view which I
>> believe to be related.
>>
>> http://trac.adiumx.com/changeset/16183 and http://trac.adiumx.com/
>> ticket/4226
>>
>> To summarize, I'm of the opinion that our internal notification
>> system sucks. A lot. Going forward, it's going to make implementing
>> logging, especially the <event> tag, a pain in the ass. What should
>> we do, if anything, to improve it? Augie suggested a central
>> NotificationCenter for listObject status notifications. I think it
>> would be nice to have categories of events. You could subscribe to
>> that entire category and get all of the notifications in that  
>> category.
>>
>> What do you guys think?
>>
>> -Colin
>>
>> _______________________________________________
>> Adium-devl mailing list
>> Adium-devl at adiumx.com
>> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>>
>