TASEmulators / TASEmulators/BizHawk

Address manager

Open
#1,700 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

App: EmuHawk Open to design proposals only Request: Feature/Enhancement
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

We have to juggle addresses all the time, lots of them are shared between tools, and they mostly have the same structure around them: domain, length, name, description, etc.

I think it would be better to have a uniform format for addresses in general (json?), and to reuse the whole list in the tools that need it: ram watch, ram search, hex editor bookmarks, symbolic trace-logging (whenever we have it), etc. The format would include flags representing which tools want this address.

This also includes having a dialog that just edits those addresses, and possibly converts to and from the new format, until all tools support it.

edit: a watch is similar to what a cheat needs, but not precisely, consider refactoring to not even have [a separate Watch class] --adelikat

edit: see also #677

Contributor guide

Open the contributing guide

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 reviewing the existing ram watch, ram search, hex editor bookmarks, symbolic trace-logging, and separate Watch class mentioned in the issue, along with related issue #677. Determine how these tools currently represent addresses and whether a shared format and editing dialog can cover them; done would mean a decided design and coordinated support across the listed tools.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
devtools, tooling
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.