Well, the boards are HTML tables, so rotating them doesn't seem to be an option. I also don't see any point in it; just rotate the board back 45 degrees, and it becomes a normal board. You just have to keep in mind that the Betza angular specification have to be a bit different, for pieces that are not totally symmetric.
As to hexagonal boards: perhaps. It would be possible to build a table on a grid of half-width or half-height cells, an merge two cells bordering on their long side into one by colspan="2" or rowspan="2" parameters. And do that in a masonry-like pattern. That would give the same topology as a hexagonal board. By suppressing the borders and specifying transparent square shades, you could the use a whole-board image with true hexagons as background.
The script just refers to the table cells by HTML id of the <td> elements, and would not have to know about the 'skewed' layout. The only thing that would have to be changed is the routine that constructs the table. You might need more parameters than just files and ranks to describe the board. E.g. the files and ranks parameters could define the left and bottom sides of a diamond, and a third parameter could specify how many 'short diagonals' should be left in the center. (Where the default 0 would give you a rectangular board).
Move descriptions would of course look strange and asymmetric, like frblvvssQ for a rook-like move along 6 rays. AFAIK there is no hexagonal Betza notation.
Well, the boards are HTML tables, so rotating them doesn't seem to be an option. I also don't see any point in it; just rotate the board back 45 degrees, and it becomes a normal board. You just have to keep in mind that the Betza angular specification have to be a bit different, for pieces that are not totally symmetric.
As to hexagonal boards: perhaps. It would be possible to build a table on a grid of half-width or half-height cells, an merge two cells bordering on their long side into one by colspan="2" or rowspan="2" parameters. And do that in a masonry-like pattern. That would give the same topology as a hexagonal board. By suppressing the borders and specifying transparent square shades, you could the use a whole-board image with true hexagons as background.
The script just refers to the table cells by HTML id of the <td> elements, and would not have to know about the 'skewed' layout. The only thing that would have to be changed is the routine that constructs the table. You might need more parameters than just files and ranks to describe the board. E.g. the files and ranks parameters could define the left and bottom sides of a diamond, and a third parameter could specify how many 'short diagonals' should be left in the center. (Where the default 0 would give you a rectangular board).
Move descriptions would of course look strange and asymmetric, like frblvvssQ for a rook-like move along 6 rays. AFAIK there is no hexagonal Betza notation.