| 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) |
| | | |
| # 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) |
| t | | t |
|
| | |
|
| | | # Game Instance Provider
|
| | |
|
| | | Currently the game instance provider only supports |
| | | game instances from type 'SimpleGameInstance' - t |
| | | he reason for this is, that it is serialized using |
| | | standard java serialization .. which would not wo |
| | | rk if the classes which need to be loaded come fro |
| | | m another classloader..
|
| | |
|
| | | it would be better to use IMemento - and each game |
| | | instance provider should be responsible on it's o |
| | | wn to serialize and deserialize the stored game in |
| | | stances.
|
