I had some experience with xml and java package for parsing it, but I do not understand why you need another (a part of .pgn. , .sci., cbh, .si4) format.
Il Martedì 25 Marzo 2014 18:10, "scidb-users-requ...@lists.sourceforge.net" <scidb-users-requ...@lists.sourceforge.net> ha scritto: Send Scidb-users mailing list submissions to scidb-users@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/scidb-users or, via email, send a message with subject or body 'help' to scidb-users-requ...@lists.sourceforge.net You can reach the person managing the list at scidb-users-ow...@lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of Scidb-users digest..." Today's Topics: 1. Re: Scidb-users Digest, Vol 20, Issue 1 (Pietro) 2. Re: Schedule of development (Gregor Cramer) 3. Alternative to PGN (Gregor Cramer) 4. Re: Alternative to PGN (Drew Ferguson) ---------------------------------------------------------------------- Message: 1 Date: Fri, 21 Mar 2014 21:25:21 +0000 (GMT) From: Pietro <ilcecchino2...@yahoo.it> Subject: Re: [Scidb-users] Scidb-users Digest, Vol 20, Issue 1 To: "scidb-users@lists.sourceforge.net" <scidb-users@lists.sourceforge.net> Message-ID: <1395437121.70250.yahoomail...@web28902.mail.ir2.yahoo.com> Content-Type: text/plain; charset="iso-8859-1" Nice schedule! My opinion: 9, 10, 11, 14, 18, 19 and 21 are not of primary importance (almost 7 months in your estimate). Also 22 is not so necessary :) Is ticket #33 definitely up to Jessy? Bye Message: 1 Date: Wed, 19 Mar 2014 18:55:46 +0100 From: "Gregor Cramer" <rema...@gmx.net> Subject: [Scidb-users] Schedule of development To: scidb-users@lists.sourceforge.net Message-ID: ??? <trinity-e387000b-3c0a-49dd-a71a-d1702fef198f-1395251745889@3capp-gmx-bs30> ??? Content-Type: text/plain; charset=UTF-8 A rough overview about the development schedule, and the estimated time how long implementation and testing will still take. Please note that below are only the primary functions, there are still more secondary functions. And please consider that it is hard to estimate the development time, the real development time may differ significantly (in both directions). 1. New database format, allowing faster search, supports ? opening classification, smaller index file, less memory ? consumption, and eventually smaller game files, ? currently in test phase (hopefully successful, this is ? all based on a transposition-invariant classification ? key, completely different from Scid's technology, and I ? had to overwork the emulation of Scid databases). 2. Game links, already implemented, not yet tested, ? about 2 weeks. 3. Opening classification tab (already partly implemented), ? this includes the overwork of the ECO list, the current ? list is not integrally closed, about 1 month. 4. Flexible window layout, about 3 months. 5. Multiple selection in game lists (required for ? filter functions), about 2 weeks. 6. Search and filter functions, based on CQL, about ? 6 months (already partly implemented). 7. Support of opening books (.ctg and .bin), about 1 month ? (already partly implemented). 8. Tablebase/endgame support, about 1 month (already partly ? implemented). 9. HTML export, about 2 months. 10. LaTeX export, about 1 month. 11. PDF export, about 1 month. 12. Keyboard input of games, about 2 weeks. 13. Finishing move information support, about 2 weeks. 14. Internet update of player dictionary, engine dictionary, ? ? and more, about 2 weeks. 15. Finishing the help pages, this will be done concurrently. 16. Loading databases at start-up in background, about 2 weeks. 17. A new tab for database access and displaying information, ? ? about 1 month. 18. Tip-of-the-Day dialog, already implemented, but more ? ? tips have to be written, about 1 week. 19. Spell-correction functions, especially for player names, ? ? event names, and site names, about 1 month. 20. Eliminating duplicated games, about 2 weeks. 21. Finishing and testing the board/piece design dialogs, ? ? about 1 month. 22. Windows version, about 6 months. Some comments which tasks are necessary for the first alpha version? Some primary functions still missing? Please note that the Windows version will not be done until the first alpha version under Linux is released. Furthermore after the release of the Windows version the implementation of Jessy will start. Jessy provides: playing against engines, automatic analysis of chess games, playing on ICS or FICS, and some more functions. Jessy will have a database interface to Scidb, but his own graphical interface. Some more tasks for Scidb, but less priority: 23. Support of Bughouse games. 24. Finishing the support of Crazyhouse, Antichess, and ? ? Three-Check Chess. 25. Optimizing the load of the player base, it's still ? ? a bit time consuming. 26. Accelerating the database and PGN import/export. 27. Support of children's chess. This will allow the input ? ? of invalid moves, like Nc1-c3. 28. Database service API (feature request #35). 29. Time usage diagram (feature request #36). 30. Integrated document viewer (feature request #30). And more... -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 2 Date: Sat, 22 Mar 2014 12:37:51 +0100 From: "Gregor Cramer" <rema...@gmx.net> Subject: Re: [Scidb-users] Schedule of development To: scidb-users@lists.sourceforge.net Message-ID: <trinity-637049c1-fd8b-4949-956c-be5268a42289-1395488271595@3capp-gmx-bs41> Content-Type: text/plain; charset=UTF-8 > My opinion: 9, 10, 11, 14, 18, 19 and 21 are not of > primary importance 9, 10, 11 (export to documents) may come after the first alpha release. 14 (internet update of player data) is nowadays a must, please consider that with the first alpha version the distributors (Debian, Arch Linux, ...) may provide Scidb as a package, and then internet update is the appropriate method to be up-to-date, the player data plays an important role for many users, and in this way Scidb can inform about new updates. 18 (tip of the days) is important for me, the Tip-of- the-Day dialog plays a significant role to point out some features of Scidb. 19 (spellchecker) may come later (good task for a volunteer!). 21 (board/piece design dialogs) may be finished later, but testing and fixing is unavoidable, currently there exists some nasty errors. (Somebody who likes to test?). > Also 22 is not so necessary :) I agree that the Windows version is not important for Linux users, but it is unavoidable, about 80% percent of the chess database users are friends of Windows (I know, a Linux cannot understand this, and I cannot understand this, too). Probably it will take less time to do this, about 90% of the Windows functionality is already implemented, but testing all the stuff is very time consuming. Hopefully I will have some assistance when doing the Windows version. Is ticket #33 definitely up to Jessy? It is not yet finally decided whether Ticket 33 (http://sourceforge.net/p/scidb/feature-requests/33/) is a task for Jessy, but this is not a database specific function, and may become part of Jessy. PS: I've forgotten one feature: a player report. But this may come after the first alpha release. Any suggestions about the content of a player report? PPS: It may happen that a secondary task will be realized earlier than planned. Sometimes I have a good idea how the implement a specific task, and then I'm doing this. This is one my "methods" to be so fast (due to Ohloh Scidb's code took an estimated effort of more than 100 years <http://www.ohloh.net/p/scidb>). Gregor ------------------------------ Message: 3 Date: Tue, 25 Mar 2014 18:04:49 +0100 From: "Gregor Cramer" <rema...@gmx.net> Subject: [Scidb-users] Alternative to PGN To: scidb-users@lists.sourceforge.net Message-ID: <trinity-e8b229de-5a85-4c67-a2d2-c4c6f357b9ff-1395767089856@3capp-gmx-bs01> Content-Type: text/plain; charset=UTF-8 Due to the fact that PGN (http://en.wikipedia.org/wiki/Portable_Game_Notation) is not sufficient for modern chess applications, I'm working on a different format, especially for the backup of unsaved games. I'm in fact not very familiar with XML, so I need some suggestions. My first idea is something like this: --------------------------------------------------------------------- <?xml version="1.0"?> <!-- cif --> <meta charset=utf-8"/> <meta author="Scidb"/> <description lang="en">Only an incomplete example</description> <game variant="normal" startpos="518"> <tag name="Event">At home</tag> <tag name="White">It's me</tag> <tag name="Black">It's my opponent</tag> <moves> 1.e4 e5 2.Nf3 Nc6 3.Bc4 Nf6 4.Ng5 $5 <post lang="en">Due to Tarrasch this is a <b>patzer</b>.</post> <post lang="de">Laut Tarrasch ist dies ein <b>Patzerzug</b>.</post> <arrow from="g5" to="f7"/> 4...Bc5 <marker type="square" color="yellow" to="f2"/> (d5 <post lang="en">This is the usual reply.</post>) 5.Nxf7 Bxf2+ <trailing lang="en">I've abandoned, that's too much for me.</trailing> </moves> </game> --------------------------------------------------------------------- This example is of course not complete. The chess variant and the start position will be given with the <game...> markup, because this is also an information for the parser. <trailing>...</trailing> is a trailing comment, <post>-...</post> is a comment after last move, <arrow ...> defines an arrow, and <marker ...> defines a coloured square. The syntax for comments is a subset of xhtml (this makes it parseable for XML parsers, I think), and may contain UTF-8 characters. But I'm not satisfied with the syntax of the tags like <tag name="Event">At home</tag> probably somebody knows an alternative way. <!-- cif --> is the magic number, and is an abbreviation for "Chess Interchange Format". Gregor ------------------------------ Message: 4 Date: Tue, 25 Mar 2014 17:10:11 +0000 From: Drew Ferguson <d...@afccommercial.co.uk> Subject: Re: [Scidb-users] Alternative to PGN To: scidb-users@lists.sourceforge.net Message-ID: <20140325171011.0e684...@blacktav.fergiesontour.org> Content-Type: text/plain; charset=US-ASCII Hi Gregor I think there already is an XML DTD Whether it will meet your requirements is another thing; I will try and hunt it down On Tue, 25 Mar 2014 18:04:49 +0100 "Gregor Cramer" <rema...@gmx.net> wrote: > Due to the fact that PGN > (http://en.wikipedia.org/wiki/Portable_Game_Notation) is not sufficient > for modern chess applications, I'm working on a different format, > especially for the backup of unsaved games. I'm in fact not very > familiar with XML, so I need some suggestions. My first idea is > something like this: > > --------------------------------------------------------------------- > <?xml version="1.0"?> > <!-- cif --> > > <meta charset=utf-8"/> > <meta author="Scidb"/> > > <description lang="en">Only an incomplete example</description> > > <game variant="normal" startpos="518"> > <tag name="Event">At home</tag> > <tag name="White">It's me</tag> > <tag name="Black">It's my opponent</tag> > > <moves> > 1.e4 e5 2.Nf3 Nc6 3.Bc4 Nf6 4.Ng5 $5 > <post lang="en">Due to Tarrasch this is a <b>patzer</b>.</post> > <post lang="de">Laut Tarrasch ist dies ein > <b>Patzerzug</b>.</post> <arrow from="g5" to="f7"/> > 4...Bc5 > <marker type="square" color="yellow" to="f2"/> > (d5 <post lang="en">This is the usual reply.</post>) > 5.Nxf7 Bxf2+ > <trailing lang="en">I've abandoned, that's too much for > me.</trailing> </moves> > </game> > --------------------------------------------------------------------- > > This example is of course not complete. > > The chess variant and the start position will be > given with the <game...> markup, because this is also > an information for the parser. > <trailing>...</trailing> is a trailing comment, > <post>-...</post> is a comment after last move, > <arrow ...> defines an arrow, and > <marker ...> defines a coloured square. > The syntax for comments is a subset of xhtml (this > makes it parseable for XML parsers, I think), and may > contain UTF-8 characters. But I'm not satisfied with > the syntax of the tags like > <tag name="Event">At home</tag> > probably somebody knows an alternative way. > > <!-- cif --> is the magic number, and is an abbreviation > for "Chess Interchange Format". > > Gregor > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and > their applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > Scidb-users mailing list > Scidb-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/scidb-users -- Drew Ferguson AFC Commercial http://www.afccommercial.co.uk ------------------------------ ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ------------------------------ _______________________________________________ Scidb-users mailing list Scidb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scidb-users End of Scidb-users Digest, Vol 20, Issue 2 ******************************************
