Check out Alice Chess, our featured variant for June, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Thu, Feb 4, 2021 02:23 PM UTC:

I have started work on creating a piece database. At this point, I have created three tables, and I will be working on a script for updating them. The three tables are called PieceInfo, PieceImages, and PieceNames.

Each one includes a column called PieceID. For simple consistency, I expect it makes sense to use Betza codes, perhaps with some added standardization when two different codes could otherwise be used for the same piece, such as alphabetizing parts that could be written in an arbitrary order. Since I don't work with Betza codes much, others may have more insight on this. Presently, this column can be up to 32 characters in length. That's just a guess, since I don't know how long Betza codes typically get.

PieceInfo will contain a description of how a piece moves and the ItemID for the Piececlopedia page on that piece. This will be a one-to-one table.

PieceImages will be a many-to-many, or maybe many-to-one, table in which PieceIDs are associated with URLs to images stored in /graphics.dir/. I should probably include separate columns for White and Black images.

PieceNames will be a many-to-many table in which piece names are associated with PieceIDs. This will be indexed by a combination of PieceID and ItemID, where the ItemID will be for a page describing a game using that piece. The Name column will store the name used for the piece on that page.

The purpose behind this database is to build a better and more comprehensive Piececlopedia by collecting extensive data on piece usage and naming. Also, the PieceImages table may prove helpful for Game Courier or the interactive diagrams.

Since I am not versed in Betza code, and this is a big project, I am thinking of writing code for crowd-sourcing the work and for mining the interactive diagrams for data, since it already includes much of the requisite date in standardized forms.


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.