scidvspc-users

Re: [Scidvspc-users] July news

[<fb...@li...>]

<quote>
Mainline SCID git allows different column arrangements for each open base [and multiple gamelists/switchers - way too confusing] but this doesnt work imho.So , added to the fact that the tk widget we use (tktreeview) doesnt really support column rearrangement, and any implementation is a hack, i might just pass on rearranging columns for the immediate future.


I should also mention, recent Scid git versions have been messing  with the databse backend and (specifically) name frequencies. It's probably best not to use Scid git for major database work without backing up your databases, as name corruption is possible, and there is also a lot of untested code.</quote>
This is simply not true.
 I would appreciate it if you stopped spitting venom on Scid (from which you copied most of the code).
 With regard to gamelist column arrangement, does not appear so complicated to me: in each gamelist windows you can change the order with a simple drag and drop.
Fulvio










 

Re: [Scidvspc-users] July news

[Steve A <ste...@gm...>]

Steven wrote
> > I should also mention, recent Scid git versions have been messing  with
the databse backend and (specifically) name frequencies. It's probably best
not to use Scid git for major database work without backing up your
databases, as name corruption is possible, and there is also a lot of
untested code.

Fulvio wrote
> This is simply not true.

Sorry Fulvio, but it is true. You are writing some interesting code, but
Gregor has shown you that recent changes you have made to the name
frequency calculation make it *possible* to break database names if a base
is worked on in Scid git, then reloaded in Scid 4.3 4.5 or Scid vs PC.

Steven

[Scidvspc-users] Re: July news

[Gregor C. <re...@gm...>]

Steven wrote:
> I should also mention, recent Scid git versions have been messing  with
> the databse backend and (specifically) name frequencies. It's probably best
> not to use Scid git for major database work without backing up your
> databases, as name corruption is possible, ...

Fulvio wrote:
> This is simply not true.

Steve's message is true, name corruption is possible, and namebase compaction
is not working as expected. The latest git version is writing namebases not 
conform to the .si4 format. There is a way to fix such a database written with 
latest git version, use

  scidt -N <database>

and the new namebase will be in .si4 format again. It's probably a good
idea to make a backup before fixing the database.

Fulvio wrote:
> Since your contribution to the Scid project is negative (not only there are 
> no lines of code written by you, but you even harm the project by spreading 
> false news) I invited you to leave the Scid project.

I cannot understand this, he is definitively not harming the project. I wrote 
you a message about the problems with the namebase proven by two
examples (also confirmed in tests) many weeks ago, and in a reply you've
agreed with my analysis.

Gregor

Re: [Scidvspc-users] July news

[Alan W. <a.c...@gm...>]

It is sad that exchanges like these have to be so prevalent. Steve has 
tried to help out only to be met with much vitriol.


On 07/05/2014 09:02 AM, Gregor Cramer wrote:
> Steven wrote:
>> I should also mention, recent Scid git versions have been messing  with
>> the databse backend and (specifically) name frequencies. It's probably best
>> not to use Scid git for major database work without backing up your
>> databases, as name corruption is possible, ...
> Fulvio wrote:
>> This is simply not true.
> Steve's message is true, name corruption is possible, and namebase compaction
> is not working as expected. The latest git version is writing namebases not
> conform to the .si4 format. There is a way to fix such a database written with
> latest git version, use
>
>    scidt -N <database>
>
> and the new namebase will be in .si4 format again. It's probably a good
> idea to make a backup before fixing the database.
>
> Fulvio wrote:
>> Since your contribution to the Scid project is negative (not only there are
>> no lines of code written by you, but you even harm the project by spreading
>> false news) I invited you to leave the Scid project.
> I cannot understand this, he is definitively not harming the project. I wrote
> you a message about the problems with the namebase proven by two
> examples (also confirmed in tests) many weeks ago, and in a reply you've
> agreed with my analysis.
>
> Gregor
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Scidvspc-users mailing list
> Sci...@li...
> https://lists.sourceforge.net/lists/listinfo/scidvspc-users
>

Re: [Scidvspc-users] July news

[Steve A <ste...@gm...>]

> the background of the game and move list is grey although I switched it to white,

Ok - i think i have a robust solution for background colours now (pic attached).
It is in svn, and i'll hopefully put a windows beta up in the next few weeks.

S.

Re: [Scidvspc-users] July news

[<gre...@gm...>]

Thank you Steve, although it's just a minor issue it's much appreciated.

Andreas


> > the background of the game and move list is grey although I switched it to white,
> 
> Ok - i think i have a robust solution for background colours now (pic attached).
> It is in svn, and i'll hopefully put a windows beta up in the next few weeks.
> 
> S.
> 

Re: [Scidvspc-users] July news

[<fb...@li...>]

>
>I cannot understand this, he is definitively not harming the project. I 
wrote 
>you a message about the problems with the namebase proven by two
>examples (also confirmed in tests) many weeks ago, and in a reply you've
>agreed with my analysis.
>
>Gregor
>

Are you referring to quick hack that i wrote in this commit?
http://sourceforge.
net/p/scid/code/ci/9274b0b6999061dd0abdd50a4499a28982d453b5/

As I told you by e-mail I did not wanted to upgrade Scid to version 5 and in 
fact the hack was removed in subsequent commit:
http://sourceforge.
net/p/scid/code/ci/3494477a503abdc7c092cce0ac356cadaa2836e5/


I'm not a native english speaker, but this two senteces are simply false:
"Mainline SCID git allows different column arrangements for each open base 
[and multiple gamelists/switchers - way too confusing]"
Drag and drop cannot be considered "way too confusing"

"I should also mention, recent Scid git versions have been messing  with the 
databse backend and (specifically) name frequencies. It's probably best not
to use Scid git for major database work without backing up your databases, as 
name corruption is possible, and there is also a lot of untested code."
I've not messed with anything, nor commited untested code and the latest git 
code does not cause name corruption.

Fulvio