Dboingue
commented
2 months ago This is the idea, pretty close. Let me try another way. to make sure. And also, guess what, not able to stop covering all possible angles. at the risk of confusion in the end. This is to prevent false hope, for reader. It might be less disappointing.
That the lichess user SAN tree itself, not need to be voiced, but that the study author added comments of the chess poisitoins after the moves, in the user tree, not have to be diverting the eye gaze from the board information.
put the hearing pathways extra bandwidth to use. and keep train of thought on both board and author intent.
The chess move component sentence I do not undestand. Although if configurable, I think why not.
I currently do not need the moves to be read, as I can just use the mouse (trackball) on general board area. and mouse sroll I also have can have one hand on keyboard if needed. with home key internalized whereabouts, so pause to a key within that already brain mapped keyboard region, would not be a distraction. or sand in the cogs.
I currently can use peripheral vision to have some clue (but only in light background where the CSS seems to be optimized in choice of highlights and background, dark picutre mode, does not allow peripheral vision orientation, same for the active chapter by the way). The problem is for informative teacher dense comments, that need learning themselves, and would have to contain chess pointers themselves, such as plan ideas and board coordinte. I do not compute as second nature, the spreadheet concepts of AN. A-H. 1-8.. sorry. bad patzer here. too old for such new tricks maybe.
MS editor:
The concept is nearly there. Let me articulate it differently to ensure clarity. Moreover, I find myself unable to refrain from examining every possible angle, even at the risk of causing confusion ultimately. This approach is to avert giving the reader false hope, potentially leading to less disappointment.
In the case of the lichess user's SAN tree, it isn't necessary for it to be vocalized, but rather for the study author to add comments on the chess positions following the moves within the user's tree, without distracting from the board information.
Utilizing the additional bandwidth of auditory pathways could help maintain focus on both the board and the author's intent.
The sentence regarding the chess move component is unclear to me. However, if it's configurable, then I see no reason not to consider it.
Currently, I don't require the moves to be read aloud, as I can navigate using the mouse (trackball) over the general board area and scroll as needed. Additionally, I can keep one hand on the keyboard if necessary, with the home key's location internalized, so pausing to press a key within that familiar region of the keyboard wouldn't be a distraction or throw a wrench in the works.
At present, I can rely on peripheral vision to get a sense of the board (but only against a light background where the CSS seems optimized for highlight and background choices; the dark picture mode does not facilitate peripheral orientation, and the same applies to the active chapter). The challenge arises with dense, informative comments from the teacher, which require learning in themselves and should include chess pointers, such as strategic ideas and board coordinates. I don't instinctively grasp the spreadsheet concepts of algebraic notation, A-H, 1-8. Apologies, I'm just a poor player here, perhaps too old to learn such new tricks.
Me again
quizz: find the errors of MS editor. There are meaningful ones. Although give my redundance means of expression, they might be not crucial (in signal per character density, my expression might have some noise robustness, that kolmogorov notions of complexity or information might not have had in their ambient space declarative (usual rarely mentioned).
User wants to be able to fully immerse in the study (moves, board position, etc.) so not visually switch to the comments in the PGN. The comments would be read by text-to-speech, but have the ability to pause/start - using not only visible buttons, but also key shortcuts.
Also, there are the English language component of the comment and more technical bits, like SANs or UCIs. The SAN/UCI/variation part of the comment should be read slower, carefully.