Just glancing at your tutorial for the Applet (which I seem to recall is necessary to read, to make an Interactive diagram from scratch), it seems it's not just a matter of moving the pieces - it seems all sorts of special steps/reading is needed besides, unless I'm not getting my head around the instructions
I wonder where you got that idea. It literally did not require anything other than typing the number 12 and 10 for the board size, pressing 'Apply', set up the position on the (now) 12x10 board by moving the desired pieces from the table there, pressing 'Initial position', and then 'GAME code'. Because (like would be the case for most variants) all the pieces you need are already in the table with the move you want them to have, all with acceptable 1-letter IDs too.
I am sorry if it seems I am badgering you, but there is a reason: if glancing at the instructions causes such a gross misconception, the description is obviously inadequat, and should be improved. I just want to get a better fis on what is wrong with it.
I see that your variant uses fast castling, though; I don't think the the GAME code supports that, even though the Interactive Diagram does. But this would be a show stopper anyway, no matter who creates the Diagram. That it is currently not completely trivial to select fast castling in the Applet is just an oversight: just like the piece table contains multiple Pawns for use in Shatranj/FIDE/Omega/Wildebeest it could also display two Kings with different moves, one for fast castling, the other for normal. It is undoable to put versions of all pieces in the table with every move each could conceivably have, but Pawns, Kings and castling are needed very frequently, so for those it woould make sense. If no one points out the problem, though, it will never be cured...
@ Haru:
If you could post the 'code' for the Interactive Diagram you just made for Wide Nightrider Chess, I'd be grateful.
Note you can always let your browser display the 'Page Source' of the comment (preverably first viewed in isolation through the View link, so that there is less on the page), and copying the Diagram description from there.
I wonder where you got that idea. It literally did not require anything other than typing the number 12 and 10 for the board size, pressing 'Apply', set up the position on the (now) 12x10 board by moving the desired pieces from the table there, pressing 'Initial position', and then 'GAME code'. Because (like would be the case for most variants) all the pieces you need are already in the table with the move you want them to have, all with acceptable 1-letter IDs too.
I am sorry if it seems I am badgering you, but there is a reason: if glancing at the instructions causes such a gross misconception, the description is obviously inadequat, and should be improved. I just want to get a better fis on what is wrong with it.
I see that your variant uses fast castling, though; I don't think the the GAME code supports that, even though the Interactive Diagram does. But this would be a show stopper anyway, no matter who creates the Diagram. That it is currently not completely trivial to select fast castling in the Applet is just an oversight: just like the piece table contains multiple Pawns for use in Shatranj/FIDE/Omega/Wildebeest it could also display two Kings with different moves, one for fast castling, the other for normal. It is undoable to put versions of all pieces in the table with every move each could conceivably have, but Pawns, Kings and castling are needed very frequently, so for those it woould make sense. If no one points out the problem, though, it will never be cured...
Note you can always let your browser display the 'Page Source' of the comment (preverably first viewed in isolation through the View link, so that there is less on the page), and copying the Diagram description from there.