Marcin Kasperski a écrit : >>> It would be nice to have sth like File/Open Tree or >>> File/Open as Tree, what would do just the same - open >>> selected database, open it's tree, and lock it - while >>> keeping the currently loaded game active. >>> >> You are right, and also that seems pretty easy to do >> (...) >> > > (keeping fingers crossed ;-)) > > >> Another suggestion you may find useful : I added a book >> window, so if you really have a favorite reference DB, why not >> generate a book with polyglot from it so you will get a very >> quick navigation (no calculation when moving). (...) >> > > Well, this suggestion finally motivated me to patch your scid so > it is able to access the book even if it is not under the > directory where main binary lies (if you are interested in > patch, let me know, I would need to polish it a little bit, > it extends my old patch significantly and keep windows > convention as it is). > Yes, I hard coded book paths which is not good. If you have a patch, I am interested. I think it could be good to have the choice between for example 4 directories for books' path (exactly like the EGTB dialog box), and save it. > And ... yes and no. Book window may be valuable reference > for early moves, but later on it is not that useful. It does not > offer any statistics (who played such move and with which > result), and - what is more important - it does not offer any > method to navigate to the games where the quoted moves > were played. > > So I would rather stick with the tree... > > >> But when I added the book window feature, I thought that would >> make useless the need for multiple trees, don't you think ? >> > > Well, see above. The book window would be great for the opening > study/analysis purposes if: > - it offered wider, tree-like stats > - it offered direct navigation to the top matching games > > >> Tree is slow : Yes ! this is where the books come into action >> : fast, lightweight and efficient ! >> > > Well, I think I will stop repeating myself. Maybe I will add one > more note: ChessAssistant uses something a bit similar to the > book - precomputed, quickly displayed information about the > moves played in selected positions. But it keeps far more info > there (well, more or less all what scid tree window has). > > In fact, I think that maybe the best of all worlds would be to > use some book-building-like-technique to build index(es) for the > tree, so they work as fast as the book ;-) > > There is already some cache for the tree window, and despite not being as fast as books, I find the Tree window faster in Scid than its equivalent in Chessbase. I agree with you that books are not as pleasant as the Tree window. At least I tried to point out a workaround. Don't tell anybody, but I never use the book : only the Tree window ...
I will see what I can do about multiple Tree support and others, but as I told you Scid Pocket eats all my time now (and it supports *both* Tree and Book display, at once in the same window). Pascal ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
