🚀 go-pugleaf

Dear friends

About five months ago I initiated a project based on TurboChess
program written in Pascal. I had a few reason for choosing this 
very particular problem.

. To Understand how a chess program works.
. To Make a chess program more coherent to average programmer.
. To Practice and Apply Object Oriented concepts.
. To Use and practice C++ in a fairly large project.
. To initiate a resereach on tranformating procedural programs 
  -to OOP without re-writing the algorithms and data-structure
  -and only changing the segmentation of the program.
  
Ever since, I had discoverd a few important points on the whole 
problem that made me to decide to share my experiments with 
other people like yourself. I was hoping that having a working
program
  a- has the potentail of less algorithm errors.
  b- helps to find a good way to standardize transformation
     from any Pascal program to C++ program.
I am afraid expireince shows that if a program is written in 
a such way that was not considered to be extensible or even 
modifiable, there is a little that anyone can do without 
overhauling the program.

My supervisor Mr Don Beal ( an activce researcher in chess and 
co-writer of many papers and books such as advances in chess.5)
convinced me to design and implement my own chess program which
aims at:

. An interactive chess program
. A chess program which can be understood by anyone
. An extensible chess program
. A chess program which does compromises the simplicity
  against effeciency.

These points clearly mean that I am not going to write a 
competative chess but, a chess program which people can 
understand and hopefully make it better themselves.

After my communication to TCPLUS and CHESS bulletin boards 
I have received the following's messages either indicating
an interest or giving advice.


I think all or most of you would be interested in designing your
chess program which fits the mentioned description, as well as 
not spending much time on it. So, here is my suggestion. Why not 
set a timetable for different part of the chess i.e.

- Data Structure design	(possible classes and objects )
- Detail Design
- UserInterface Design
- Chess Implementation
- UI implementation

Of course, these are just suggestions and can replaced with 
better ones anytime.

The above scheme does have its advantages

- Contribute as little or as much as you want
- Participate on certain areas i.e. UI, Move generator
- Improve your knowledge about chess, C++ and design
  of complicate multi-purpose application
  
The very famous word from a very famous person " all the 
innovations and new ideas come from small teams with lots of
enthusiasm".

I would be eager to hear your opinions and your criticism on any
parts of this proposal.

By the way, there will be a computer chess tournoment in mid of
August and hopefully our chess program can evolve from a 
prototype to a full-blown product by then.


I am looking forward to hearing from you soon.




Ramin
*****