Hi,

I released Scid 3.6.19 at
http://prolinux.free.fr/scid/

(Source files for Linux and binary for Windows).

Note that all Scid Pocket code corresponding to version 0.25 is now up
to date and can be found in the pocket directory along with engines
ported to Pocket PC.

For those curious, here is the changelog:

- clean up of configuration files (thanks to Marcin Kasperski)
- books' path is now configurable through ./configure and Makefile.conf
(SHAREDIR) (thanks to Marcin Kasperski)
- some code added to support Novag's chess board. This code is not
finished (and will not be finished until I put a hand on a Novag
Citrine), so the menu entries are hidden to the user until further notice.
- Added a new menu entry : "open base as Tree window" (a kind of
shortcut that avoids switching between bases)
- Refresh of Tree window can be toggled
- A Tree window can be opened for each base through the command tools-
open base as tree. So now the meaning of "locked" for a tree window has
changed. This used to mean display information of *this* base in the
Tree window, but now it means, if the Tree window is locked, that
closing the Tree implies closing the associated base. This seems natural
because using "open base as tree" means the user wants to get a kind of
"book/tree" and not really a base. So it makes sense to link base's fate
to tree's one. Moreover, as a Tree window, a Graph window and a Best
Games window, etc. can be opened for each base, more than 30 windows can
be opened related to Trees, so the closing of a Tree window has to clean
up things.
When several Tree windows are opened the top most is refreshed first,
then others.
- Memory leaks fixed (particularly in Game class)
- New API : sc_tree free to release memory used by Tree windows (sc_tree
search). This sould only be used for systems with low memory constraints.
- New API : sc_game truncatefree : when truncating a game, moves are
freed. This sould only be used for systems with low memory constraints.
- New API : sc_info logmem : useful with checkmemlog.tcl script to
detect memory leaks.
- New API : sc_var deletefree : when deleting a variation, moves are
freed. This sould only be used for systems with low memory constraints.
- modified scmerge so it can take an unlimited number of input files
(each separated by a carriage return) (thanks to Marcin Kasperski).
Example usage :
find . -name '*.si3' | sed s/\\.si3// | scmerge newbase -
This is necessary because shell command lines have a size limit.
- Added players' Elo in Score graph title
- removed explicit iso8859 encodings in some language files (french,
italian, nederland, norks, portbr, ...), so that characters are
correctly displayed in Tk widgets (like comment editor).
- added new piece sets to increase max board size (80) (Thanks to Uwe
Klimmek)
- Merida piece sets reworked and added the possibility to use image
files for white and black squares. See wsquare.gif and bsquare.gif in
bitmaps directory (Thanks to Uwe Klimmek)
- added menu entries and shortcuts (F2 and F3) to directly starts
engines (Thanks to Uwe Klimmek)
- increased list limit to 1000 in tourney window
- increased stats window info (Thanks to Uwe Klimmek)
- when annotating a game, the engine's name may contain "-" or "+"
(Rybka for example) which will confuse the parsing of scores inside
comments. So those characters are now replaced with spaces in comments,
and the score graph window will correctly display info.
- added an option in the score graph window : if the scores are not
related to white's point of view, it is possible to check either "white"
or "black" option to get a correct display (Thanks to Uwe Klimmek)
- updated spelling and rating files : july 2007 (thanks to Franz Nagl)
- directories for books and training bases are configurable (options menu)
- minor fixes

Pascal

On Sat, 03 Nov 2007 14:18:18 +0100, Pascal wrote:

I released Scid 3.6.19 at
http://prolinux.free.fr/scid/


This is confusing, there is no new scid version at

http://scid.sourceforge.net




--

PGP: 0x661AB571

Andreas Schwarz a écrit :
On Sat, 03 Nov 2007 14:18:18 +0100, Pascal wrote:

I released Scid 3.6.19 at
http://prolinux.free.fr/scid/


This is confusing, there is no new scid version at

http://scid.sourceforge.net


Yes, (nearly) everybody agrees with it. Scid has not been updated at
Sourceforge since 2004. This is sad, but pleases some people.

Pascal

On Sun, 04 Nov 2007 18:23:24 +0100, Pascal wrote:

Andreas Schwarz a écrit :
On Sat, 03 Nov 2007 14:18:18 +0100, Pascal wrote:

I released Scid 3.6.19 at
http://prolinux.free.fr/scid/


This is confusing, there is no new scid version at

http://scid.sourceforge.net


Yes, (nearly) everybody agrees with it. Scid has not been updated at
Sourceforge since 2004. This is sad, but pleases some people.

Ok, but if you use the same name, it's not possible to include your
version into the package managment systems (for example, the freebsd
ports structure). Your version collide with the original scid, this
causes some problems.


--

PGP: 0x661AB571

Andreas Schwarz a écrit :
On Sun, 04 Nov 2007 18:23:24 +0100, Pascal wrote:

Andreas Schwarz a écrit :
On Sat, 03 Nov 2007 14:18:18 +0100, Pascal wrote:

I released Scid 3.6.19 at
http://prolinux.free.fr/scid/

This is confusing, there is no new scid version at

http://scid.sourceforge.net

Yes, (nearly) everybody agrees with it. Scid has not been updated at
Sourceforge since 2004. This is sad, but pleases some people.

