You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When comparing chess.com and lichess's chessboards, their coordinates are displayed inside the board, which makes the layout more compact and visually appealing. In python-chess, the coordinates are rendered outside the chessboard. Based on documentation and testing, there seems to be no parameter or method to control the coordinate display style.
Is there a plan to support internal coordinate rendering in future updates?
chess.com
lichess
python-chess
The text was updated successfully, but these errors were encountered:
IMO the only good aspect of the Lichess coordinate placement is the compactness. In every other regard, especially clarity and readability, it is (significantly) inferior.
IMO the only good aspect of the Lichess coordinate placement is the compactness. In every other regard, especially clarity and readability, it is (significantly) inferior.
How about the new coordinate layout for python-chess ?
Coordinates are clearly a second class citizen on that board. They are available, but not really meant to be used. Consider for a moment using a projector to show a puzzle to a class room. Either the students mostly know coordinates or they will struggle to read them. Note that the same idea applies to both Lichess and Chess.com -- most users either don't care about coordinates at all or know them blindly.
When comparing chess.com and lichess's chessboards, their coordinates are displayed inside the board, which makes the layout more compact and visually appealing. In
python-chess
, the coordinates are rendered outside the chessboard. Based on documentation and testing, there seems to be no parameter or method to control the coordinate display style.Is there a plan to support internal coordinate rendering in future updates?
chess.com

lichess

python-chess
The text was updated successfully, but these errors were encountered: