| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | first successful pagedown test, first bug found by test | Kartik K. Agaram | 2022-05-23 | 4 | -14/+86 |
| | | | | | | | | | | | | | | | | | | | | I also really need to rethink how people debug my programs. My approach of inserting and deleting print() takes a lot of commitment. I need my old trace-based whitebox testing idea. However, in my past projects I never did figure out a good framework for tweaking how verbose a trace to emit. Perhaps that's too many knobs. Perhaps we just need a way to run a single test with the most verbose trace possible. Then it's just a matter of having the trace tell a coherent story? But even if the trace stays out of program output in that situation, it's still in the programmer's face in the _code_. Ugh. Current plan: ship program with maximum tests and zero commented-out prints. If you want to debug, insert prints. This is better than previous, text-mode, projects just by virtue of the stdout channel being dedicated to debug stuff. | ||||
| * | first test! | Kartik K. Agaram | 2022-05-22 | 2 | -12/+87 |
| | | |||||
| * | fold variables for screen dimensions into the app framework | Kartik K. Agaram | 2022-05-22 | 1 | -8/+8 |
| | | |||||
| * | one more implication | Kartik K. Agaram | 2022-05-22 | 1 | -0/+3 |
| | | |||||
| * | basic test-enabled framework | Kartik K. Agaram | 2022-05-22 | 4 | -34/+251 |
| | | | | | | Tests still have a lot of side-effects on the real screen. We'll gradually clean those up. | ||||
| * | rename | Kartik K. Agaram | 2022-05-22 | 2 | -1/+3 |
| | | |||||
| * | yet another bugfix. But for how long? | Kartik K. Agaram | 2022-05-22 | 1 | -1/+1 |
| | | |||||
| * | beginnings of a test harness | Kartik K. Agaram | 2022-05-22 | 2 | -0/+38 |
| | | | | | | | | | | | | | | | | | | | | I have no fucking idea what I'm doing. All I know is that there's still too many goddamn bugs[1]. Test motherfucking harness or bust. For starters this is just the default love.run from https://love2d.org/wiki/love.run [1] The following file crashes if you repeatedly press cursor-down: << a b c ```lines ``` x >> | ||||
| * | up and down arrow now moving by screen line where possible | Kartik K. Agaram | 2022-05-21 | 1 | -25/+47 |
| | | | | | Drawings can't be drawn partially, which sometimes makes things jerky. | ||||
| * | bugfix: printing the first part of a line at the bottom made it seem ↵ | Kartik K. Agaram | 2022-05-21 | 2 | -30/+43 |
| | | | | | | | non-wrapping Still lots wrong here. | ||||
| * | cleaner | Kartik K. Agaram | 2022-05-21 | 1 | -3/+2 |
| | | |||||
| * | I feel confident now that page-down is working. | Kartik K. Agaram | 2022-05-21 | 2 | -3/+12 |
| | | |||||
| * | couple of TODOs | Kartik K. Agaram | 2022-05-21 | 2 | -1/+2 |
| | | |||||
| * | beginning of a new approach to scroll+wrap | Kartik K. Agaram | 2022-05-21 | 2 | -155/+187 |
| | | | | | | | | So far I've just changed how existing variables are organized, and put some scaffolding in place for dealing with the new types. Next up: rewriting the code for scrolling to something that feels more obviously correct. | ||||
| * | bugfix: escape key to hide online help | Kartik K. Agaram | 2022-05-21 | 2 | -6/+6 |
| | | |||||
| * | help tweak | Kartik K. Agaram | 2022-05-21 | 1 | -1/+3 |
| | | |||||
| * | show when we're naming a point | Kartik K. Agaram | 2022-05-21 | 1 | -2/+14 |
| | | |||||
| * | support for naming points | Kartik K. Agaram | 2022-05-21 | 7 | -4/+62 |
| | | | | | There's still an absence of affordance showing when you're in naming mode. | ||||
| * | new known issue with drawings | Kartik K. Agaram | 2022-05-21 | 1 | -0/+19 |
| | | |||||
| * | one missing transition between shape modes | Kartik K. Agaram | 2022-05-21 | 1 | -1/+3 |
| | | |||||
| * | several bugfixes | Kartik K. Agaram | 2022-05-21 | 2 | -2/+9 |
| | | | | | All introduced when I built rectangles and squares in commit e27165cb. | ||||
| * | bugfix: rectangles and squares are now saved | Kartik K. Agaram | 2022-05-21 | 2 | -2/+11 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2022-05-21 | 1 | -10/+2 |
| | | | | | | Looks like I never retested rectangles after I implemented drawing squares, even though I made changes to the rectangle implementation :/ | ||||
| * | bugfix: missed rename in one file | Kartik K. Agaram | 2022-05-21 | 1 | -2/+2 |
| | | |||||
| * | disable some debug prints | Kartik K. Agaram | 2022-05-20 | 1 | -23/+23 |
| | | | | | | I'm still very much in the region where this is valuable sensor data. This is a new domain. | ||||
| * | more precise height calculation when scrolling up as much as possible while ↵ | Kartik K. Agaram | 2022-05-20 | 1 | -4/+21 |
| | | | | | keeping cursor on screen | ||||
| * | keep cursor on screen when pressing 'down' | Kartik K. Agaram | 2022-05-20 | 2 | -3/+5 |
| | | |||||
| * | rename | Kartik K. Agaram | 2022-05-20 | 1 | -7/+7 |
| | | |||||
| * | reduce ambitions a bit: page up/down need not start screen from the middle ↵ | Kartik K. Agaram | 2022-05-20 | 2 | -20/+17 |
| | | | | | | | of a line But we still have work to do for cursor up/down. | ||||
| * | first stab at equally hacky cursor down support | Kartik K. Agaram | 2022-05-20 | 1 | -11/+42 |
| | | |||||
| * | stop recomputing Cursor_x now that we're saving it | Kartik K. Agaram | 2022-05-20 | 1 | -5/+3 |
| | | |||||
| * | clearer comments | Kartik K. Agaram | 2022-05-20 | 1 | -2/+3 |
| | | |||||
| * | ensure Filename is writable when opened outside a terminal | Kartik K. Agaram | 2022-05-20 | 1 | -1/+1 |
| | | | | | Thanks Jimmy Miller for reporting this. | ||||
| * | some more logging | Kartik K. Agaram | 2022-05-20 | 1 | -1/+11 |
| | | | | | | | | | | | | Still lots of signs it's all messed up, but I can't be sure until I bring all the other keyboard shortcuts in sync. I just need a better data structure that simplifies the logic. Perhaps talk in terms of screen lines. In which case: We'll need to convert lines to screen lines at some point. We'll need to fix up screen lines when inserting and deleting characters. | ||||
| * | snapshot - no, that's all wrong | Kartik K. Agaram | 2022-05-20 | 3 | -17/+43 |
| | | | | | | I've been only thinking about up arrow when cursor is at top of screen. Hopefully this is better. | ||||
| * | another piece of support for line wrapping in cursor up | Kartik K. Agaram | 2022-05-20 | 2 | -1/+10 |
| | | |||||
| * | first stab at supporting wrapping in cursor up | Kartik K. Agaram | 2022-05-20 | 2 | -13/+33 |
| | | | | | Looks pretty clean. | ||||
| * | bugfix | Kartik K. Agaram | 2022-05-20 | 1 | -16/+3 |
| | | | | | | | | I'd wrapped currx in two conditionals, and not noticed that it gets reclaimed within the other. The hint is clearly more work than it's worth. Just take it out. | ||||
| * | new globals: draw partial screen line up top | Kartik K. Agaram | 2022-05-20 | 2 | -2/+9 |
| | | | | | | I'm not setting these yet. Rendering seems to be working after manually setting them. | ||||
| * | start using some globals | Kartik K. Agaram | 2022-05-20 | 2 | -6/+6 |
| | | |||||
| * | move | Kartik K. Agaram | 2022-05-20 | 1 | -2/+4 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2022-05-20 | 1 | -1/+1 |
| | | |||||
| * | start remembering where the cursor is drawn in px | Kartik K. Agaram | 2022-05-20 | 2 | -0/+4 |
| | | | | | We'll start using this in cursor up/down motions. | ||||
| * | extract a function | Kartik K. Agaram | 2022-05-20 | 2 | -12/+9 |
| | | |||||
| * | move | Kartik K. Agaram | 2022-05-19 | 1 | -35/+35 |
| | | |||||
| * | planning out cursor up/down over wrapped lines | Kartik K. Agaram | 2022-05-19 | 2 | -3/+5 |
| | | |||||
| * | bugfix: cursor past end of screen line | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 |
| | | |||||
| * | bugfix: text past cursor was rendered red on wrapped lines | Kartik K. Agaram | 2022-05-19 | 2 | -0/+3 |
| | | |||||
| * | bugfix: show cursor when past end of line | Kartik K. Agaram | 2022-05-19 | 2 | -0/+6 |
| | | |||||
| * | change text cursor shape | Kartik K. Agaram | 2022-05-19 | 2 | -3/+5 |
| | | |||||