draw octants directly rather than relying on font

[dankamongmen]

• implement yQuads() and draw_octant(), pretty obvious extensions of existing code. to allocate up to 3 potential remainder lines, consider that octants will often appear in a rectangular subset of the terminal. we want the distributed excess uniformly distributed across such a region. so:
  • one excess row: break symmetry in any direction (pick an arbitrary tetrad and use it everywhere)
  • two excess rows: go to alternating tetrads
  • three excess rows: break symmetry, do not use three contiguous tetrads
• our Octants are octary arrays of bool, provided as a somewhat opaque constant table
• the 8-line copy-and-paste draw based on the Octant is not the prettiest thing in the known universe
  • we could generalize draw_sextant() and draw_octant() like notcurses did, almost certainly
  • oh bird thou never wert

with that said, i don't think draw_octant() is actually being called lol, so let's not merge this yet. happy to hear early feedback, though.

[dankamongmen]

hrmmm, do the builtin draws only run when we can't find these glyphs in the font? that would explain things. i'd suggest giving them primacy should that be the case, but can understand going the other way.

[jcollie]

hrmmm, do the builtin draws only run when we can't find these glyphs in the font? that would explain things. i'd suggest giving them primacy should that be the case, but can understand going the other way.

Take a look at this. There are a couple of places in Box.zig and Face.zig where the glyphs need to be "linked in" in order for them to be drawn.

[jcollie]

It seems rather tedious and error-prone to convert the name of the octant from "BLOCK OCTANT-12345" to a boolean array like this. With comptime strings and inline for loops this can be made so much easier.

[dankamongmen]

hrmmm, i agree that using the language's native features for this kind of thing would be far less opaque. i'm intrigued, but doubt i'll get to it this weekend--feel encouraged to use this PR as a starting point to do something better. i have no emotional ties to this matrix.

[dankamongmen]

thanks for the pointers to the ziggery, though!

[mitchellh]

I haven't reviewed this PR yet but I agree this code is very C (no surprise!). Zig's comptime facilities should allow us to do something much nicer here I believe.

[dankamongmen]

hrmmm, do the builtin draws only run when we can't find these glyphs in the font? that would explain things. i'd suggest giving them primacy should that be the case, but can understand going the other way.

Take a look at this. There are a couple of places in Box.zig and Face.zig where the glyphs need to be "linked in" in order for them to be drawn.

got it, much appreciated