Re: [jdt-ui-dev] Vote: Potential matches always at the end

["Daniel Megert/ZRH/OTI" <Daniel_Megert@xxxxxxx>]

Randy,

I asked exactly that same question on jdt-core-dev mailing list. Here is a copy of the first:
        A potential match means that the search engine could not resolve everything
        it needed. This can happen if the build path was not correctly set by the
        user (for example some required projects are missing from the build path),
        or if the user code would not compile (for example a class doesn't
        implement all the methods of an interface).

        The main benefit of showing a potential match is that the user can still
        see references and declarations even if his/her code is not ready to be
        compiled.

You might want to follow the discussion there.

My personal opinion is that the concept of potential (or possible) matches is hard to understand for users (see my answer in the jdt-core-dev mailing list) and that only exact matches should be displayed. Because they now do exist in the model and appear in the UI, some users suggested to put them at least at the end of the list in the Search view. 

Dani

"Randy Giffen/OTT/OTI" <Randy_Giffen@xxxxxxx> Sent by: jdt-ui-dev-admin@xxxxxxxxxxx 12/04/01 08:06 PM Please respond to jdt-ui-dev

To:        jdt-ui-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [jdt-ui-dev] Vote: Potential matches always at the end

Dani, could you explain under what circumstances a search result is considered to be a "potential match" and why the fact that it is a potential match is important in determining the sort order.

"Daniel Megert/ZRH/OTI" <Daniel_Megert@xxxxxxx> Sent by: jdt-ui-dev-admin@xxxxxxxxxxx 12/04/01 10:29 AM Please respond to jdt-ui-dev

To:        jdt-ui-dev@xxxxxxxxxxx        cc:                Subject:        [jdt-ui-dev] Vote: Potential matches always at the end

The Search view may contain potential matches (marked with '?'). Whether or not it makes sense to show them at all or if they are in fact wrong matches doesn't matter for this discussion. 

The proposal is to show the potential matches always at the end of the list i.e. the Search view first displays all exact matches sorted by the specified sorter and then all potential matches sorted by the specified sorter.

Please vote until Dec. 11 2001 

Dani