Community
Participate
Working Groups
Seems like a logical choice for it to be in the 'Properties' view in my opinion.
Not sure I agree that service properties belong in the properties view, as these properties are unlike many other properties displayed in properties view...and wouldn't this add a fair number of dependencies (?)...but I'm +1 if you want to go for it.
I'll mess with this over next few days.
Fix/enhancement released to HEAD.
I see that this has been implemented with tabbed properties. It certainly introduces more dependencies to the plug-in, I do not know the exact number. The idea I originally had in mind was to just have a separate plug-in that contributed an IPropertySource adapter to IServiceInfo.
(In reply to comment #4) > I see that this has been implemented with tabbed properties. It certainly > introduces more dependencies to the plug-in, I do not know the exact number. > The idea I originally had in mind was to just have a separate plug-in that > contributed an IPropertySource adapter to IServiceInfo. > Yes, it does add require bundle-level dependency on org.eclipse.ui.views.properties.tabbed. I would be open to other impls. Actually, I sort of hope/expect that all this can be replaced or enhanced by the discovery view work from lemmy. I don't yet know what it's dependencies are, however. I'm open to alternative implementations too.
(In reply to comment #5) > I would be open to other impls. Actually, I sort of hope/expect that all this > can be replaced or enhanced by the discovery view work from lemmy. I don't yet > know what it's dependencies are, however. CQ 2038 (http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2038) depends on EMF 2.3. org.eclipse.emf.ecore, org.eclipse.emf.edit, org.eclipse.emf.edit.ui to be precise.
