Author: Michael Yee
Date: 10:37:28 09/04/05
Go up one level in this thread
On September 04, 2005 at 12:58:38, A. Cozzie wrote: >... >His solution is to not support UCI. My solution is to not care. >... >anthony I second your perspective--worrying about someone else's GUI sounds very strange to me. In any case, commercial programs seem to have taken all sorts of approaches: - open protocol (own gui) : shredder uci - open protocol (shared gui) : gandalf, deep sjeng - proprietary protocol (shared gui) : fritz, junior - semi-locked version of open protocol (own gui) : chessmaster - several proprietary protocols (shared gui) : chess tiger I don't know much about their market shares, but all appear at least somewhat successful. My opinion (for what it's worth--not worth much, I admit!) is it'd be best to support as many protocols and operatings systems as possible to make your product useable by the largest number of people. Additionally, I think having your gui support WB and UCI would make it attractive to people who might not even care about a new engine so much. (I'm guessing you already are planning this, though.) As others have noted in the past, there's still lots of room for innovation in chess guis, e.g., tutorial features, tournament handling (e.g., correct swiss system pairing), etc. Michael
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.