about summary refs log tree commit diff stats
path: root/chessboard-cursor.mu
Commit message (Collapse)AuthorAgeFilesLines
* 616 - buffered-stdin handles backspaceKartik K. Agaram2015-01-251-1/+4
| | | | Chessboard now *almost* handles backspace perfectly.
* 611 - all tests passing againKartik K. Agaram2015-01-241-10/+6
|
* 610 - all examples working againKartik K. Agaram2015-01-241-3/+0
|
* 601 - fix callers of 'read-key'Kartik K. Agaram2015-01-241-1/+1
|
* 593 - clean up the raw stdin addressKartik K. Agaram2015-01-181-11/+15
|
* 591Kartik K. Agaram2015-01-181-5/+2
| | | | | I don't remember what exactly we wanted to test in the second move. But we can write it next time we need it.
* 590Kartik K. Agaram2015-01-181-0/+2
|
* 589Kartik K. Agaram2015-01-181-3/+0
|
* 588Kartik K. Agaram2015-01-181-2/+0
| | | | | Now that there isn't a stdout channel we can postpone the test showing the need to flush-stdout before clearing screen.
* 587Kartik K. Agaram2015-01-181-1/+0
|
* 586Kartik K. Agaram2015-01-181-23/+13
| | | | Dump yet another trying-to-be-polymorphic function.
* 583Kartik K. Agaram2015-01-181-1/+0
|
* 582 - first tests for printing to screenKartik K. Agaram2015-01-171-13/+16
|
* 578 - switch to non-polymorphic 'print' functionsKartik K. Agaram2015-01-171-2/+2
| | | | | Also clean up various prints from last few commits. As a convention, for debugging we always print directly to host.
* 574 - printing string literals is a hack; hard-code it in for nowKartik K. Agaram2015-01-161-8/+8
|
* 573 - print-board now takes terminal parameterKartik K. Agaram2015-01-151-10/+11
| | | | Feeling more confident now that prints are being managed right.
* 572Kartik K. Agaram2015-01-151-9/+10
|
* 571 - screen primitives take an explicit terminalKartik K. Agaram2015-01-151-19/+19
| | | | | | | | | | | | | | | | | This will let me swap in a fake in tests. Still hacky, though. I'm sure I'm not managing the parameter right in the chessboard app. And then there's the question of whether it should also appear as an output operand. But it's a start. And using nil to mean 'real' is a reasonable convention. If I ever need to handle multiple screens perhaps we'll have to switch to 1:literal/terminal and 2:literal/terminal, etc. But those are equally easy to guard on.
* 567 - stupid function name conflictKartik K. Agaram2015-01-141-4/+4
| | | | Is it even worth having my generic function prepend idea?
* 562Kartik K. Agaram2015-01-141-1/+0
|
* 560Kartik K. Agaram2015-01-131-3/+0
|
* 554 - tedious to have to check for routine errors on every forkKartik K. Agaram2015-01-131-0/+1
|
* 551Kartik K. Agaram2015-01-131-55/+61
| | | | Tests force me to extract functions 'read-rank' and 'read-file'.
* 550 - another bugfix, another pending testKartik K. Agaram2015-01-131-0/+3
|
* 549 - suppress prints in read-moveKartik K. Agaram2015-01-131-5/+21
| | | | | | This is the sort of thing we want to make super easy. But there's a bug at the moment: chessboard prints junk input at second move.
* 546 - chessboard now reads from stdinKartik K. Agaram2015-01-121-5/+13
| | | | Hacky, but it's a start.
* 544 - text modes now called 'retro' & 'cursor'Kartik K. Agaram2015-01-121-0/+223
Other options considered for 'retro': 'teletype': perhaps most accurate, but arcane 'chat': captures that you have to hit 'enter', but not the rendering 'wrap': captures the auto-wrap when printing text but not that you have to hit 'enter' when typing 'text': useful as a synonym of 'chat' while conveying more information in other meanings, but too generic, nobody will get it Why do the input and output options have to be entangled like this?
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-09-15 05:51:35 +0000