Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | support selections in the source editor | Kartik K. Agaram | 2022-09-06 | 1 | -1/+0 |
| | | | | | I've only tested side A so far, and included a statement of how I want side B to behave. | ||||
* | support drawings in the source editor | Kartik K. Agaram | 2022-09-05 | 1 | -17/+22 |
| | |||||
* | editing source code from within the app | Kartik K. Agaram | 2022-09-03 | 1 | -5/+0 |
| | | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243 | ||||
* | set color for each fragment | Kartik K. Agaram | 2022-08-23 | 1 | -1/+1 |
| | | | | | In general it seems like good practice to minimize assumptions about the current color. | ||||
* | helper: trimming whitespace from strings | Kartik K. Agaram | 2022-08-23 | 1 | -0/+12 |
| | |||||
* | fix a name | Kartik K. Agaram | 2022-08-19 | 1 | -4/+4 |
| | |||||
* | couple of accidental globals | Kartik K. Agaram | 2022-08-18 | 1 | -2/+2 |
| | | | | Luckily they didn't bite me yet. | ||||
* | get rid of some ridiculous code | Kartik K. Agaram | 2022-08-18 | 1 | -15/+5 |
| | | | | | | I guess I wrote it before I settled into the idiom of: * first change cursor * then scroll if necessary | ||||
* | spurious args | Kartik K. Agaram | 2022-08-18 | 1 | -18/+18 |
| | |||||
* | dead code | Kartik K. Agaram | 2022-08-18 | 1 | -2/+0 |
| | |||||
* | generalize a function | Kartik K. Agaram | 2022-08-18 | 1 | -9/+10 |
| | |||||
* | extract a variable | Kartik K. Agaram | 2022-08-18 | 1 | -2/+3 |
| | |||||
* | simplify | Kartik K. Agaram | 2022-08-18 | 1 | -4/+1 |
| | |||||
* | move caching behavior inside compute_fragments | Kartik K. Agaram | 2022-08-17 | 1 | -6/+6 |
| | |||||
* | remove some unnecessary work | Kartik K. Agaram | 2022-08-17 | 1 | -1/+3 |
| | |||||
* | standardize scroll check in a few places | Kartik K. Agaram | 2022-08-17 | 1 | -3/+3 |
| | | | | | | | | | | | | I'm taking some lessons from pensieve.love here. It seem like specific pixel thresholds don't matter too much for plain lines.love. I'd probably feel safer if I just used Text.cursor_out_of_screen in these places, but it means we draw the screen twice for most events[1]. Let's see if we can get by with the current approach. [1] Or we have to start scheduling things for the next draw, which is more complex to orchestrate. | ||||
* | simplify cursor-on-screen check | Kartik K. Agaram | 2022-08-17 | 1 | -6/+6 |
| | |||||
* | swap return values | Kartik K. Agaram | 2022-08-17 | 1 | -5/+5 |
| | |||||
* | obsolete comment | Kartik K. Agaram | 2022-08-16 | 1 | -2/+0 |
| | |||||
* | move | Kartik K. Agaram | 2022-08-15 | 1 | -28/+28 |
| | |||||
* | drop some unnecessary calls | Kartik K. Agaram | 2022-08-15 | 1 | -6/+0 |
| | |||||
* | stop confusingly reading a global | Kartik K. Agaram | 2022-08-15 | 1 | -2/+2 |
| | | | | | | | The way Text.draw is called by edit.draw, we know it'll never be called for lines above screen_top1.line. Comparing every line on screen with screen_top1 makes no sense. The intent is really just to compare with screen_top1 only for the first line, and otherwise to ignore this check. | ||||
* | bugfix: handle drawings when updating screen top | Kartik K. Agaram | 2022-08-11 | 1 | -0/+1 |
| | |||||
* | rename | Kartik K. Agaram | 2022-08-11 | 1 | -24/+24 |
| | |||||
* | bugfix: pagedown was sometimes bouncing up | Kartik K. Agaram | 2022-08-10 | 1 | -1/+1 |
| | |||||
* | bugfix: backspace from start of final line | Kartik K. Agaram | 2022-08-10 | 1 | -1/+5 |
| | |||||
* | unnecessary args | Kartik K. Agaram | 2022-08-10 | 1 | -1/+1 |
| | |||||
* | click to the left of a line | Kartik K. Agaram | 2022-07-29 | 1 | -2/+1 |
| | |||||
* | bugfix: search | Kartik K. Agaram | 2022-07-21 | 1 | -1/+1 |
| | | | | | Broken since commit 188bbc73 9 days ago :/ At least we have a test for it now. | ||||
* | use line cache for drawings as well | Kartik K. Agaram | 2022-07-20 | 1 | -26/+26 |
| | |||||
* | bugfix: where cursor is drawn | Kartik K. Agaram | 2022-07-20 | 1 | -4/+11 |
| | | | | | | | The published version of lines.love was broken for almost an hour. The cursor would render one position to the right of where it really is. To fix it, this commit rolls back 26ba6e4e5a71. There doesn't seem a good way to test it. | ||||
* | . | Kartik K. Agaram | 2022-07-20 | 1 | -0/+2 |
| | |||||
* | exclude left margin from my word-split heuristic | Kartik K. Agaram | 2022-07-20 | 1 | -1/+1 |
| | | | | | Gratifying how few tests need changing. Recent commits seem on the right track. | ||||
* | allow Text.nearest_pos_less_than to return 0 | Kartik K. Agaram | 2022-07-20 | 1 | -5/+2 |
| | | | | This eliminates another case of overflowing margins. | ||||
* | drop an unnecessary level of indent | Kartik K. Agaram | 2022-07-20 | 1 | -23/+21 |
| | |||||
* | clean up some prints | Kartik K. Agaram | 2022-07-20 | 1 | -17/+10 |
| | | | | | (Looking at prints in Text.draw, Text.compute_fragments and Text.nearest_pos_less_than) | ||||
* | move a var closer to its use | Kartik K. Agaram | 2022-07-20 | 1 | -2/+2 |
| | |||||
* | more clearly skip prints before screen top | Kartik K. Agaram | 2022-07-20 | 1 | -21/+19 |
| | |||||
* | unify two similar functions | Kartik K. Agaram | 2022-07-19 | 1 | -11/+4 |
| | | | | | | The cost is just having to tweak a few more brittle tests. I can't actually perceive any difference in how the cursor moves when I click on text. | ||||
* | keep text from overflowing right margin | Kartik K. Agaram | 2022-07-19 | 1 | -5/+15 |
| | | | | | | | | | | I've been sloppy about this so far, and outside of tests I can't find any examples where it matters, but it matters in a potential fork where I'm rendering multiple columns of text. It's unfortunate that my tests have this level of brittleness. What I'd really like to assert in many of these changed lines is that the text stays inside the margins and that more text would overflow margins. | ||||
* | bugfix: couple of margin-relative computations | Kartik K. Agaram | 2022-07-17 | 1 | -2/+2 |
| | |||||
* | separate data structure for each line's cache data | Kartik K. Agaram | 2022-07-17 | 1 | -50/+58 |
| | | | | I have no idea what the performance implications of this are.. | ||||
* | keep all text cache writes inside text.lua | Kartik K. Agaram | 2022-07-17 | 1 | -5/+5 |
| | |||||
* | switch to line index in a function | Kartik K. Agaram | 2022-07-17 | 1 | -2/+3 |
| | | | | - Text.screen_line_width | ||||
* | switch to line index in a function | Kartik K. Agaram | 2022-07-17 | 1 | -16/+17 |
| | | | | - Text.compute_fragments | ||||
* | make a function oblivious to line data structure | Kartik K. Agaram | 2022-07-17 | 1 | -5/+5 |
| | | | | - Text.screen_line_index | ||||
* | switch to line index in a function | Kartik K. Agaram | 2022-07-17 | 1 | -3/+3 |
| | | | | - Text.to_pos_on_line | ||||
* | switch to line index in a function | Kartik K. Agaram | 2022-07-17 | 1 | -15/+16 |
| | | | | - Text.populate_screen_line_starting_pos | ||||
* | switch to line index in a function | Kartik K. Agaram | 2022-07-17 | 1 | -1/+2 |
| | | | | - Text.in_line | ||||
* | drop some redundant args when clearing the cache | Kartik K. Agaram | 2022-07-17 | 1 | -10/+10 |
| |