Re: [Scid-users] engine auto-install

2014-11-26 Thread Gregor Cramer
> If you think SCID should not install the > engine, the logical > solution would be to not list "chess". OTOH, there does not seem great > harm if > the engine was installed in SCID as a duplicate of Stockfish. But not listing "chess" may irritate other GUI's, IMO this cannot be the solution (Ko

Re: [Scid-users] engine auto-install

2014-11-26 Thread H.G. Muller
Fulvio schreef op 11/26/2014 4:51 PM: > The list will be used by tcl code to install the engines and interact > with the user, but i do not want to write the tcl code to parse the .eng > files (because i know that there will be ten thousand changes like the > ones that you just proposed; and then

Re: [Scid-users] engine auto-install

2014-11-26 Thread H.G. Muller
Fulvio schreef op 11/26/2014 4:08 PM: > In your previous post you talked about apt-get, so i believed that we > were talking about distro packages. > For example when you install scid on a debian machine with: > sudo apt-get install scid > the package manager suggest that you should install also s

Re: [Scid-users] engine auto-install

2014-11-26 Thread H.G. Muller
Gregor Cramer schreef op 11/26/2014 4:11 PM: > Thanks for your answer. > > I like to propose some more attributes: Great. Any suggestion for what would be useful is welcome. This is intended to service every conceivable GUI, and some GUIs might value other information than others. So it is good i

Re: [Scid-users] engine auto-install

2014-11-26 Thread Fulvio
Gregor Cramer wrote: > Fulvio wrote: > >> So as usual the GUI developers have to do the hard work... >> > > I don't agree that this is the hard work, IMO H.G. Mullers proposal is quite > appropriate for a solution of auto-installing engines. The GUI has to do the > work anyway, because the

Re: [Scid-users] engine auto-install

2014-11-26 Thread Gregor Cramer
Fulvio wrote: > So as usual the GUI developers have to do the hard work... I don't agree that this is the hard work, IMO H.G. Mullers proposal is quite appropriate for a solution of auto-installing engines. The GUI has to do the work anyway, because the user of this GUI might interact with the aut

Re: [Scid-users] engine auto-install

2014-11-26 Thread Gregor Cramer
>> Where can I find the definition of the file format for an .eng file? > The original proposal for the *.eng format was made here: > http://www.talkchess.com/forum/viewtopic.php?t=53674&start=0 Thanks for your answer. I like to propose some more attributes: 1. Short identifier with version num

Re: [Scid-users] engine auto-install

2014-11-26 Thread Fulvio
User discussion of SCID wrote: > User discussion of SCID schreef op 11/26/2014 9:43 AM: > >> Honestly I would have preferred a single file /etc/chessengines ... >> > The problem with this is that, although potentially easier for GUIs, it > becomes > far harder for engines: they would all n

Re: [Scid-users] engine auto-install

2014-11-26 Thread Ben St-Pierre
> There is no 'submit comment' button on that page. You need to create a SF account and log in, HG. Then you'll see ​​a Discussion, with a box to respond. I've linked to your previous comment. -- Download BIRT iHub F-Type

Re: [Scid-users] engine auto-install

2014-11-26 Thread User discussion of SCID
It seems Gregor Cramer posted a question there, but I have no idea how to answer it. There is no 'submit comment' button on that page. So I just answer it through the list: > Gregor Cramer > 15 hours ago > Where can I find the definition of the file format f

Re: [Scid-users] engine auto-install

2014-11-26 Thread User discussion of SCID
User discussion of SCID schreef op 11/26/2014 9:43 AM: > Honestly I would have preferred a single file /etc/chessengines ... The problem with this is that, although potentially easier for GUIs, it becomes far harder for engines: they would all need some non-standard install script that would edit

Re: [Scid-users] engine auto-install

2014-11-26 Thread User discussion of SCID
User discussion of SCID wrote: > I was hoping that SCID too would be interested in adopting this system. > Obviously getting this to work smoothly is strongly dependent on the > number of GUIs as well as engines that adopt this method, and if we > cannot achieve a 'critical mass' the endeavor is