[Pydev-code] Proposed change to Hover Participants

[Mark L. <mid...@ve...>]

I'm making a change to PyDev and will submit a pull request if 
appropriate. But I'd like to know if there's a better way to do what I'm 
trying to do, or if the behavior I'm after is not of general interest.

The issue I'm having is that I implemented a hover participant, and I'd 
like it to preempt the TextHover contributions from PyDev when it has 
something to contribute. This was a simple change, including the 
addition of a preference to toggle the behavior of ignoring PyDev's 
TextHover info when one or more hover participants contributes hover info.

However, it seems I should probably make a more general mod as well, 
even though the above meets my current use case. What I have in mind is 
to add two attributes to the hover participant extension point. One 
attribute is an integer that specifies priority, and the other is a 
boolean that specifies whether or not to preempt PyDev's built-in 
TextHover. The behavior will be that registered hover participants will 
be called in decreasing priority order, and as soon as one contributes 
hover info, the remaining participants are not invoked. If any 
participant contributes hover info, the built-in PyDev TextHover will be 
invoked subsequently only if the aforementioned boolean attribute for 
the contributing participant specifies that PyDev TextHover should not 
be ignored.

Does this make sense? Is there a better way to approach it? Is this 
behavior of general interest?

-Mark