Single Comment

I guess the different behavior of the Chess and Ultima Diagrams occurs because these make use of different Diagram scripts. These past months I have been working on a 'next generation' of the Diagram script, which for now is called betzaNew.js instead of betza.js (in the same directory, /membergraphics/MSinteractive-diagrams/). This new script uses the AI's move generator for move entry and execution. This allows entry of moves with more than 1 locust victim, which the old code (from before the addition of an AI) that is being replaced could not handle. That conversion is not really completed yet (move notation for triple captures is still lacking), but Ultima can only be handled through betzaNew.js.

This betzaNew.js also differs from the old one by including a style attribute for the table cells "backround-size:contain", (the piece images are displayed as background, so the highlighting markers can be displayed in front of those as cell content), to force too-large images to fill the cell. The latter was done to allow use of larger-than-needed raster (as opposed to SVG) piece images, which then would allow zooming without too much image degradation. E.g. the Diagram in the Minjiku Shogi article uses the 50x50 alfaeriePNG set, but has a 100x100 GIF image for the Fire Dragon. (This because the GIF, which I needed for animation, does not seem to support an alpha channel, which would cause a ragged outline, unless I make the browser smoothen it on demagnification.)

This 'contain' specification also stretches images that are too small to fill the cells, and apparently stretch the horizontal and vertical dimension independently.

The Diagram script was designed for using piece images of a uniform size. The easiest solution is probably to edit the images so they all get the same size. This is what I did for the 'Horizons' piece set used in the Stone Garden Chess article.