| Re: [ecf-dev] Optionally Using ECF Functionality |
Scott,
No. BTW, do you mean a chat view as in the IM chat, or the example collab chat?
This is the ID of the view we want to use: org.eclipse.ecf.presence.ui.chatroom.ChatRoomManagerView
I'd prefer not to add ECF dependencies into our build system. It is complex enough already...Understood...complex build systems seem to be the way of the plugin world. But I'm not sure that even an ECF extension point would really help you with avoiding this, as if I'm reading you right you probably want to include ECF plugins/bundles in the version of you product targeted for Eclipse 3.3, but not for versions targeted for Eclipse 3.2 or earlier...is that right?
Well, we don't want to necessarily include ECF at all. If a user opts in and installs ECF we'd like communication features in our perspective. Essentially we'd like to detect an extension point at runtime, query for the presence of the necessary ECF plugins, and via the schema create the ECF view in our perspective. The extension point schema would allow us to create the view without having to reference ECF classes (avoiding the build and tight coupling issue.)
Currently we have some ECF boilerplate code that creates an IRC container and passes that to the chatroom view. I see no reason why this could not be encapsulated into ECF. Thoughts?
thanks! ken