Hi!
>>> I reworked Mask view
>> Looks very promising promising, indeed! :)
>>
> Hope you appreciated the speed up : 10000 % ! Note that
> Mask info menu gives stats on hashes that will be removed
> later.
Actually, as I'm about to add lines manually I did not have
the chance to really feel it, but I already fastened the
seat belts :)
>> Just stumbled accross () in commentary. This throws an
>> exception.
>
> Strange, I tried by importing a game with a fake "()" and added manually
> "trial [] ..() .. {} .." without problem (even if I thought [] would
> lead to problems, but it works). So could you send me a file or a
> procedure to reproduce it ?
Ok, I'll try again. Procedure? Well I just clicked through
the tree, added the line to the tree, RMB -> Add commentary.
So, nothing special.
> So far I imported 5000 positions in a Mask file with vars, comments,
> evaluations without any problem.
I did not import it from some file. So the () was passed
along from the text widget. My immediate idea was "some
problem with escaping a special char"?
>> Additionally, could it be that there're some \n written to
>> the stm file that are not intended.
>>
> No, I don't think so. "\n" are appended by the user when
> entering multi-line comments
Yes, there it happens as well. I just had a look at the new
format and saw many \n's there. It was almost readable ;)
And in my first trials I did not yet add my epic commentary.
> (you noticed entry box has changed).
Yes. Very nice! (Be sure, otherwise I'd have complained
again ;)
> On the Tree window only the first line is displayed, but
> associated tooltip displays the complete comment.
Noticed that as well. :) Maybe it is a good idea to have the
colour label also as an active area for the tooltip to
display. The window can then be taller. (Thinking especially
about people with small displays and huge fonts.)
>> Adding a marker should probably add the line to the mask
>> automatically. (Makes sense to me, but maybe I miss an
>> occasion where it shouldn't?)
>
> For safety I preferred to use a 2 phases process : first add move to
> Mask, then add markers /comments to it. This avoids the case where you
> want to flag in green e4 but you miss the line and add by error the move
> just below (but anyway this kind of error may always happen).
Ic.
>> To play arround I would enter my current sor-file. But just
>> that I do not do it twice: how is it inteded to use
>> concerning white/black openings?
>
> This is the same logic for maintaining distinct white and black
> repertoires : when you review your openings, you do it for one side, and
> certainly for some specific lines. So maybe it is clearer for the user
> to separate things. Moreover things are not symmetric : you may like
> playing the French defense with Black but strictly avoid it with White.
> Hence the 2 repertoires.
Sure. That brought me to the difficulty how to distinguish
the white and black repertoir if I have it in one file. I'd
need two greens and two reds and so on.
>> Do you think they should both go into one file, or
>> should I rather split them? If the latter is probably
>> cummulative loading of mask files intended so I could
>> first load the white lines and then the black ones
>> and have both in the tree?
>
> It is really easy to merge Masks, but current code does
> not allow it (data is reseted when opening a Mask). I
> would prefer to avoid it, to keep things simple and not
> confuse users.
>
> Now the main question : are there markers, flags or
> anything that should be added ?
To know that one surely has to play arround with the stuff
in more detail.
One main thing I thought about while adding lines yestereve
was "hm, where's the back button". Just as I've to add the
commentary one layer upwards to the line.
Also of some interest (IMHO) is "how do I came here? and
what would be alternative lines to arrive at this position?"
Probably: how many alternative ways result in this postion
is a usefull number. Mabe even from a given starting point.
Say you start out e4 e6 d4 d5 and then you want to reach a
a certain position but avoid line A as this can lead to an
alternative you're not comfortable with. In the french you
can e.g. use the Steinitz for cutting theory a bit shorter.
Stuff like that. And as the new way to handle a repertoir is
much more friedly to transpostion handling...
> So far it seems there are enough info, but maybe it would
> also be interesting to display score in various colors.
> For example : if Average Elo is > 2200 and number of games
> >20 and Score > 55%, put it in green if Average Elo is >
> 2200 and number of games > 20 and Score < 45%, put it in
> red
I could imagine this usefull if you can define the levels
eg. Some sort of: well, I do not play Kasparov, Topalov and
Anand tomorrow, the average level in the Club is about ...
what are the usual lines of play there. Depending on the
level of your opponent one experiences very interesting
handlings of ones own openings.
Maybe one would want to correlate such info also with the
players actual rating. The latter could result from either
manual input or from the friend mode games I recently
suggested. (Or both of course.)
--
Kind regards,
Alexander Wagner
Universitaetsbibliothek Ilmenau
Langewiesener Str. 37
98693 Ilmenau
Tel.: 03677/69-4521 , Fax.: 03677/69-4617
-------------------------------------------------------------------------
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
