Files
katrain-qt/TODO
T
2020-04-29 19:07:52 +02:00

46 lines
4.0 KiB
Plaintext

[x] Player button to black/white with AI style spinner
[x Non square boards
[x] remove fast -> in settings?
[x] Polish graph
[x] BoxLayout padding/spacing use instead of fiddling?
[x] P:noise pass not noisy
[x] graph wonky on branch switch -> check in children &c.
[x] Scrolling add a move on the board instead of navigating through the game. This was already the case in the 0.9 version and it's quite annoying as scrolling seemed only natural and I kept forgetting not to do it :p
[x] show PV on hint hover? Although Katrain wasn't meant to be like Lizzie to begin with, it would be really neat if we could visualize the expected variations when hovering over the top moves.
[x] Self-play tournaments in separate script.
[x] ai thoughts in sgf
[x] more AI modes?
[x] pol value override > 0.95 ? policy threshold override P:pick?
[x] config player to sep. row/popups?
[x] dots: teacher settings fixes
[x] ogs bot connector
[x] clarify score change vs score
[x] List edit settings/object edit settings? -> Mostly superseded by popups.
[x] box to label ? split in status and comment?
[x] Currently, when saving an SGF after analyzing a game, Katrain stores data for every move by default. Like for dots, it would be great if it was possible to only store data for moves that we were interested in (e.g. only from this or that player, and/or only the most inefficient moves/most costly mistakes, etc.)
[x] Typing something in the comments window freezes Katrain -> probably keyboard shortcuts / solved by label
[x] In the 0.9 version I could hide dots from one player, which was handy to focus on my own mistakes when reviewing games, not my opponent's. For what I saw, we can't do that in the 1.0 version anymore, which is a shame IMO.
[x] Since dots help to discriminate between mistakes, it would be nice to be able to show only those that are big enough to worry about: for example showing only non-green dots, or showing only orange and red dots, or even only red dots, since strong and weak players will have different needs. In my case, when I was reviewing games (my own or classical Japanese ones) with the 0.9 version of Katrain, I would typically focus on moves that would be rated less than 80% efficient (ranging from orange to red, if I remember correctly). A slider going from 0 to 100% to show moves according to their efficiency would be handy, I think. Just an idea ^_^
[x] engine status
[x?] sgf review improvements -- Likewise, in the 0.9 version, better alternatives to the played move were shown with squares, which was also pretty useful when using the sgf outside of Katrain. I mean, having the top move mentioned is all and good, but when you see multiple squares shown on the board as better alternatives to the move played in the game, it makes obvious how far from perfect that move actually was :D
[/] README
[] Release notes
Low priority
[] pv with overlap?
[] more teaching / groups in danger? hard
[] When creating a new game, the 9 buttons on the right side aren't all that useful. Maybe the 9, 13 and 19 ones make sense since these three board sizes are the traditionally used ones, but why 2, 4 and 9 stones buttons? Why 0.5, 6.5 and -40pts komi buttons?
[] Score instead of game end
[] Plus, explanatory bubbles would help to clarify labels like "Debug" (are there bugs in the matrix? :p), "enable_ownership" (which didn't seem to prevent or allow visualizing territory ownership on the board, as that was already covered by the "owner" checkbox anyway... so I guess I missed something), etc.
-- possible right-click?
Wont do for now
[] dual engine support -- easily possible but has weird effects on win rate etc
[/] The UI would be directly understood if there were bubbles with a short explanation popping up when hovering above buttons and labels, e.g "Performing additional analysis to 1502 visits" which appears currently in the comments window after pushing the Extra button would also make a perfect explanatory bubble when hovering over said button too.
--- partially solved by config with help for some