On 01/16/2011 11:31 AM, Gerd Lorscheid wrote:

Hi!

> so things become clearer. Alexander and Steven are multi-window user and
> Joost and me are single window user. Steven wants to connect the switcher to
> the game list. For me as single window user it is connected anyway.
> But there is a problem for multi. The switcher is also related to the main
> window as the current game does switch with the actual database. And with
> the changes I planning the game list is no longer dependent on the switcher.
> Last point is that multi window users like Alexander don't use the game list
> window in favor of the browser as stated below. Steven, you should think
> twice.

I admit I can not follow entirely why you see a difference between 
having muliple windows and multiple tabs in the logic of a program.

> Filtering on the tree data. In my private code I have a hack. If the
> database is larger than 100.000 games it creates a statistic only on those
> games with rating>  2300.

Though I understand the filerting as such, I usually do this by having 
StatBase and RefBase. The latter is the really big thing. StatBase is 
much smaller, cleaned of dupes in the sense that every game that has the 
same moves is a dupe regardless of metadata. (Not much sense in counting 
a move twice if the games are identical. Try to drop GM draws etc. 
here.) The reason for RefBase to exist is actually that it may very well 
contain real dupes, e.g. if I have by some chance the same game several 
times annotated by different persons you'll find it in RefBase, but not 
in StatBase.

Also StatBase uses a bit a softer limit as you suggest. I usually 
generate it from time to time by copy RefBase, dedupe it like mentioned 
and then drop games where both oppoents are below $threshold or if one 
opponent meets the $threshold but the other is far below. (E.g. with a 
2400 threshold +-200: 2400:2400 is included as well as 2400:2300 while 
2400:1800 is not.)

A very nice side effect of this cleansing is that StatBase is pretty fast.

> A good question is how a clean implementation could look like. Again the
> search filter of the database should not be misused for this as it has its
> own useful purpose. One possibility could be a minimum rating field in the
> tree window or just a flag with a hardcoded limit or the possibility to set
> a full or some attributes of the header mask... I am open to alternatives
> here.

Hard coded limits do not work that well, I think. I'm also not sure if 
it's entirely easy to do it "all on the fly" or if it's not a better 
approach to reduce a large refbase to a statbase in the sense mentioned 
above by more automatised means as I do it now. (But in my slow world, I 
admit that I do it only once a year, so I never worked on implementing 
any code for this.)

cu
Alexander

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to