Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Thu, Nov 5, 2015 07:33 PM UTC:

I now even made a design-help page, which has input fields for all the parameters (clearly labeled with their function, and pre-filled with the default values), and buttons to add those to the diagram description. Itcontains a diagram, and performs the conversion Description -> Actual Diagram each time you change the description (e.g. by adding an extra piece). When you are finally done it prints the HTML code with the diagram description in a text memo, so that the user can copy-paste it into his own page, at the point where he wants the diagram to appear.

There is still one issue, though, and that is the filenames of the piece images. The design page that is running on my website taps into the piece images I have on-line there (hgm.nubati.net/rules/sym/). This is a directory that does not contain an index.html file, so when you browse there, it prints a listing of all the (.png) files there. The Design Page uses this to compile a list of the available image files, to present it to the user when the latter clicks a 'Pick' button. The user can then click one of the names to transfer it to the 'Image filename' field. (And the piece name and ID are derived from the filename, if not specified, so that he only has to supply the Betza move in that case. And even that is not needed for orthodox pieces.)

If this page were to be hosted on chessvariants.org, this would currently not work: if, for example, the 'graphics.dir/alfaerie' directory would be specified as the piece-image directory, the directory listing of that page would be eclipsed by the index.html that is in it. That means the 'Pick' button would not show anything, so that people would have to figure out for themselves what the names are of the alfaerie files they want to use.

Perhaps a server-side script could be used to provide a list of filenames of these directories, so that the JavaScript running in the client could request it from the server, and present the list (possibly fetching the images to display them with it) to the user, so he can pick the image.

But of course these are just minor issues in the user-friendliness of the designing process. For users that upload their own images, they would have to refer to those from their html submission anyway, and they would know how they named them.


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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.