Ok, but if you use the same name, it's not possible to include your
version into the package managment systems (for example, the freebsd
ports structure). Your version collide with the original scid, this
causes some problems.

That is right. Maybe renaming to Scid2 would ease things ?

Anyway is there any interest in having anywhere the two versions at the
same time ? I do because I need to make some regression tests, but I
doubt any user would need both.

Pascal

Pascal skrev:
I released Scid 3.6.19 at
http://prolinux.free.fr/scid/

This is confusing, there is no new scid version at
http://scid.sourceforge.net

Yes, (nearly) everybody agrees with it. Scid has not been updated at
Sourceforge since 2004. This is sad, but pleases some people.

Ok, but if you use the same name, it's not possible to include your
version into the package managment systems (for example, the freebsd
ports structure). Your version collide with the original scid, this
causes some problems.

Anyway is there any interest in having anywhere the two versions at the
same time ? I do because I need to make some regression tests, but I
doubt any user would need both.

What if Shane starts releasing updates to the original Scid again? Or
for that matter, anybody else picks up the code and says "Hey, I just
released Scid 4.0! Get it at
http://geocities.yahoo.com/therealscid"

Morten Skarstad a écrit :
Pascal skrev:
I released Scid 3.6.19 at
http://prolinux.free.fr/scid/

This is confusing, there is no new scid version at
http://scid.sourceforge.net

Yes, (nearly) everybody agrees with it. Scid has not been updated at
Sourceforge since 2004. This is sad, but pleases some people.

Ok, but if you use the same name, it's not possible to include your
version into the package managment systems (for example, the freebsd
ports structure). Your version collide with the original scid, this
causes some problems.

Anyway is there any interest in having anywhere the two versions at
the same time ? I do because I need to make some regression tests, but
I doubt any user would need both.

What if Shane starts releasing updates to the original Scid again?

This would be great news.

Or
for that matter, anybody else picks up the code and says "Hey, I just
released Scid 4.0! Get it at
http://geocities.yahoo.com/therealscid"

Unfortunately there is nothing behind your link. Do you have some that
works ?

Pascal wrote:

Unfortunately there is nothing behind your link. Do you have some that
works ?

Uhm ... Pascal .... he made it up! It was for the purposes of illustrating
his point.

--
Thomas T. Veldhouse

When the ax entered the forest, the trees said, "The handle is one of us!"
-- Turkish proverb

On Tue, 06 Nov 2007 12:26:02 +0100, Pascal wrote:

Andreas Schwarz a écrit :
On Sun, 04 Nov 2007 18:23:24 +0100, Pascal wrote:

Andreas Schwarz a écrit :
On Sat, 03 Nov 2007 14:18:18 +0100, Pascal wrote:

I released Scid 3.6.19 at
http://prolinux.free.fr/scid/

This is confusing, there is no new scid version at

http://scid.sourceforge.net

Yes, (nearly) everybody agrees with it. Scid has not been updated at
Sourceforge since 2004. This is sad, but pleases some people.

Ok, but if you use the same name, it's not possible to include your
version into the package managment systems (for example, the freebsd
ports structure). Your version collide with the original scid, this
causes some problems.

That is right. Maybe renaming to Scid2 would ease things ?

Maybe this will help, but it's also confusing (it's to close
to the original name).


Anyway is there any interest in having anywhere the two versions at the
same time ? I do because I need to make some regression tests, but I
doubt any user would need both.

This is not the question. A package maintainer can not add your version
without removing the original scid.



--

PGP: 0x661AB571

Andreas Schwarz a écrit :
On Tue, 06 Nov 2007 12:26:02 +0100, Pascal wrote:

Andreas Schwarz a écrit :
On Sun, 04 Nov 2007 18:23:24 +0100, Pascal wrote:

Andreas Schwarz a écrit :
On Sat, 03 Nov 2007 14:18:18 +0100, Pascal wrote:

I released Scid 3.6.19 at
http://prolinux.free.fr/scid/
This is confusing, there is no new scid version at

http://scid.sourceforge.net

Yes, (nearly) everybody agrees with it. Scid has not been updated at
Sourceforge since 2004. This is sad, but pleases some people.
Ok, but if you use the same name, it's not possible to include your
version into the package managment systems (for example, the freebsd
ports structure). Your version collide with the original scid, this
causes some problems.
That is right. Maybe renaming to Scid2 would ease things ?

Maybe this will help, but it's also confusing (it's to close
to the original name).

It is hard to use a really different name without making silly things
(massive renaming of "Scid" tokens to XYZ in all files, source files,
help files, etc.), with stricly no added value. This would also add
confusion, if someone wants to continue development of original Scid one
day.

Anyway is there any interest in having anywhere the two versions at the
same time ? I do because I need to make some regression tests, but I
doubt any user would need both.

This is not the question. A package maintainer can not add your version
without removing the original scid.

So why not renaming it to Scid2 ? This would allow the use of both
binaries, but then there will be a problem with user's configuration
files.... One could think that if an engine is configured in Scid, it
should also appear in Scid2 (this is just one of the problem that arises).
That's not so easy. And from my own point of view (an user's point of
view) this is a work that is a bit useless. But if someone wants to take
the code of "Scid2" and tweak it to make it compatible with the original
Scid, he can of course do that.

Pascal