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

Enter Your Reply

The Comment You're Replying To
(zzo38) A. Black wrote on Fri, Nov 28, 2008 04:54 AM UTC:

Actually, I think Forth is a excellent program language, and I like Forth. I do think there are some problems with Axiom, for one thing you have to write your own evaluation function even if you don't want to. And Axiom also requires some Zillions code to be written as well. Also it has many problems that it has just because Zillions has these problems also. For example, you have to make picture for each piece and the board, for each game you have to do that (with Z_GenImg library you don't have to do that though). And some things just can't be done in Zillions even with a external engine. In addition, neither Zillions nor Axiom is free software.

But, I am working on a new program, called Moxia ('Moxia' is a anagram of 'Axiom'), which is free software (free as in speech, and also as in you don't have to pay), standalone (doesn't require Zillions or Axiom to run), cross-platform (XUL-runner based), and more things. Such as making stacks of multiple pieces on the same cell, not requiring icons of pieces (text-based coding can be used), fix some bugs present in Zillions (such as having multiple partial moves to the same location), and various other things. Moxia is also Forth based.


Edit Form

Comment on the page Mad Queen Shogi

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.