Recently, I have commented this question with a friend who is a great
programmer. We check the code and he suggested me that the best way to store
timestamp data should start from the PGN files, and then create the
appropiate methods to register in SCID classes to handle/parse the way that
is going to be shown inside the aplication.
I am disgusted with this idea, because it will be stored in the game
comments and then needs to be parsed first then converted into a datetime
format in order to manipulate it inside SCID. My idea is (internally on
SCID) to store the timestamp in the database as a datetime field, apart from
the comment field, and eventually from there create/handle the PGN format.
We revised the moveT's struct written on "game.h":
*struct moveT
{
simpleMoveT moveData; // piece moving, target square etc
char san[10]; // SAN representation of move
char * comment;
moveT * prev;
moveT * next;
moveT * varChild;
moveT * varParent;
markerT marker; // can be NO_MARKER, START_MARKER or END_MARKER
byte numVariations;
byte nagCount;
byte nags[MAX_NAGS];
};*
A quick example could be to store the time as a datetime field inside this
structure:
*struct moveT
{
simpleMoveT moveData; // piece moving, target square etc
char san[10]; // SAN representation of move
char * comment;
moveT * prev;
moveT * next;
moveT * varChild;
moveT * varParent;
markerT marker; // can be NO_MARKER, START_MARKER or END_MARKER
date timestamp;
byte numVariations;
byte nagCount;
byte nags[MAX_NAGS];
};*
2011/9/2 Marcin Kasperski <marcin.kasper...@mekk.waw.pl>
> > I like the ICC format, just a comment with the remaining time ( h:mm:ss )
> > For example:
> >
> > 1. e4 {1:40:30} c6 {1:40:25} 2. d4 {1:40:02} d5 {1:40:50}
>
> The problem here starts once you also have some true annotations.
> I don't really like
> 1. e4 {1:40:30 Most popular opening move}
> or
> 1. e4 {Most popular opening move 1:40:30}
>
> Enhanced PGN Spec (
> http://www.enpassant.dk/chess/palview/enhancedpgn.htm )
> proposes somewhat better syntax with [% ...] markers.
> For example:
>
> 27. Kg1 Qxg3+ {[%clk 0:00:07][%eval -6.05] White is toast}
>
> (clk means current clock, eval engine eval, there is also emt - time
> spent on the move and some others)
>
> The problem with this syntax is that some javascript viewers break on
> it, but in general I like the idea.
>
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Scid-users mailing list
> Scid-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scid-users
>
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
