codechenx / tv / 37464473484
48%
master: 51%

LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
37464473484

push

github

codechenx 
Lay the table out by content, and make the stats panel readable

The table gave every column an equal share of the terminal and left-aligned
everything, so a two-character number sat in a seventeen-character field and
digits never lined up. Columns are now measured from their header and a sample
of their values, numbers and dates align right, headers take their column's
alignment, and only a column cut short by the width cap takes a share of what
is left over. Alternate rows carry a lifted background, which is what makes a
wide row easy to follow across, and the palette moved into one var block.

Measurement has to be repeated while a load runs. drawUI measures as soon as
the first batch lands, so measuring only there sized every column from about
ten rows and truncated everything longer for the rest of the session.
refreshWhileLoading re-measures periodically and once more on completion.

The footer said "Column Type: Str  |  0,0": a bare pair of indices with no
totals to measure them against and no name for the column they referred to. It
now reads "score · Num   r42/400  c2/4", with the source and its shape on the
left.

Both stats plots went through asciigraph, which draws a line through the
values, so a frequency distribution came out as a near-flat line that said
nothing. They are horizontal bars now, labelled and carrying counts and
shares, which is what a histogram and a value count actually are. That was the
only use of asciigraph, so the dependency goes too.

Also in the panel: it sizes itself to its contents instead of taking 80% of
the screen and leaving most of the box empty; its spacers paint, because a nil
Flex item paints nothing and the table showed through around it; whole numbers
read as whole numbers rather than "25.0000"; and the mode reports "none (all
distinct)" instead of presenting an arbitrary value. calculateMode and the
frequency ranking both break ties by value — taking the map's first maximum
meant the reported mode chang... (continued)
Source Files on build 37464473484
Detailed source file information is not available for this build.