2008/8/17 Alexander Wagner <[EMAIL PROTECTED]>
>
> Hi!
>
> All Tree data are visible. I commited in CVS a first draft, you can try it
>> (just define a new mask, then right click on moves).
>> [...]
>>
>
> This looks very nice already! :) Just some immediate
> observations.
>
> - Move comment:
>
> Probably it would be better to have it in a tooltip for
> the color marker as it gets lost a bit at the end fo the
> line. Maybe even a tooltip is not the correct thing but a
> small part of the window that gets set aside. The comment
> could e.g. show up if the mouse hovers over the line.
This was my first idea, but it is not good.
>
>
> Also it is well possible that one wants to add a bit
> more prosa there, so considering multiple lines would be
> nice. Think of a short discussion of the main features of
> the resulting game. Surely e.g. a French Winawer has a
> very different layout than the Classical and you'd want to
> drop a note about Bb4 here.
>
Again, I also thought about that, but UI would get overcrowded.
>
> - Move Nags:
>
> I miss a flag that says: "do not play". This is differen
> from "??" as it could even be a strong line, but one that
> leads to positions one does not like, ie. lines one wants
> to exclude from ones own repertoir but that are not weak.
>
> In the above example someone who plays the Winawer only
> would surely want to exclude the Classical. Ok, marking
> Bb4 with !! sounds a bit strange, but Nf6 with ??, well I
> don't know ;)
Exclude -> use a red marker.
>
>
> - Colour codes
>
> One might want to allow userdefinde labels, but I guess
> this is already in your set of ideas.
>
Yes, but I decided to simplify things where user data must go in annotation
area, and only there.
>
> - Comment position
>
> I'm a bit confused by this menue popping up in the context
> menue of the move line. Actually one is commenting the
> position _before_ this move is entered, so it should more
> likely be in the Mask menue, or just an MLE where the
> current comment shows up that can be edited.
It is the best place for me : everything in the popup menu. Mask menu is for
file management, not data.
> Here also it
> might very well be that one would want to add some sort of
> discussion concerning the position at hand, I think a
> oneliner is probably a bit short. Think of a short
> discussion of the position at hand, say general strategy,
> weak points, strong points and so on.
>
Why not ? Anyway that's pretty to change later, file being compatible.
>
> - stm-Files
>
> Though it is clearly not the intention, do you see a
> possibility to have an easier text format for the
> stm-files? (BTW: my mime-base tells me .stm to be some
> audio file.) The current one is surely very nice for tcl
> to read in, but I admit that I sometimes like to set up
> such stuff by hand, especially if I want to do this
> outside of scid, e.g. if I've already some data at hand or
> if I just want to correct a typo that appears throughout
> the file.
Let the user write by hand such file is unmaintainable (for the user
himself). Such file should contain thousands of moves. The format used is
the best : to load a Mask is just one line of code "source file.msk".
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
