Vector35 / Vector35/binaryninja-api

work-list feature

Open
#2,373 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

We've talked about TODO lists in the past but it would be great to be able to have a generic work-list concept where things like a subset of:

  • Functions
  • Xrefs
  • Tags
  • Text notes
  • etc

Could be added to a simple work-list to enable checking off particular tasks.

Basic/MVP features could include:

  • Deleting elements
  • Adding elements
  • "Completing elements"
  • Filtering completed or all elements
  • Saving work-lists to BNDBs

Advanced features could (but almost certainly wouldn't happen in an MVP) include:

  • Integration into collaboration to allow assignments
  • Go crazy with other project planning features such as due-dates, dependencies, etc.

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

The issue names no files, tests, or entry points. Start by defining the MVP data model and how work-lists relate to functions, xrefs, tags, and text notes; then identify the API and BNDB persistence entry points. Done means the agreed MVP supports adding, deleting, completing, filtering, and saving work-list elements.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.