There has to be a shift in use case design more than making it prettier.
There has to be a shift in use case design more than making it prettier.
To start with, we have undo, which is a simple feature but it underlies some design decisions that are going to show up in other features in the near future as well.
Because we have the ability to separate user interactions from our internal analysis we can not only undo, but also better support collaborative editing and upgrading of older saved databases.
In terms of features we already have, we have a static data flow implementation that allows you to query register values at addresses which greatly simplifies a lot of analysis plugins. Here's an example:
http://arm.ninja/2016/03/08/intro-to-binary-ninja-api/
(The domain name is a coincidence, Q was just a beta tester, not officially affiliated with us)
Notice how much more robust and simpler the final implementation of that plugin using our data flow is:
https://github.com/Vector35/binaryninja-api/blob/dev/python/...
Do you have the one where a line goes to one side by more than a screen's width, goes down a tad, and then goes back sideways to nearly where it started?