Recent changes to Contribution

Contribution modified by Asher Stern

Asher Stern — Mon, 01 Sep 2014 08:16:33 -0000

--- v5
+++ v6
@@ -26,7 +26,7 @@
     + the jboard.properties file should contain the English strings.
     + If you don't know the string for some other languages, add an English string for each of their properties files, and open a ticket about it.
 + Write small classes and small methods. If you find yourself writing large classes/methods, then it probably indicates a bad design. Try to break the methods and write classes which concentrate on more specific aspects.
-+ In this project, checked exceptions should not be used. Throw only runtime-exceptions. In case you use a method which does throw a checked exception, wrap it with try...catch.
++ In this project, checked exceptions should not be used. Throw only runtime-exceptions. In case you use a method which does throw a checked exception, wrap it with try...catch, and throw a runtime exception from within the catch block. That runtime exception should contain the original exception as the "cause" (set as a parameter in the constructor of the new exception).
 + Do not use any external library. Use only J2SE libraries (libraries in the JDK).

Contribution modified by Asher Stern

Asher Stern — Sun, 31 Aug 2014 10:33:29 -0000

--- v4
+++ v5
@@ -24,7 +24,7 @@
 + Strings presented to the user should not be hard-coded. Instead, they should be written in the properties files, and referred to with the localized() method in org.jboard.jboard.utilities.StringUtils class.
     + The properties files are under the "resource" directory.
     + the jboard.properties file should contain the English strings.
-    + If you don't know the string for other languages, add and English string for each of the other properties files, and open a ticket about it.
+    + If you don't know the string for some other languages, add an English string for each of their properties files, and open a ticket about it.
 + Write small classes and small methods. If you find yourself writing large classes/methods, then it probably indicates a bad design. Try to break the methods and write classes which concentrate on more specific aspects.
 + In this project, checked exceptions should not be used. Throw only runtime-exceptions. In case you use a method which does throw a checked exception, wrap it with try...catch.
 + Do not use any external library. Use only J2SE libraries (libraries in the JDK).

Contribution modified by Asher Stern

Asher Stern — Sun, 31 Aug 2014 10:31:16 -0000

--- v3
+++ v4
@@ -44,5 +44,5 @@
 + Improve error handling.
 + Build an installer (to install jboard on the user's computer).
     + It should be a multi-platform installer.
-    + It should be designed for user who are not familiar with Java
-    + It can then be added into the "downloads" page of this project.
+    + It should be designed for users who are not familiar with Java
+    + It can then be added into the "Files" page of this project.

Contribution modified by Asher Stern

Asher Stern — Sun, 31 Aug 2014 10:30:39 -0000

--- v2
+++ v3
@@ -42,3 +42,7 @@
 + Support user input of mouse and touch screen events
     + Currently only keyboard events are supported to make moves on the board.
 + Improve error handling.
++ Build an installer (to install jboard on the user's computer).
+    + It should be a multi-platform installer.
+    + It should be designed for user who are not familiar with Java
+    + It can then be added into the "downloads" page of this project.

Contribution modified by Asher Stern

Asher Stern — Sun, 31 Aug 2014 10:26:19 -0000

--- v1
+++ v2
@@ -1,25 +1,44 @@
 How to join and contribute
 --------------------------
+
+Welcome every body who wants to contribute this project.
+
+Below are few guidelines for successful contribution.

 [TOC]

-Welcome every body who wants to contribute this project.
+### General guidelines

-# General guidelines

-Below are few guidelines for successful contribution.

 1. Please contact the project owner and let him know about the changes you are intending to make.
 + Go to the project's GitHub, fork the repository, make the changes and ask for a pull request.
 + Please avoid, as much as you can, modifying existing code. Add your own new classes. Eventually you will have to make some small changes in the existing classes, such that your new classes will take effect, but make these changes as small and local as you can.

-# Coding guidelines
+### Coding guidelines

-1. Give a documentation for every class with a main comment. Each public method should be documented as well.
-+ Constant values should not be hard coded, but added to the Constants class
-+ Strings presented to the user should not be hard-coded. Instead, they should be written in the properties files, and referred with the localized() method in org.jboard.jboard.utilities.StringUtils class.
+1. Write a documentation for every class as its a main comment. Each public method should be documented as well.
++ Constant values should not be hard coded, but added to the org.jboard.jboard.Constants class.
++ Strings presented to the user should not be hard-coded. Instead, they should be written in the properties files, and referred to with the localized() method in org.jboard.jboard.utilities.StringUtils class.
+    + The properties files are under the "resource" directory.
+    + the jboard.properties file should contain the English strings.
+    + If you don't know the string for other languages, add and English string for each of the other properties files, and open a ticket about it.
 + Write small classes and small methods. If you find yourself writing large classes/methods, then it probably indicates a bad design. Try to break the methods and write classes which concentrate on more specific aspects.
 + In this project, checked exceptions should not be used. Throw only runtime-exceptions. In case you use a method which does throw a checked exception, wrap it with try...catch.
 + Do not use any external library. Use only J2SE libraries (libraries in the JDK).
+
+
+### Issues to develop
+
+This is a list of issues proposed for improving the project.
+
+1. Display list of moves.
++ Add the option to save and load PGN files.
++ Support also SAN notation.
+    + Chess engines like SJeng use SAN notation, so they are currently not supported.
+    + Currently only coordinate notation is supported.
++ Support user input of mouse and touch screen events
+    + Currently only keyboard events are supported to make moves on the board.
++ Improve error handling.

Contribution modified by Asher Stern

Asher Stern — Sun, 31 Aug 2014 10:14:22 -0000

How to join and contribute

How to join and contribute

General guidelines

Coding guidelines

Welcome every body who wants to contribute this project.

General guidelines

Below are few guidelines for successful contribution.

Please contact the project owner and let him know about the changes you are intending to make.
Go to the project's GitHub, fork the repository, make the changes and ask for a pull request.
Please avoid, as much as you can, modifying existing code. Add your own new classes. Eventually you will have to make some small changes in the existing classes, such that your new classes will take effect, but make these changes as small and local as you can.

Coding guidelines

Give a documentation for every class with a main comment. Each public method should be documented as well.
Constant values should not be hard coded, but added to the Constants class
Strings presented to the user should not be hard-coded. Instead, they should be written in the properties files, and referred with the localized() method in org.jboard.jboard.utilities.StringUtils class.
Write small classes and small methods. If you find yourself writing large classes/methods, then it probably indicates a bad design. Try to break the methods and write classes which concentrate on more specific aspects.
In this project, checked exceptions should not be used. Throw only runtime-exceptions. In case you use a method which does throw a checked exception, wrap it with try...catch.
Do not use any external library. Use only J2SE libraries (libraries in the JDK).