Vector35 / Vector35/binaryninja-api

re-organize first-party plugin actions

Open
#8,090 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Effort: Trivial Impact: Medium UI: Menu Bar
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

Right now, the following plugins put their menus in the top-level "plugin" menu when they belong elsewhere. This issue tracks moving those into more appropriate locations:

  • (Jordan) BinExport (move to File / Export)
  • (Mason) BNTL (Maybe a new "Types" top level menu?)
  • (?) Export as DWARF (move to File / Export)
  • (Josh) Ghidra (should be split into Import / Export and moved to the appropriate sub-menu probably?)
  • (Mason) Load IDB File (maybe this can be buried much deeper now that the better workflow is using OwO?)
  • (Mason) Load SVD File (maybe "import"? Maybe a Types menu?)
  • (Brandon) Run EFI resolver (probably should go away entirely once we have the right workflow eligibility?)
  • (Mason) TriCore / Debug Current Instruction (should not be a sub-menu but maybe belongs under "Analysis"? Or if it's super rare, just put it in the command-palette only, not a UI menu.
  • (Mason) WARP (I like this being under a tyop-level "Types" menu but we can discuss this)

Blocked by #8091

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by resolving the dependency on #8091, then review the menu registrations for the listed first-party plugins, including BinExport, BNTL, Ghidra, WARP, and the file-loading actions. Done means each item has an agreed destination, removal decision, or command-palette-only treatment, with the top-level Plugin menu no longer holding actions that belong elsewhere.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering, tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.