create extensible tooltip API

[agnosticlines]

What is the feature you'd like to have? Would be really awesome to see Binary Ninja get a native/built in implementation of FRIEND or it's newer fork AIME this would allow reverse engineers to stay inside of Binary Ninja instead of alt+tabbing or control+fing ISA pdfs to find out what side effects an instruction has.

A screenshot of it in use on IDA from the FRIEND repo:

There's only a few considerations for implementation I think such as how it'd work on the IL level:

• Would it work at all?
• Would it just work on the disassembly views?
• Would there be equivalent instructions so it'd map the IL operations to the underlying instruction visually?
• Would the IL have it's own documentation for side effects etc

Not sure the last one would make sense, but just wanted to get it down as an issue so it can be tracked :-)

Also how the documentation would be generated, I assume V35 wouldn't want to maintain a bunch of scripts to parse lots of architecture PDFs, but maybe if they implement the hover the community could share databases similar to Ghidras FIDB or IDA's FLIRT?

As awesome as it'd be to have a set of known good instruction semantics provided with Binary Ninja I get that that's probably not going to happen :)

Is your feature request related to a problem? I still have to leave Binary Ninja to do RE sometimes

Additional Information: Intern project? ;-)

Paging: @psifertex and @jonpalmisc cause I said I'd make an issue

[fuzyll]

Need to have a callback or UI plugin that is capable of doing this (extensible tooltip API).

[agnosticlines]

I feel like the tooltip API should be a separate issue, while this issue would depend on that API, I think having instruction set documentation as a first class feature would be really cool.

[psifertex]

We have no plans to implement the instruction set documentation as a first class feature, just the tooltip API since porting the existing plugin at that point should be really straight forward.