Tatsh / dade

100%

push

github

rbplus: draw a chart as SVG or as a page

The suffix given to dump-chart --image now chooses the form: .png as before,
.svg for the same drawing as vectors, and .html for a page whose every note
answers to a click.

The renderer drew straight onto a Pillow image, so a second form would have
meant a second copy of the geometry. It now lays a chart out once and draws
through a surface, and canvas.py holds the three: PillowCanvas, SVGCanvas, and
HTMLCanvas. Only the surface differs, so the three forms cannot drift apart.

The vector surface needs no arithmetic of its own. The layout was already
computed at three times the finished size, so that the raster surface could be
reduced once at the end and smoothed by it, and those same numbers are the view
box. A chart that writes at 1604 by 1596 pixels carries viewBox="0 0 4812 4788"
and scales without loss.

HTMLCanvas subclasses SVGCanvas rather than reimplementing it, so the page
embeds exactly the document the .svg file would hold. Around each note is a
group carrying its index, and a click or a keypress fills a Bootstrap card with
what the note is: its side, whether it is held, slid, vertical, swiped back or
aimed at an alternative target, its hit, spawn and travel times, the lane it was
laid out in, its route selector, its group, its flags, and its chain and path
fields. Bootstrap comes from its content delivery network, so the page wants a
connection the first time it is opened.

Naming a suffix nothing writes is a user error rather than a fault, and
dump-chart reports it as one instead of letting the ValueError through.

Checked against the hard chart of 100000109.rb: all three forms write, the SVG
parses as XML with 736 note groups, and the page carries 736 matching records,
34 of them reporting a hold. What is not checked is the two forms against each
other pixel for pixel, there being no SVG rasteriser installed here; they share
their drawing calls and coordinates, which is an argument rather than ... (continued)

4202 of 4202 branches covered (100.0%)

Branch coverage included in aggregate %.

236 of 236 new or added lines in 4 files covered. (100.0%)

16611 of 16611 relevant lines covered (100.0%)

5.0 hits per line