Alexander Wagner, wtorek, 19 sierpnia 2008: >The downside of this is, that it requires to start each >engine if you enter config, and actually, as you can not be >sure to know what the user did (imagine renaming phalanx to >rybka e.g. ;) you'd have to start the engine every time the >GUI config is changed. As launching the engine is a bit time >consuming this is actually quite ugly (Jose uses this >approach, e.g.). Considering you'd only want to change some >personality settings for serious game etc. I think guessing default mode when adding new engine is enough, letting users to do what he likes after that. But beginners will be left with working setup from the very beginning.
>If firing up the engine woule not be an issue, I think >engine mode is easy to guess. Just send "uci" and if you get >"uciok", well its uci, if not its xboard. You can (but IMHO >you don't have to) send xboard to crosscheck and "protocol >2" to check which version, but well. >One could proably avoid starting each engine by checksuming >the engines binary and store the value launching the engine >only if the checksum changes. This does not need to be perfectly secure and impossible to hack. The only important thing is that a beginner. who does not understand what UCI or *Board protocol are, is still able to add a new engine downloaded from the Internet. -- Michal Rudolf ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
