Re: [Scid-users] Opening tree easier? Multiple tries at once? Disabling tree sync temporarily?

2007-08-23 Thread Marcin Kasperski
> The points 1. and 3. are done now ("open base as tree" and > "stop refreshing the tree when board changes"). I will release > a Scid 3.6.19rc1 sometime soon. Nice :-) > Concerning the "multiple Trees", I tend to think 2 Tree > windows is enough (like engines windows). What do you think > about

Re: [Scid-users] [patch] Handling directory hierarchy better on Linux, without spoiling the current state on Windows

2007-08-23 Thread Marcin Kasperski
> always use Scid from the > compilation dir, and maybe others do the same (I understand > people that are reluctant to issue a make install as root). If somebody on Linux is not wishing to install as root, I would recommend sth like ./configure BINDIR=$HOME/bin SHAREDIR=$HOME/share/scid or

Re: [Scid-users] Opening tree easier? Multiple tries at once? Disabling tree sync temporarily?

2007-08-23 Thread pgeorges
Marcin (and others ...), The points 1. and 3. are done now ("open base as tree" and "stop refreshing the tree when board changes"). I will release a Scid 3.6.19rc1 sometime soon. Concerning the "multiple Trees", I tend to think 2 Tree windows is enough (like engines windows). What do you think

Re: [Scid-users] [patch] Handling directory hierarchy better on Linux, without spoiling the current state on Windows

2007-08-23 Thread pgeorges
Marcin Kasperski a écrit : > It should not be necessary, if somebody issues just > ./configure > it is equivalent to > ./configure BINDIR=/usr/local/bin SHAREDIR=/usr/local/share/scid > (both those defaults are set in configure file and seem reasonable) > > Maybe the fallback could help i

Re: [Scid-users] [patch] Handling directory hierarchy better on Linux, without spoiling the current state on Windows

2007-08-23 Thread Marcin Kasperski
> So, for people that don't issue a correct : > ./configure BINDIR=$HOME/scid SHAREDIR=$HOME/scid > (...) > Scid will fallback to the "classical" directories, and this > cannot hurt. It should not be necessary, if somebody issues just ./configure it is equivalent to ./configure BINDIR=/

Re: [Scid-users] Funny things in the source distro

2007-08-23 Thread pascal . georges1
That's not that the source distribution would have been really smaller, but it would have been far cleaner (blush) ! Pascal Selon Marcin Kasperski <[EMAIL PROTECTED]>: > I think that the *source* distribution would be noticeably > smaller, if it did not contain the following files (the list > be

Re: [Scid-users] [patch] Handling directory hierarchy better on Linux, without spoiling the current state on Windows

2007-08-23 Thread pascal . georges1
Thank you Marcin, it is integrated. But before I fully understood what you did, and after I patched the code with yours, I wrote the following fallback code : # detect the case where, under Linux, Scid is used without prior installation # the fallback directory is Scid's exec dir if {! [file isdir

[Scid-users] Funny things in the source distro

2007-08-23 Thread Marcin Kasperski
I think that the *source* distribution would be noticeably smaller, if it did not contain the following files (the list below according to the scid-3.6.18.tar.bz2): Makefile Makefile.bak engines/Phalanx-XXII/book.lrn engines/Phalanx-XXII/position.lrn engines/crafty-20.14/book.lrn engines/cra

Re: [Scid-users] Opening tree easier? Multiple tries at once? Disabling tree sync temporarily?

2007-08-23 Thread Marcin Kasperski
> > There is already some cache for the tree window, and despite > not being as fast as books, I find the Tree window faster in > Scid than its equivalent in Chessbase. I've never used chessbase, but in ChessAssistant the tree tab refreshes instantly. There is some cons there - after changing t

[Scid-users] [patch] Handling directory hierarchy better on Linux, without spoiling the current state on Windows

2007-08-23 Thread Marcin Kasperski
The attached patch (due to my laziness it is in two parts as I just maintan it in this way, apply both in order) changes scid so it complies to the typical Linux way of organising data files (data files are separate from the binary, all paths in use are set-able by ./configure switches) - but it