Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Fri, Jul 24, 2020 03:43 PM EDT:

Let me move this discussion to a more applicable thread. Are you changing the color after you rendered it as PGN, through a flood fill? That would indeed not work, because the anti-aliasing would produce all kind of average shades where the color touches the outline, some very close to white but not exactly so, and the flood fill would not capture those. You would have to change the color when it is still SVG.

The way I do it in the renderer is that I load the SVG in a memory buffer, search it for #FFFFF (or whatever I know the original color to be), and substitute that for the desired color, (it is a text file!) before I pass it to the routine that renders it as a bitmap. And then use a routine to save bitmaps as PNG.

I suppose it should be very little work to change the renderer (which now parses CGI query strings handed to it as 'environment' variables) to take its requests from the normal (argc, argv) command-line arguments (or even hard-code what color / size / orientation we want), and then run it in a shell script to render every SVG file. But I guess we should be a bit selective in what we render; we probably only want rotated versions of the orthodox pieces. And I am not sure whether we would want to have complete alfaerie sets in red or green.


Edit Form

Comment on the page Diagram Editor with scalable 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.