Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Mon, Nov 9, 2015 10:04 AM UTC:

In equiping my variants with the interactive diagram I noticed the following pattern is very common: I want the diagram to 'float' to the left (so that the text nicely wraps around it), and to the right of the diagram (i.e. the start of the text in the 'Setup' section) I have a list summarizing the piece types and their starting squares.

Now I typically want that list to be clickable, so that clicking on a line in that list would display its moves on an empty board ('footprint') in the diagram. This can be done by including an onclick="ShowMoves(N)" parameter in the list-item (li) tags, where N is the number of the piece type. ShowMoves() is an entry point in the JavaScript associated with the diagram.

If we want the diagram to be usable in submissions that do not have the HTML checkbox ticked, e.g. by replacing the first occurrence of '[diagram]' / '[/diagram]' pairs (or perhaps upto the next empty line) by the HTML code for the diagram (i.e. link to the .js file plus the text after '[diagram]' in a {div id="diagram"} tag pair) in the submission script, it would be nice if this functionality was still available without HTML too.

I therefore wanted to propose to let the submission pre-processor also scan for tags of the form [p N] at the beginning of lines in non-HTML submissions, where N = 1, 2, 3, ..., to create a list-item tag pair (and surrounding {ul}/{/ul}) with the corresponding ShowMoves() event around the remaining part of the line.


Edit Form
Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.