Hello,
after embedding ChesBrainVB (WB-2)
https://github.com/RZulu54/ChessBrainVB/releases into WinBoard 4.8.0 http://www.open-aurec.com/wbforum/viewt ... 19&t=51528 the engine´s name is not be mentioned/evoked. Why?
Best wishes,
Norbert
WinBoard 4.8.0 and ChessBrainVB
Moderator: Ras
-
Norbert Raimund Leisner
- Posts: 1643
- Joined: Tue May 20, 2008 4:57 pm
- Location: Augsburg - Germany
-
Guenther
- Posts: 4718
- Joined: Wed Oct 01, 2008 6:33 am
- Location: Regensburg, Germany
- Full name: Guenther Simon
Re: WinBoard 4.8.0 and ChessBrainVB
What do you mean by 'embedded'? Can you elaborate a bit more, what exactly you did and where the name does not appear - do you mean the selection list?Norbert Raimund Leisner wrote:Hello,
after embedding ChesBrainVB (WB-2)
https://github.com/RZulu54/ChessBrainVB/releases into WinBoard 4.8.0 http://www.open-aurec.com/wbforum/viewt ... 19&t=51528 the engine´s name is not be mentioned/evoked. Why?
Best wishes,
Norbert
BTW there is already since long a much newer WB version:
http://talkchess.com/forum/viewtopic.ph ... board+beta
-
hgm
- Posts: 28499
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: WinBoard 4.8.0 and ChessBrainVB
With 'embedded' Norbert usually means what other people call 'installed', i.e. put it in the GUI's engine list. 'Installed' is actually a misnomer, causing confusion under Linux, where 'installing' an engine means to download its package from the repository, and moving it to the right places in the file system (through a command like "sudo apt-get install fruit"). At that point any GUIs on your machine would still be unaware of the presence of the engine, however. (Unless the GUI and the engine package support the 'plugin standard'; e.g. installing the fairymax package will automatically make Fairy-Max appear in XBoard's engine list after such an install.)
I coined the term "registering the engine to the GUI" for the task normally accomplisehed through the XBoard 'Load Engine' dialogs (in particular the "Add engine to list" checkbox. This step consists of making the GUI aware of the location of the engine executable, whether to treat it as UCI or WB engine, any special arguments that might be needed in the engine startup command, whether it should use GUI book. 'Embedding' is also not a bad name for this.
I coined the term "registering the engine to the GUI" for the task normally accomplisehed through the XBoard 'Load Engine' dialogs (in particular the "Add engine to list" checkbox. This step consists of making the GUI aware of the location of the engine executable, whether to treat it as UCI or WB engine, any special arguments that might be needed in the engine startup command, whether it should use GUI book. 'Embedding' is also not a bad name for this.