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...
