Hi there!

We need some discussion to finish this.

On Feb 22, 2009, at 11:34 AM, Pascal Georges wrote:

> There is no need to keep Crafty, it is no longer needed by any  
> feature of
> Scid.

Crafty is out of the equation.

> phalanx-pg is not a correct name. Maybe phalanx-scid ?
> Current name is phalanx, which collides with original phalanx which  
> is no
> longer maintained. So indeed there could be both versions installed
> (probability is low but it is possible), so a renaming makes sense.

I like phalanx-scid.

Should Toga II be renamed from "fruit" to "togaII", "toga2", "togaii"  
or "toga"?  I noticed that on windows it's already called  
"TogaII.exe", but I think we should use small caps for the rest of the  
OSes.

How should the renaming be handled? from the engine's makefile (I  
think for phalanx this would be ok) or from Scid's makefile (for toga)?

Can we eliminate the engine's parent folders? instead of "engines/ 
Phalanx-XXII/phalanx.scid" why dont we use "engines/phalanx-scid" and  
the same for toga. What's the reason behind that setup?

So far, these are the paths where Scid would search for the engines:

$::scidExeDir
::scidExeDir/engines
::scidShareDir/engines
::scidUserDir/engines
/usr/local/share/scid/engines
/usr/local/bin
/usr/bin
/usr/local/games
/usr/games

I tested those paths running on Windows, Mac and Ubuntu; on Mac and  
Ubuntu they work if Scid is run from the compilation folder also, I  
would have tried on Windows but I don't know how to compile there (I  
edited scid.gui by hand to test there).

You can check the code at the end of the message (note that I renamed  
the engines).

Cheers,
Israel

-------

# Read the user Engine List file now:
#
catch { ::enginelist::read }
if {[llength $engines(list)] == 0} {
   # No engines, so set up a default engine list:
   set scidlet "scidlet"
   set phalanx-scid "phalanx-scid"
   set togaII "togaII"
   if { $::windowsOS } {
     set scidlet "scidlet.exe"
     set phalanx-scid "phalanx-scid.exe"
     set togaII "TogaII.exe"
   }
   set scidEngPaths [list \
       $::scidExeDir \
       $::scidExeDir/engines \
       $::scidShareDir/engines \
       $::scidUserDir/engines \
       /usr/local/share/scid/engines \
       /usr/local/bin \
       /usr/bin \
       /usr/local/games \
       /usr/games \
       ]
   # The next four lists should have the same length!
   set scidEngCmds [list \
       "${phalanx-scid}" \
       "$togaII" \
       "$scidlet" \
       ]
   set scidEngNames [list \
       Phalanx-Scid \
       "Toga II" \
       Scidlet \
       ]
   array set parentDirs "
     ${phalanx-scid} {\"/Phalanx-Scid\" \"/Phalanx-XXII\"}
     $togaII {\"/togaII1.2.1a\" \"/toga\" \"/togaII\" \"/togaII1.2.1a/ 
src\"}
     $scidlet {\"./\"}
   "
   set isUCI [list \
       0 \
       1 \
       0 \
       ]
   # Let's search the engines:
   foreach cmd $scidEngCmds name $scidEngNames uci $isUCI {
     set leave 0
     foreach path $scidEngPaths {
       if { [file executable "${path}/$cmd"] } {
         engine [list \
           Name $name \
           Cmd  "${path}/$cmd" \
           Dir  . \
           UCI  $uci \
           UCIoptions {} \
           ]
         set leave 1
       } else {
         foreach parent $parentDirs($cmd) {
           if { [file executable $path$parent/$cmd] } {
             engine [list \
               Name $name \
               Cmd  "$path${parent}/$cmd" \
               Dir  . \
               UCI  $uci \
               UCIoptions {} \
               ]
             set leave 1
             break
           }
         }
       }
       if { $leave } { break }
     }
   }
}


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to