Not a problem at all.
I have been going through the plugin.xml and wanted to know if my outline of the steps I need to take, makes sense. I think I will have to make the changes in o.e.i.client.widgets/plugin.xml
1) Define a command in the 'Commands' section, say, o.e.i.client.widgets.commands.ConnectCore. Basically, I add another command to the extension point org.eclipse.ui.commands.
2) Similar to how CreateItemHandler is defined, I add a handler in the extension point org.eclipse.ui.handlers, where the class would point to something like o.e.i.client.common.ConnectCoreHandler and the commandId would be the previously defined command. So does this entry basically map the Handler to the Command name?
3) Define ConnectCoreHandler similar to other handlers, i.e. it extends from AbstractHandler and defines an execute function. The current code in ConnectCoreAction seems to specify paths to the icon gif to use. I guess that is older code as the newer code specifies similar information in the plugin.xml itself.
So ConnectCoreHandler should follow the new code pattern. I am thinking of defining an execute function which spawns a hostname and port dialog box, but this is just for starters.
I know that the end goal as part of issue 262 is to list the Cores that the client is attached to and to separate the client from the build, those would be the next set of steps, once this works.
Hope this helps.
Regards,
Ram