by Steve Lopez

Just When You Think Chess Can't Get Any Weirder Dept.: Two weeks ago in ETN, I made some jokes about fistfights. This week, I see this item appear in the chess news. I suspect that we haven't heard the last of this one. But, c'mon, let's be reasonable here. Toss a little kid out of a major chess tournament over what amounts to a minor schoolyard scuffle? Oh, puh-leese! If you have to devise a punishment, just do what they did in school: take the kid's ball away and give it back at the end of the tournament. And, if you must, order the parents to keep the kids separated. But tossing the kid out was a bit like using a cricket bat to swat a gnat. I'm a parent and, trust me, scuffles and disputes go on all the time; you have to use a little common sense when you're dealing with children and their misbehavior.


by Steve Lopez

Last week, we looked at setting up chess engine tournaments. This week, we'll describe (briefly) how to "publish" them on the Interrant. This article will assume several prerequisites:

Last week's ETN showed the dialogue in which you set up your engine tournament. By clicking the "Publish" button, you'll get the following dialogue:

The first step is to confirm that you want to put the event on the Interrant by checking the "Publish tournament" box. The next order of business is to tell the program where on the Web you want the games to be sent; this is accomplished through the various fields in the "Connection" section of the dialogue:

You'll see a "Test" button at the end of this section of the dialoue. After you've filled in the requisite info, click this button to test your connection to the server and make sure that you've set the connection up correctly.

Finally, you can set how often the tournament files will be updated (in the "Update" section of the dialogue, of course). You can update the files every x number of minutes; this allows visitors to your site to view games in progress (this is especially useful for games played at longer time controls). If you'd rather have your tournament updated at the end of every game, you have the option to do this as well.

This is all you have to do in Fritz to have your engine tournament published on the Web. However, there are a few extra steps you'll want to take in order for your visitors to be able to get to the tournament.

Add a link on your main welcoming page that sends your visitors right to the tournament page. In my example, I'd add a description of the tournament with an accompanying button they'll click to go to the event's index page (in my case, the HREF behind the button would send them to "/0702/index.html"). I'd typically add this link before setting up the event; then, when I access my site via FTP to add the new directory for the tournament's files, I'd just upload the revised welcoming index page and the new button graphic at the same time. Do this in advance and add a "start time" to your index page, so that visitors know when to log in to view the games. Your visitors must also have Java scripting enabled in their Web browsers to be able to see the games, so it might be a good idea to provide this info as part of your description as well.

Your link will take the visitor to the tournament's index page. This will provide additional links to the individual games of the event. Clicking on one of these links jumps themn to a page in which they can play out the game on their browser using a Java-based chessboard. When you set up the event and start it, Fritz uploads the requisite chessboard graphics and Javasript plus updates the index and individual game pages automatically without any further intervention by you. And, while this next part comes under the general heading of "Duh", please remember that your computer has to be connected to the Interrant the whole time the tournament is in progress for these pages to be automatically updated.

Until next week, have fun!

You can e-mail me with your comments, suggestions, and analysis for Electronic T-Notes.

Click here to return to the main Electronic T-Notes page.

© 2002, Steven A. Lopez. All rights reserved.