Bug 208713 - [imchat][presence][ui] add API for contributing roster entry properties to MultiRosterView
Summary: [imchat][presence][ui] add API for contributing roster entry properties to Mu...
Status: RESOLVED WONTFIX
Alias: None
Product: ECF
Classification: RT
Component: ecf.presence (show other bugs)
Version: 1.2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2007-11-04 19:31 EST by Scott Lewis CLA
Modified: 2014-05-09 13:33 EDT (History)
1 user (show)

See Also:
remy.suen: review-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Lewis CLA 2007-11-04 19:31:21 EST 
It should be possible for a plugin to add to the set of properties associated with the user's acount, whenever a presence update is sent via the MultiRosterView (via presenceSender.sendPresenceUpdate).  This would include when the user connects, and a presence update AVAILABLE is sent, as well as other types of presence updates.  

I'm not sure whether it would make more sense to have an extension point or programmatic API, but perhaps extension point for org.eclipse.ecf.presence.ui.MultiRosterView?  i.e. some new interface that gets called when MRV.sendPresence is called?...perhaps passed the MultiRosterAccount and returns IPresence...or maybe just properties to add to IPresence instance.

This will make it possible/easy for other plugins that want to add properties (and use them on the receiving end of presence info) to do so.
Comment 1 Remy Suen CLA 2007-11-21 08:26:25 EST 
Will there be an actual user interface for this or are adopters expected to craft their own user interface as needed and then hook onto this mechanism?
Comment 2 Scott Lewis CLA 2007-11-21 11:56:42 EST 
(In reply to comment #1)
> Will there be an actual user interface for this or are adopters expected to
> craft their own user interface as needed and then hook onto this mechanism?
> 

I would prefer that it have no user interface...and leave UI to adopters.
Comment 3 Scott Lewis CLA 2007-12-08 13:46:51 EST 
Any progress on this?  If possible, it would be nice to have this in 3.4M4 so that the roster menu can/could be used more effectively for upcoming demos (among other things).
Comment 4 Remy Suen CLA 2007-12-09 22:22:32 EST 
(In reply to comment #3)
> Any progress on this?  If possible, it would be nice to have this in 3.4M4 so
> that the roster menu can/could be used more effectively for upcoming demos
> (among other things).

I'm in exam season over here so I won't be able to investigate this.
Comment 5 Scott Lewis CLA 2014-05-09 13:33:05 EDT 
Resolving as wontfix due to limited resources.  If contributors or committer resources become available for additional work in this area then please reopen.