|Re: [ecf-dev] Optionally Using ECF Functionality|
Ken Gilmer wrote:
Well, the only way that I can immediately think of not to have *any* compile time dependencies (not on core or any ECF bundles) would be to create an extension point that takes only strings and does the right things (e.g. creates the ECF view inside of a given perspective...i.e. where perspective id is passed in I in?). Anyway, if we can define such an extension point that will work for you (i.e. do the right thing with/for your user interface) then we can add it...obviously it can't depend upon anything but platform UI code (since ECF can't/couldn't depend upon your company's UI).
But after thinking about it a little more it does seem like having something like what the bot API does, along with some attributes in extension point schema for doing the right thing WRT your/other UI would be doable.
BTW, not sure whether you were aware of it, but ECF 1.0.0 added a 'Communications' perspective. Perhaps that could be of some usefulness.