Right now WARP, much like SigKit, lacks in the UI department, this is stopping us from giving the user control over manually applying functions and other UX related features.

What is the UI responsible for?

1. Displaying and filtering possible matches for the current function.
2. Displaying the selected match underneath the possible match list (much like the selected type in the types sidebar)
3. Allowing the user to apply the selected match, and also possibly edit / remove it.
4. What else?

Integration with the networked WARP component would need the following:

1. Selected match should display the server that the match came from, along with information like the author and other exposed metadata.
2. The user must be able to block authors, or otherwise blacklist functions. If we do add a way to blacklist functions this might need a callback so that we can also post the blacklist to the server so that the server does not send down those functions anymore.

Initially we had thought adding a clickable link in the function header would be the UI for overriding match selection. However this really does not work well with the design of the product, i.e. navigating to a function will show the cross references local to that function and the stack info a variable info. You shouldn't need to open a popup to view possible matches.