From 4243d710ed2a4a3d7881dae01879598a4fbcb5c7 Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Fri, 22 May 2015 17:11:03 -0700 Subject: 1418 - starting trace-browser implementation in C++ I still have no idea how it will hook up to the rest. Parsing traces will be slow. I can't test it like this. Writing the large trace data structure to mu memory will be slow. But let's at least see the new algorithm in action. (Not in this commit; so far we just render the first n lines from the chessboard trace, and wait for a 'q' or 'Q' to quit.) --- chessboard.mu | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'chessboard.mu') diff --git a/chessboard.mu b/chessboard.mu index aac3e1cc..679d4805 100644 --- a/chessboard.mu +++ b/chessboard.mu @@ -25,7 +25,7 @@ recipe main [ ## But enough about mu. Here's what it looks like to run the chessboard program. scenario print-board-and-read-move [ - $close-trace # administrivia: most scenarios save and check traces, but this one gets too large/slow +#? $close-trace # administrivia: most scenarios save and check traces, but this one gets too large/slow # we'll make the screen really wide because the program currently prints out a long line assume-screen 120:literal/width, 20:literal/height # initialize keyboard to type in a move @@ -33,6 +33,8 @@ scenario print-board-and-read-move [ ] run [ screen:address, keyboard:address <- chessboard screen:address, keyboard:address + $browse-trace + $close-trace # icon for the cursor screen:address <- print-character screen:address, 9251:literal # '␣' ] -- cgit 1.4.1-2-gfad0