The Uglyboard Project

Intro | Uglyboard II| Misc | Using | History| End notes | Source Code

Run Uglyboard II!

        Look at some chess games on the program itself. And if you wish to learn more about it, and why I wrote it, please read the rest of the page.

Click Here to run Uglyboard II

Introduction

        Since finishing University, I have taken advantage of the free time available to me, to start to learn to program. The language I decided to start with was Java, as it is (I believe) simpler than C++ and the ability to write Java Applets for web-pages seemed an excellent practical use of any new skills I acquired.
        I soon tired of working through the examples, simply copying text is not programming, and the simple examples were lifeless and dull. I felt the need to try writing a real program of my own. Therefore the 'Uglyboard' Project. By writing an applet to display chess games on web-pages I hoped:

        Perhaps the most important distinction between writing this program and the book examples, is that here from the start I had a good idea of what I wanted to produce, but no idea how to do it. Whereas with examples, you start with the skills, and then find artificial ways of using them. On starting the project I had absolutely no knowledge of the majority of code I would eventually use.

Uglyboard II

        The current version of the program:

Misc. & Limitations

How to Use Uglyboard II

History of Uglyboard

        Why not take the time for a good laugh! Have a look at the earlier versions including my first ever applet.

Take me to something UGLY!

End notes

        Outside debugging bugs I haven't yet found and a few tweaks, Uglyboard II is now finished. This version is (for the moment at any rate) the end of the Uglyboard project, as it has fulfilled my original plans. So here are a few notes on my feelings and what I think I've learnt:

The Code itself

        Feel free to look at the code itself. As some of the lines are far longer than any width of webpage they're likely to be viewed on, they will wrap onto the next line making the code harder to follow. However if the reader has the ability to understand the code they won't have any difficulty with working out a way to solve this (e.g. Select all the text, copy it and paste in notepad.)

The program has grown to a rather large amount of text, which is not thoroughly annotated. However at the top of the file there is an explanation of what each individual 'Method' does.

Okay lets see it then!