Draw a tune's notes at a size that reads easily, wrapping its bars and using the margin beside it

Open
#306 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start by finding the music fence renderer and how it configures abcjs in Work, Edit, and Present. Check how the available width and adjacent margin are determined, then compare abcjs's wrap and staff width options. Done means notes stay readable, bars wrap in narrow columns, and Work can use the otherwise empty margin beside the staff.

Written by the indexing model from the issue text.

Description

A music fence draws its staff exactly as wide as the text and fits the whole line of bars into it, so in a narrow column the notes are small.
In Work, on a window 1280 pixels wide, the staff is 503 pixels, the margin beside it 312 pixels and empty when no aside is there, and a note's head is about 20 pixels; in Edit's column, beside the editor, it's smaller still. In Present the notes are easy to see.

```music
X:1
T:Twinkle, Twinkle
M:4/4
L:1/4
K:C
C C G G | A A G2 | F F E E | D D C2 |]
```

Today: however narrow the column, the four bars are fitted onto one line, and the notes shrink to fit.

Instead:

  • Notes are drawn at a size that reads easily, and a tune wraps onto more lines when its column is too narrow for them, as abcjs can (wrap, with a set staff width). It's bigger in Edit and on a phone too, at the cost of a taller tune.
  • In Work, a staff takes the margin beside it too, when no aside is next to it, as the margin is otherwise empty.

Widening Work's text column for everything was turned down: every paragraph's lines would grow past what reads easily.

Came up in the retro of the 2026-11-16 review, from #99.

Dominant language
JavaScript
Stars
0
Forks
1
Avg merge
2d 4h
Merged PRs (30d)
26

Getting set up

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.

More from jzheaux/reader

All issues in jzheaux/reader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.