commited: r12581 = 7de4cd9aa842418178f0280ccf9c5e473671e0f8
1. It introduces a component registry (UIComponentRegistry.java) that offer the possibility for plugin to replace some default components with their own instances
By default Spark implementation are going to be used
Spark classes that can be replaced:
private static Class<? extends ContactItem> contactItemClass = ContactItem.class;
private static Class<? extends ContactInfoWindow> contactInfoWindowClass = ContactInfoWindow.class;
private static Class<? extends ContactGroup> contactGroupClass = ContactGroup.class;
private static Class<? extends ContactList> contactListClass = ContactList.class;
private static Class<? extends StatusBar> statusBarClass = StatusBar.class;
private static Class<? extends CommandPanel> commandPanelClass = CommandPanel.class;
private static Class<? extends SparkTabbedPane> workspaceTabPaneClass = SparkTabbedPane.class;
private static Class<? extends LoginDialog> loginDialogClass = LoginDialog.class;
private static Class<? extends ThemePanel> themePanelClass = ThemePanel.class;
private static Class<? extends ConferenceServices> conferenceServicesClass = ConferenceServices.class;
2. It also contains changes in Spark code to support such mechanism, separates a bit UI building from business login
and exposes some UI elements through protected get/set methods
Example on how a plugin can register its own ContactItem implementation:
public class TestPlugin implements Plugin {
public TestPlugin()
{ UIComponentRegistry.registerContactItem(TestContactItem.class); }
....
}
where TestContactItem extends Spark ContactItem:
public class TestContactItem extends ContactItem
{ ... }
Phase2:
commited: r12582 = ac966579032b14d708e5cafb625c25a1d5691a80
-Chat and Group Chat changes to support extension through plugin
-created ButtonFactory class responsible with button creations and use it when needed
-UIComponentRegistry is imporved with Chat/GroupCHat registration capabilities
Phase3:
commited: r12583 = c3b1aadf13de5dbb9649868cf12b786174324b9c
-LoginDialog: put username, password, serverName protected get/set methods
-some more get/set methods to expose UI objects
Sub-task
Closed
Major
Attached patch description
1. It introduces a component registry (UIComponentRegistry.java) that offer the possibility for plugin to replace some default components with their own instances
By default Spark implementation are going to be used
Spark classes that can be replaced:
+ private static Class<? extends ContactItem> contactItemClass = ContactItem.class;
+ private static Class<? extends ContactInfoWindow> contactInfoWindowClass = ContactInfoWindow.class;
+ private static Class<? extends ContactGroup> contactGroupClass = ContactGroup.class;
+ private static Class<? extends ContactList> contactListClass = ContactList.class;
+ private static Class<? extends StatusBar> statusBarClass = StatusBar.class;
+ private static Class<? extends CommandPanel> commandPanelClass = CommandPanel.class;
+ private static Class<? extends SparkTabbedPane> workspaceTabPaneClass = SparkTabbedPane.class;
+ private static Class<? extends LoginDialog> loginDialogClass = LoginDialog.class;
+ private static Class<? extends ThemePanel> themePanelClass = ThemePanel.class;
+ private static Class<? extends ConferenceServices> conferenceServicesClass = ConferenceServices.class;
2. It also contains minor changes in Spark code to support such mechanism
Example on how a plugin can register its own ContactItem implementation:
public class TestPlugin implements Plugin {
public TestPlugin()
{ UIComponentRegistry.registerContactItem(TestContactItem.class); }....
}
where TestContactItem extends Spark ContactItem:
public class TestContactItem extends ContactItem
{ ... }