Community
Participate
Working Groups
When trying to create a new completion proposal processor to handle ranking the content assist by interest for the Mylyn integration, the ICElement was needed, but I was unable to get it from the proposal. This element should be included as it is in JDT so integrations can take advantage of the easily accessible information on a ICElement when computing the proposals that they want to display.
Computing the ICElement for a proposal is expensive. Even JDT computes this information only lazily when a proposal is selected in the proposal popup (LazyJavaCompletionProposal). I.e. Filtering proposals based on associated ICElement is at least sub-optimal performance-wise.
If this is sub-optimal, is there a good way to compare a handle from and ICElement to and IBinding?
(In reply to Shawn Minto from comment #2) > is there a good way to compare a handle from and ICElement to and IBinding? I know the implementation of some CDT features such as type hierarchy and call hierarchy uses IndexUI.elementToBinding() to convert an ICElement to an IBinding. I don't really have a good handle on whether this method is performant enough to run on each proposal during content assist. If you're still interested in this, could you describe your use case a bit more?
