Enter Your Reply

What I don't fully understand is why you stress that it should be HTML and
JavaScript. Perhaps because I don't fully understand how you envision this
to be used.

When I encounter a PGN game somewhere (as text on a web page, or as a
downloadable .pgn file), I always view it with WinBoard (by pasting it in,
or loading it from the downloaded file). Then you have all the
functionality you say: you can step through the game, while viewing the
comments, edit the game by adding or deleting moves at the end, add
comments to it, or edit the exsting comments, save the (edited) game on
file, or copy it (or the position) to the clipboard, save positions as a
diagram on a bitmap file.

Plus you can do more, as it is also possible to have an engine analyze the
positions in the game, and show its scores and PVs in a separate window. I
always have a WinBoard shortcut on my desktop to quickly start it up when I
need to view PGN.

I don't see how HTML would add anything to this. The reason I made the
JavaScript viewer was to allow people to follow games live with a browser.
It was never meant as an analysis tool.

BTW, the castling tag is not really needed, absense of castling could
simply be indicated in the FEN for the initial position.