Repository navigation
Added horizontal byte map view to Atom Map with zoom - #14
Merged
Merged
Conversation
The indented tree grew one row per box, so a long recording — especially a fragmented one, where a moof+mdat pair repeats per fragment — ran to thousands of rows. The new horizontal view draws the boxes onto the file itself: left to right is byte offset, one lane per nesting level, so the map is a handful of rows tall however long the video is. Clicking a block zooms the view to its byte range, with a breadcrumb back out. Boxes too narrow to draw at the current zoom are merged into one block saying how many it stands for rather than dropped, so a 20,000-fragment file is a few blocks that open up as you zoom instead of an empty map. Color says which top-level box a byte belongs to; the palette was checked for colorblind separation and contrast against both themes. A Horizontal/Vertical toggle picks between the new view and the original tree, and the choice is remembered. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0191Yrv8pTa7ujjv9iC9WiZE
|
Tip All tests passed and all changes approved!🟢 UI Tests: encoding-helper-storybook: 2 changes accepted as baselines |
|
Tip All tests passed and all changes approved!🟢 UI Tests: encoding-helper-playwright: 2 tests unchanged |
for more information, see https://pre-commit.ci
|
Codecov Report❌ Patch coverage is
🚀 New features to boost your workflow:
|
The byte-proportional map could not give a moov under 1% of the file room for its 24 children, so it summarised the whole subtree into one block and most of what the indented tree shows went missing at the default zoom. The Atom Map now offers two horizontal views, chosen alongside the tree from one control. Structure, the new default, sizes each box by how many boxes its subtree holds rather than by bytes, so every box in the file is drawn and labelled at once — the tree turned on its side. Bytes is the previous proportional map, kept because it is the one that shows a 99%-mdat file and whether moov comes before mdat. Merged runs are also cut as soon as they are wide enough to draw. A 20,000 fragment file collapsed into a single anonymous bar before; it now striates into blocks whose density is the fragmentation, each carrying the color of whatever fills most of it, so a fragmented recording reads as the sample data it mostly is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0191Yrv8pTa7ujjv9iC9WiZE
The structure view is the one worth having, and keeping a second axis meant carrying a scale parameter through the placement, the layout, the readout and the byte-offset ruler for a view nobody wanted. Dropping it also removes a rule that was working against structure. A box narrower than 2% was not opened up, because on the byte axis descending into a sub-1% moov drew lane after lane of identical slivers. On the structure axis a box's width is its subtree size, so that rule only hid children that would have fit. Gone, the view now draws everything the panel has room for and nothing less. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0191Yrv8pTa7ujjv9iC9WiZE
The map is the view; a selector between it and the indented tree was one button row standing between the tab and the thing worth looking at. Nothing the tree carried is lost. Every block is already a button whose aria-label is its type, role, offset and size, so those numbers are reachable by keyboard and screen reader as well as by hovering, and the Report tab still writes the whole tree out as indented text — the integration test now counts the map's blocks against that listing, so the two cannot drift. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0191Yrv8pTa7ujjv9iC9WiZE
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Atom Map now displays MP4 boxes in a horizontal orientation by default, mapping them onto the file's byte axis. This solves the problem of the indented tree view becoming thousands of rows tall for fragmented recordings.
Key changes:
atomLayout.tsmodule with geometry calculations for positioning atoms on the byte axis, handling clipping, collapsing, and grouping logichttps://claude.ai/code/session_0191Yrv8pTa7ujjv9iC9WiZE