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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Sun, Oct 14, 2018 08:24 PM UTC:

Well, WinBoard uses asterisk for non-space in FENs, and I was planning to do that here too, rendering the corresponding squares as transparent. But for combining two pieces there are still plenty other characters available. The current version of my renderer (fen2.cgi) uses parentheses to enclose piece names for which no dressed-letter ID is available. I could easily switch that to braces, I have no preference in that respect. I don't think it is a good idea to use the same enclosing for full piece names and IDs, though. Infix notation is unambiguous enough.

I have now made it such that a 1x1 FEN always uses fully transparent background, so that it can be used as a piece in other drawing routines (such as the Interactive Diagram). That means the CGI argument p=... has become somewhat redundant; to get a bishop (which before required p=wbishop) now can simply be done by f=B. That means that the piece-combining also works, f=N-Q would give you an Amazon, and f=_Q an inverted Queen. I think I will keep the p=filename argument, but implement it to do the same as f=(filename), i.e. slam parentheses (or braces) around it, and then treat it as FEN.

It might also be worthwile to have a way to add board markers. Perhaps as a second 'color FEN' through the argument m=, where each letter then indicates a color (and perhaps a shape) to be drawn over the corresponding square.


Edit Form

Comment on the page Alfaerie Variant Chess Graphics

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.