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

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Fri, Apr 29, 2016 06:41 AM UTC:
Having already rewritten most of my pages, and having discussed rewriting them again, I struggle to see how anyone could think that time is my issue! Any improvement takes longer than doing nothing. In any case, I now have enough practice writing virtual multi-cell images to cut and paste within the master document and replace the middle bit correctly than to paste the raw string of braces, tildes, and exclamation marks into the Diagram Designer. Nor only that, I can do the former entirely offline save for uploading the whole. I am currently adding movement diagrams to Man and Beast without even looking at them online. If I find errors when I do upload them the quickest way to correct them is by seeing how the page appears and changing the master document accordingly.

What I meant by inefficient was the problems that I have learned always accompany duplicate code. Over the last few years one of my major tasks at work has been refactoring and centralising tracts of duplicate code. The issues that I know of are that duplication takes up more space, is more susceptible to errors such as typos, and makes extra work if a sudden change is made. The first two I can see applying similarly to substituting another long piece of code. Single-array page will certainly use a single piece set for the array diagram, piece images, and (if any) movement diagrams, and I find it hard to imagine even a multi-array page (be it 3d or multi-subvariant) doing otherwise.

If my idea really is impossible, say so and I will live with it, but don't suggest ways of addressing an imaginary time issue by doing something even more time-consuming.


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.