2008/11/10 Alexander Wagner <[EMAIL PROTECTED]>

> Pascal Georges wrote:
>
> Hi!
>
>     - Screen Update: while Scid worked through the base it
>>    updated the main/pgn/tree window for each single move.
>>    This results in quite a heavy CPU usuage, and I think
>>    screen update is not necessary here at all.
>>    Additionally, I'd guess that most of the time the
>>    process takes is actually wasted for screen updates.
>>
>>
>> Given that the migration from a base to a mask is a
>> process that occurs only once for all, I don't see any
>> real problem here (once the mask is there, it becomes the
>> data to work with, the base becoming obsolete).  And if
>> Scid's state is not updated, there can be sometimes weird
>> behaviors.
>>
>
> Hm, well this will require the opening trainer to work with
> masks instead of bases as well. Do you plan this for the
> near future? Otherwise there's some need to convert between
> both.


Yes, it is on the TODO list : opening trainer is now obsolete for me (that
is for my own usage). But I don't know yet what to do with the training
option available in the Tree window. It seems sufficient like that for me :
adding functions (like stats, popping a message when the user chose a move
that is not in the Mask or flagged with a "?") does not mean the user gets a
better training tool.

So at first sight, the removal of "opening trainer" is pending. Any
objections ?
I may inhibit the menu entry in next release and see if there is any
protestation.

[...]


>
>
>       IMHO it would be better if the status window shows
>>      overall status, but if it shows the status for each
>>      game it must at least not pop to front and gain
>>      focus.
>>
>> This is a side effect of code factorisation. Not a big
>> problem for me.
>>
>
> I don't get you. Maybe a missunderstanding. Currently, the
> status window pops to front at every game that gets filled
> into the mask. It took about half an hour here and while
> that happend I was absolutely unable to do anything else on
> the system. Ok, I can switch to the console with
> ctrl-alt-f1, but within X this window poping to front every
> other second makes it impossible to do anything as you'll
> loose the focus all the time. (I've no idea what that has to
> do with code factorisation, however.)
>

When filling the Mask with a base, you have a progression bar popping for
every game, and a "cancel" button : I checked that and it works. But maybe
you got a race problem : if the base contains 1000 games with 2 moves each,
the dialog will pop up 1000 times for 0.1 sec, then you will not have time
to press the cancel button and the flickering box is certainly annoying in
this extreme case. This certainly needs polishing but I insist about the
fact that this import is a migration process that should be used once for
all.


>
>
>     - Commentaries within the mask: I've no idea how a repertoir
>>
> [...]
>
>>      8.Nxd4 Bc5" would be nice, not?)
>>
>>
>> I don't understand how you intend to use the Mask feature.
>>
>
> Well, I try to use the repertoir functionalities the way I
> understood you invented them. ;)
>

Well I don't understand your remark given that you seem to have made Mask's
help clearer ;-)
The idea is that the Tree window (with masks) has everything : all
information related to openings (except what belongs to the Book window).
The user should not need to use Repertoire editor nor any Opening base (as I
used to have).


>
>
>  It became for me a complete replacement to the repertoire
>> editor and to any opening base.
>>
>
> This is nice but if I want to use your opening training
> function as well this requires me to set up a base, isn't
> it? Or is that also handled differently?
>

You are right, there is some inconsistency here. But the real question is :
does anybody really use the opening trainer ?
Isn't the Training facility in Tree window better ? Don't you think I should
remove the Opening trainer ?


>
>
>  I migrated myself and now I only use the Tree window with
>> a reference database and two masks : one for White, and
>> one for black.  That way I have everything gathered in the
>> same place : evaluation of moves, comments on positions,
>> best games, stats, etc. Even the opening trainer is
>> obsolete (maybe some additions could be done to the Tree
>> training feature, like the stats of success/failure).
>>
>
> Could you give me (us) some enlighteing
> commentary/documentation of this? Does this mean that the
> opening trainer should get removed? What's the general
> direction here?
>

See above. I'd vote for an inhibition of the menu entry, just to get
reactions. And if anybody is attached to the Opening trainer, I'd like to
know why and I'd try to migrate the missing functionality to the Tree's
trainer.

[...]


    - Wouldn't it make sense to have position evaluations
>      similar to NAG? E.g. a column that shows "+=" as well?
>
> This would go to position comment : the text entry is free
> so I don't feel the need to have a separate field. The
> user can manually add any value along with position's
> comment. For moves, it is another thing, because NAG value
> can be used later for training.
>

Could you probably enlighten me with some short howto,
> please?


I don't get where it is not clear : could you precise ?


>
>
> I admit, I'm absolutely confused. As far as I got it till
> now, the idea is to have a base for the opening trainer and
> I can then fill that one into the mask. Therefore, I created
> such a base where I added the lines required and filled them
> in. I thought I was working right to the book...  Should I
> just forget about the base entirely and fill in all my
> repertoir into the mask only?


Yes, forget everything except the Mask : don't you find it clearer and
easier to use ? When entering moves in a base, how do you handle
transpositions ? There is no such problem with Tree + Mask.


> Should the current opening
> trainer be droped?


Yes.


> Is its entire functionality mapped into
> the tree?


No, not really. But I personally miss nothing.


> How would I add a "trap" to the mask, ie a ?? move
> that is not played ever but worth knowing and should be
> remarked for the learner?


Imagine a move in a position deserves a ??. If it is not present in any game
in the reference base, it will never pop up when using the training function
of the Tree window. More generally, the problem is that you can't add a move
in the Mask that is not played in the reference base (note that if a move
already exists in the Mask and not present in the Tree it will be displayed
at the bottom of the Tree). I don't know if this is desirable or not, but it
is a case where an opening base still makes sense. But is it worth to care
about a move that was never played in your 3M games database ?
So what to do ? For me the merging of information is still pertinent (that
is Tree + Mask).

Pascal
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to