Cyril Silverman
Cyril Silverman
[Worth noting that SMuFL expresses their bounding boxes in staff spaces.](https://w3c.github.io/smufl/gitbook/specification/glyphbboxes.html)
See Behind Bars, page 5 - "The Stave" > The size of every notation symbol is measured in proportion to the stave size. A stave-space is the distance between two...
Using staff spaces as the unit of measurement allows us to reason about formatting without being coupled to a specific pixel/staffspace ratio.
I do agree on the the staff's total bounding height (4 spaces + 1 line), but I think it's more intuitive to have the staff space go from staff line...
While a good graphical solution, representing this single StaveNote as two independent StaveNotes puts a big burden on `Voice` construction by requiring extra voices with complementary `GhostNotes`. In my experience,...
Another related question: when should `Glyph`'s be initialized? I think, ideally, all `Glyph` based `Elements` would construct their glyphs at the same point in the `Element` lifecycle. Provided that `Elements`...
Well here it goes: How about we rip out all formatting-centric code and start from scratch with a more rigorous set of test cases. I realize this is not a...
Yeah, I'll do that at some point. It seems like it's a lot more work than it actually is. While every element has its own formatting hook, this is unnecessary....
Good question, not sure. I'd guess that they'll mainly remain as is, just that we hook into them a different way. The formatting hooks for things like `Ornament` and `Annotation`,...