| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | first successful pagedown test, first bug found by test | Kartik K. Agaram | 2022-05-23 | 1 | -7/+8 | |
| | | | | | | | | | | | | | | | | | | | | 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. | |||||
| * | fold variables for screen dimensions into the app framework | Kartik K. Agaram | 2022-05-22 | 1 | -8/+8 | |
| | | ||||||
| * | basic test-enabled framework | Kartik K. Agaram | 2022-05-22 | 1 | -26/+25 | |
| | | | | | | 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 | 1 | -1/+3 | |
| | | ||||||
| * | beginnings of a test harness | Kartik K. Agaram | 2022-05-22 | 1 | -0/+1 | |
| | | | | | | | | | | | | | | | | | | | | 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 >> | |||||
| * | bugfix: printing the first part of a line at the bottom made it seem ↵ | Kartik K. Agaram | 2022-05-21 | 1 | -9/+17 | |
| | | | | | | | non-wrapping Still lots wrong here. | |||||
| * | I feel confident now that page-down is working. | Kartik K. Agaram | 2022-05-21 | 1 | -2/+3 | |
| | | ||||||
| * | beginning of a new approach to scroll+wrap | Kartik K. Agaram | 2022-05-21 | 1 | -25/+31 | |
| | | | | | | | | 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 | 1 | -0/+6 | |
| | | ||||||
| * | support for naming points | Kartik K. Agaram | 2022-05-21 | 1 | -0/+27 | |
| | | | | | There's still an absence of affordance showing when you're in naming mode. | |||||
| * | keep cursor on screen when pressing 'down' | Kartik K. Agaram | 2022-05-20 | 1 | -1/+1 | |
| | | ||||||
| * | reduce ambitions a bit: page up/down need not start screen from the middle ↵ | Kartik K. Agaram | 2022-05-20 | 1 | -13/+14 | |
| | | | | | | | of a line But we still have work to do for cursor up/down. | |||||
| * | ensure Filename is writable when opened outside a terminal | Kartik K. Agaram | 2022-05-20 | 1 | -1/+1 | |
| | | | | | Thanks Jimmy Miller for reporting this. | |||||
| * | snapshot - no, that's all wrong | Kartik K. Agaram | 2022-05-20 | 1 | -9/+11 | |
| | | | | | | I've been only thinking about up arrow when cursor is at top of screen. Hopefully this is better. | |||||
| * | new globals: draw partial screen line up top | Kartik K. Agaram | 2022-05-20 | 1 | -0/+3 | |
| | | | | | | 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 | 1 | -1/+1 | |
| | | ||||||
| * | move | Kartik K. Agaram | 2022-05-20 | 1 | -2/+4 | |
| | | ||||||
| * | start remembering where the cursor is drawn in px | Kartik K. Agaram | 2022-05-20 | 1 | -0/+2 | |
| | | | | | We'll start using this in cursor up/down motions. | |||||
| * | extract a function | Kartik K. Agaram | 2022-05-20 | 1 | -4/+1 | |
| | | ||||||
| * | bugfix: text past cursor was rendered red on wrapped lines | Kartik K. Agaram | 2022-05-19 | 1 | -0/+1 | |
| | | ||||||
| * | change text cursor shape | Kartik K. Agaram | 2022-05-19 | 1 | -2/+3 | |
| | | ||||||
| * | clicking now moves the cursor even on long, wrapped lines | Kartik K. Agaram | 2022-05-19 | 1 | -2/+2 | |
| | | ||||||
| * | make text and drawings the same width | Kartik K. Agaram | 2022-05-19 | 1 | -5/+3 | |
| | | ||||||
| * | comment | Kartik K. Agaram | 2022-05-19 | 1 | -6/+1 | |
| | | ||||||
| * | eliminate assumptions that line length == size in bytes | Kartik K. Agaram | 2022-05-19 | 1 | -3/+3 | |
| | | ||||||
| * | snapshot: wrapping long lines at word boundaries | Kartik K. Agaram | 2022-05-19 | 1 | -1/+3 | |
| | | | | | | | Still not working: clicking on text to move the cursor aborts up/down motions still move by logical lines rather than screen lines | |||||
| * | a few more integer coordinates | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 | |
| | | ||||||
| * | this is a bit clearer | Kartik K. Agaram | 2022-05-19 | 1 | -2/+2 | |
| | | ||||||
| * | redo y computations | Kartik K. Agaram | 2022-05-19 | 1 | -4/+8 | |
| | | ||||||
| * | simpler | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 | |
| | | ||||||
| * | delete another arg that can be deduced | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 | |
| | | ||||||
| * | delete unused arg | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 | |
| | | ||||||
| * | ensure integer coordinates | Kartik K. Agaram | 2022-05-19 | 1 | -1/+1 | |
| | | | | | | https://love2d.org/wiki/Text says text can appear blurry otherwise. I can't tell yet, though. | |||||
| * | bugfix: ensure Cursor_line is always on a text line | Kartik K. Agaram | 2022-05-18 | 1 | -3/+4 | |
| | | | | | | | | | | | | | | | | | | | | | Manual test used here: abc ```lines {"p1":{"y":72,"x":82},"mode":"line","p2":{"y":29,"x":169}} ``` def ```lines {"p1":{"y":36,"x":56},"mode":"line","p2":{"y":59,"x":163}} ``` ```lines ``` ghi jkl Hitting page-down moves the cursor from abc to ghi. The 'ghi' line should be fully visible on screen. | |||||
| * | bugfix: position cursor up top when loading file | Kartik K. Agaram | 2022-05-18 | 1 | -0/+2 | |
| | | ||||||
| * | scroll past first page | Kartik K. Agaram | 2022-05-18 | 1 | -20/+49 | |
| | | | | | | | Still some limitations. The text cursor has to be visible on screen, so if you have a long series of drawings without intervening lines of text you won't be able to scroll through them all. | |||||
| * | highlight another global | Kartik K. Agaram | 2022-05-17 | 1 | -1/+1 | |
| | | ||||||
| * | forgot to move this special case out | Kartik K. Agaram | 2022-05-17 | 1 | -0/+5 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-05-17 | 1 | -2/+2 | |
| | | ||||||
| * | delegate update events to drawings | Kartik K. Agaram | 2022-05-17 | 1 | -21/+1 | |
| | | ||||||
| * | DRY some code | Kartik K. Agaram | 2022-05-17 | 1 | -16/+12 | |
| | | ||||||
| * | move mouse_released events to Drawing | Kartik K. Agaram | 2022-05-17 | 1 | -57/+1 | |
| | | ||||||
| * | split mouse_pressed events between Text and Drawing | Kartik K. Agaram | 2022-05-17 | 1 | -20/+4 | |
| | | ||||||
| * | split keyboard handling between Text and Drawing | Kartik K. Agaram | 2022-05-17 | 1 | -286/+4 | |
| | | ||||||
| * | autosave in a couple more places | Kartik K. Agaram | 2022-05-17 | 1 | -0/+3 | |
| | | ||||||
| * | assume we always have a filename | Kartik K. Agaram | 2022-05-17 | 1 | -6/+2 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-05-17 | 1 | -6/+4 | |
| | | ||||||
| * | bugfix: duplicate character on enter | Kartik K. Agaram | 2022-05-17 | 1 | -1/+1 | |
| | | ||||||
| * | jump between lines on left/right | Kartik K. Agaram | 2022-05-17 | 1 | -0/+22 | |
| | | | | | Also skip past drawings. | |||||
| * | split lines on enter | Kartik K. Agaram | 2022-05-17 | 1 | -3/+7 | |
| | | ||||||