Problem is that for those who have JavaScript switched off this section would be empty. I tried to cure that by putting <div> tags around the header and Diagram (= <table>) together, and unhide that through JavaScript rather than just the <table>, so they would both fail to appear when JavaScript is disabled.
This, however, appears to make FireFox forget how a <H2> header should look on this page. I guess this could be cured by explicitly repating the required style in a style property of the <H2> element. What style properties are used in our articles?
For uniformity with other articles I changed the header to 'Setup'; the Diagram itself already announces that it is interactive, just below the header. Other articles have the Interactive Diagram in their Setup section. But 'modest variants' usually don't have such a section.
I also enhanced the Diagram script to make the board location where the piece will be shown in move diagrams configurable. By default it would use the board center for this. Which is usually what one wants, as this leaves the most room for distant moves on all sides. For Cylinder Chess this prevented the move diagrams to show any moves that crossed the edge, though, making them indistinguishable from the FIDE counterparts, and thus pretty useless. I made use of the new midX and midY parameters to make the pieces appear on the left edge in move diagrams.
This doesn't really provide an unambiguous indication of castling, as the a-side castling is now not shown (as it crosses the edge). Since the article spends ample text on explanation of the castling rule this doesn't seem a real problem, however.
Another case where an alternate positioning in the move diagrams was desirable was Scheherazade: many leapers there are so long range that even on a 10x10 board they don't have any moves at all! So in the Diagram I posted as a comment a page earlier I now make the pieces appear near a corner.
BTW, the case of a Rook blocked on a rank and still being able to use the other side of the obstacle by wrapping is covered by the Interactive Diagram, when tou place the obstacle by hovering in the path of the Rook in its move diagram. The move diagrams do support (single) blocking of sliders and activation of hoppers that way.
Problem is that for those who have JavaScript switched off this section would be empty. I tried to cure that by putting <div> tags around the header and Diagram (= <table>) together, and unhide that through JavaScript rather than just the <table>, so they would both fail to appear when JavaScript is disabled.
This, however, appears to make FireFox forget how a <H2> header should look on this page. I guess this could be cured by explicitly repating the required style in a style property of the <H2> element. What style properties are used in our articles?
For uniformity with other articles I changed the header to 'Setup'; the Diagram itself already announces that it is interactive, just below the header. Other articles have the Interactive Diagram in their Setup section. But 'modest variants' usually don't have such a section.
I also enhanced the Diagram script to make the board location where the piece will be shown in move diagrams configurable. By default it would use the board center for this. Which is usually what one wants, as this leaves the most room for distant moves on all sides. For Cylinder Chess this prevented the move diagrams to show any moves that crossed the edge, though, making them indistinguishable from the FIDE counterparts, and thus pretty useless. I made use of the new midX and midY parameters to make the pieces appear on the left edge in move diagrams.
This doesn't really provide an unambiguous indication of castling, as the a-side castling is now not shown (as it crosses the edge). Since the article spends ample text on explanation of the castling rule this doesn't seem a real problem, however.
Another case where an alternate positioning in the move diagrams was desirable was Scheherazade: many leapers there are so long range that even on a 10x10 board they don't have any moves at all! So in the Diagram I posted as a comment a page earlier I now make the pieces appear near a corner.
BTW, the case of a Rook blocked on a rank and still being able to use the other side of the obstacle by wrapping is covered by the Interactive Diagram, when tou place the obstacle by hovering in the path of the Rook in its move diagram. The move diagrams do support (single) blocking of sliders and activation of hoppers that way.