about summary refs log tree commit diff stats
path: root/graphics.mu
Commit message (Collapse)AuthorAgeFilesLines
* 690 - convention: '$' commands for debugging onlyKartik K. Agaram2015-02-011-7/+8
| | | | | | Swap printing generalized objects using arc's infrastructure to be the $-prefixed debug helper, while the erstwhile $print-key-to-host becomes the primitive print-character to host.
* 578 - switch to non-polymorphic 'print' functionsKartik K. Agaram2015-01-171-2/+7
| | | | | 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-2/+2
|
* 571 - screen primitives take an explicit terminalKartik K. Agaram2015-01-151-4/+4
| | | | | | | | | | | | | | | | | 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.
* 545 - graphics mode is now called bringing up a windowKartik K. Agaram2015-01-121-2/+2
|
* 503 - start of a solution for drawing piecesKartik K. Agaram2015-01-051-5/+2
| | | | | | | | | | | Dog slow, though. Drawing the sprite for a single piece takes 12s or 30ms/pixel for 400 pixels. A third of that is the actual racket overhead of drawing pixel by pixel, which would in itself be too much. We need bitblts. (Black queen pixels derived from http://www.wpclipart.com/recreation/games/chess/chess_set_1, after scaling down to 40x40 and replacing external white pixels with transparent ones in Gimp.)
* 443 - simple graphics primitivesKartik K. Agaram2014-12-231-0/+20
http://docs.racket-lang.org/graphics/Mouse_Operations.html Like with the text mode primitives, we still don't have a story for writing white-box tests for code using these.