|
Refactoring to Support JFace Content Providers
|
The presence API (plugin: org.eclipse.ecf.presence) has been enhanced to support JFace viewers. Specifically,
the roster interface classes (IRosterManager, IRoster, IRosterEntry, IRosterGroup, IRosterItem) have been enhanced
so that they can easily be used as the basis of an JFace ITreeContentProvider. This allows the
use and automatic update of a roster (buddy) list by an ECF provider that implements the presence API (e.g. the XMPP provider). For example, here is code in the new plugin
org.eclipse.ecf.presence.ui that creates a tree viewer to display multiple rosters:
protected void setupTreeViewer(Composite parent) {
treeViewer = new TreeViewer(parent, SWT.BORDER | SWT.MULTI
| SWT.V_SCROLL);
getSite().setSelectionProvider(treeViewer);
multiRosterContentProvider = new MultiRosterContentProvider();
multiRosterLabelProvider = new MultiRosterLabelProvider();
treeViewer.setLabelProvider(multiRosterLabelProvider);
treeViewer.setContentProvider(multiRosterContentProvider);
treeViewer.setInput(new Object());
}
With this approach, the UI/viewer code does not need to know anything about the messaging to change/update the roster
model. This model is managed by the ECF provider (XMPP) and when
The MultiRosterContentProvider class (and others to support this new approach) are available
in the (new) plugin: org.eclipse.ecf.presence.ui. See the classes in the org.eclipse.ecf.presence.ui package
for example usage and reusable base classes.
|
|
Overall Improvements to Presence API
|
A number of improvements were made by refactoring the presence API (plugin: org.eclipse.ecf.presence). Interface and
class names were changed for more consistency, interfaces and classes were moved around, and the API was simplified in many
ways. For details see bug: #167363
|
