TASEmulators / TASEmulators/BizHawk
Address manager
Nobody has claimed this yet.
- 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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