| | | |
| This is all fine and perfect. Except that the impl | | This is all fine and perfect. Except that the impl |
| ementation is spread accross several classes. - It | | ementation is spread accross several classes. - It |
| would be much nicer if the ContactListUI would no | | would be much nicer if the ContactListUI would no |
| t know how to handle each single of those types.. | | t know how to handle each single of those types.. |
| if this would be possible. | | if this would be possible. |
| | | |
| Another thing is the current implementation of swi | | Another thing is the current implementation of swi |
| tching the groups of a user. The AbstractContactLi | | tching the groups of a user. The AbstractContactLi |
| stUI#getMenuManagerForEntry will create a 'Change | | stUI#getMenuManagerForEntry will create a 'Change |
| Group' submenu for all 'IContactListContact' - ie. | | Group' submenu for all 'IContactListContact' - ie. |
| not for meta contacts.. or for groups themselves | | not for meta contacts.. or for groups themselves |
| .. This is not really that nice.. and it has to ch | | .. This is not really that nice.. and it has to ch |
| eck by itself (or better said the ChangeContactLis | | eck by itself (or better said the ChangeContactLis |
| tContribution class) if the user is connected to t | | tContribution class) if the user is connected to t |
| he protocol in which the IContactListContact is in | | he protocol in which the IContactListContact is in |
| . (Otherwise he can't change groups) | | . (Otherwise he can't change groups) |
| | | |
| t | | t | # IUser
|
| | |
|
| | | currently it defines a method 'setName(..)' which |
| | | allows the caller to modify the handle of the user |
| | | in the contact list.
|
| | |
|
| | | This is all nice and good, but a 'DefaultPeer' obj |
| | | ect is created for ever incoming packet - this cla |
| | | ss extends DefaultUser, which implements IUser .. |
| | | the problem is that it would be much better if IPe |
| | | er would hold a reference to IUser - The same with |
| | | IContactListContact and IUser .. This way there c |
| | | ould be only one IUser object.. so if the name is |
| | | changed it is automatically reflected everywhere.. |
| | |
|
| | |
|
| | | in addition it would need a few listeners so the U |
| | | I can be updated immediately.
|
| | |
|
| # Contact List Context Menu | | # Contact List Context Menu |
| | | |
| The AbstractContactListUI currently manages it's o | | The AbstractContactListUI currently manages it's o |
| wn MenuManger through it's own extension point. (J | | wn MenuManger through it's own extension point. (J |
| ust because i didn't know how to do it the eclipse | | ust because i didn't know how to do it the eclipse |
| -way) - see <http://www.eclipse.org/articles/artic | | -way) - see <http://www.eclipse.org/articles/artic |
| le.php?file=Article-action-contribution/index.html | | le.php?file=Article-action-contribution/index.html |
| > - ie. register the MenuManager using org.eclipse | | > - ie. register the MenuManager using org.eclipse |
| .ui.IWorkbenchPartSite.registerContextMenu(MenuMan | | .ui.IWorkbenchPartSite.registerContextMenu(MenuMan |
| ager menuManager, ISelectionProvider selectionProv | | ager menuManager, ISelectionProvider selectionProv |
| ider) | | ider) |
| | | |
| | | |
