Hi!

>> 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 :)
> 
> Beware that Mask format is evolving, and I will not handle
> backward compatibility before final release. So expect to
> lose your work each time I commit to CVS.

Sure.

> Maybe you'd better export your Sor repertoire to game(s)
> so you can always re-import this to a Mask.

Unfortunately we'll not see any problems in the interactive
input then ;)

>> Also of some interest (IMHO) is "how do I came here? and
>> what would be alternative lines to arrive at this
>> position?"
> 
> The idea is that it is the position that is important,
> more than the moves.

Yes. I also agree with that approach. The point mentioned is
mostly of interest when you interactively enter some lines
to reach a certain position. Here you may go back and add a
variation.

> This is why I prefer this approach compared to Repertoire
> or Opening games/base : it handles transpositions
> transparently, and it helps to switch from "sequence of
> moves memorization" to "get the idea behind a position".

Perfectly agree. From what I currently see its a pretty cool
tool.

>> 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...
> 
> This is why I just added the same symbols as in Repertoire
> editor "Exclude line" "Include Line" to the Mask (not in
> CVS yet).

Ah. I see, especially why I was not able to see ;)

>> 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.
> 
> I  would like to avoid user defined parameters, to keep
> things simple.

Your approach to "keep things simple" by hardcoding
everything is IMHO the contrary of userfriendliness. Its
this M$-approach to software: "WE at Redmont know what you
want to do and if you want to do it differently, YOU are
wrong." Why not allow for parameters and just set sensible
defaults? No one has to check all parameters before using
the software. E.g. I never checkt your NAG assignemnts nor
changed them, but if I feel necessary to do so I'd not have
to hack the source.

Even if you do not want to add a GUI for the parameters you
consider "very advanced", put them into a config file. This,
very advanced user who wishes to alter them may alter by
hand there. This is still much better than searching through
the source and recompile it. No offense, but I just doubt
that you can forsee every idea someone out there may have to
(re-/miss-) use your functions. Therefore I'd always keep
things as open as possible.

For the example in question: if you set the ELO level to
display in green or red to a hard value suitable for the
theoretical lines in the top level this may just not be
suitable on club level, so you implemented pretty good
highlighting but most users probably never see it or at
least can not profit form it as they play a usual "club
level opening system" instead of the latest theory. And if
you adopt it to average club level (whatever this may be)
maybe GM xyz has the inverse problem.

-- 

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

Reply via email to