Better Borders

I have a bit of time this afternoon. Let’s see what we might do about borders that would be better. I think we’ll rep;lace most of this code, but it’s working and mostly harmless, so I’ll commit and work from where we are with the hacked-in, er um official spike experimental version. Commit: border cell spike. My approach now will be to figure out what an approximation to something one might actually want, given what we know now. In particular, I think that the BorderMap / BorderList thing might be useful and I’m pretty sure it has no other purpose now but to serve what we need. I’ll try not to damage it too badly, just in case it has some other utility. Here’s that whole family: @dataclass class Border: side: tuple boundary: str border_offsets: ClassVar[dict] = { (-1, 0): ((0, 0), (0, 1)), ( 1, 0): ((1, 0), (1, 1)), ( 0, -1): ((0, 0), (1, 0)), ( 0, 1): ((0, 1), (1, 1)), } def select_boundary(self, a_dictionary): return a_dictionary[self.boundary] def line_coordinates(self, cell_xy,…