2008/7/18 Alexander Wagner <[EMAIL PROTECTED]>:
>
>
> Pascal Georges wrote:
>
> Hi!
>
> set tree(standardLines) {
>> {}
>> {1.c4}
>> {1.c4 c5}
>> {1.c4 c5 2.Nf3}
>> }
>>
>>
>> Why not simply use a PGN file or a base containing lines (in a single
>> game as variants or in several games) for that ? Then the UI is already
>> there and maintenance is easier for the user. I already added some menu
>> entries in the Tree window for that.
>>
>
> I just had it that way already and I admit I do not like such stuff
> hardcoded. But I've also no problem to remove the 3 lines of code that read
> it in from a file.
>
Hi,
I'd prefer to keep things simple and avoid those shortcuts. Look at Scid's
initialisation at startup : it is already quite a big plate of spaghetti
code, and I sometimes have trouble finding my way through it. If you make
the assumption that users (or even power users) can edit files containing
Tcl code in ~/.scid directory (that is without UI to help and check), I am
afraid this will lead quickly to problems.
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
