about summary refs log tree commit diff stats
path: root/text.lua
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2023-04-031-4/+3
|\
| * switch source side to new screen-line-based renderKartik K. Agaram2023-04-031-1/+0
| | | | | | | | Also copy over the implementation of links from pensieve.love.
| * change cursor bounds check slightlyKartik K. Agaram2023-04-021-1/+1
| | | | | | | | | | | | This doesn't affect this fork directly, but it's a bad idea to assume the _app_ is always going to be doing just what a particular subsystem (here, the text editor in edit.lua+text.lua) is doing.
| * streamline the interface for Text.drawKartik K. Agaram2023-04-021-2/+2
| |
* | Merge lines.loveKartik K. Agaram2023-04-021-90/+53
|\|
| * avoid saving fragments in linesKartik K. Agaram2023-04-011-67/+46
| | | | | | | | | | | | | | Now we render lines one screen line at a time rather than one word at a time. I can't port the source side just yet; I need to fix hyperlinks first..
| * start thinking of compute_fragments as a detailKartik K. Agaram2023-04-011-1/+1
| | | | | | | | | | | | | | | | | | | | I think all we need to maintain is the populate_screen_line_starting_pos array. It's easy to render screen lines one by one from it, and we'll only ever construct one additional screen line at a time. I'd hoped to delete other calls to Text.populate_screen_line_starting_pos, but it turns out we need to update it when editing sometimes. Give up on that for now; it's a no-op if not needed.
| * stop creating a singleton table for every wordKartik K. Agaram2023-04-011-10/+10
| |
| * clean up some debug printsKartik K. Agaram2023-04-011-8/+0
| | | | | | | | | | It's starting to become apparent just how little line_cache.fragments does for me now. Let's see if we can get rid of it entirely.
| * no more Text allocationsKartik K. Agaram2023-04-011-14/+8
| | | | | | | | Is it just my imagination, or does the app feel lighter and more fluffy?
| * App.width can no longer take a TextKartik K. Agaram2023-04-011-11/+8
| | | | | | | | | | In the process I discovered the horrible fact that Text.x allocates a new Text. And it gets called (just once, thank goodness) on every single frame.
| * bugfix: naming pointsKartik K. Agaram2023-03-261-0/+1
| |
* | Merge lines.loveKartik K. Agaram2023-03-171-11/+15
|\|
| * more bugfixKartik K. Agaram2023-03-171-1/+1
| | | | | | | | Don't crash on showing the log browser.
| * bugfixKartik K. Agaram2023-03-171-9/+14
| | | | | | | | Thanks Mikoláš Štrajt.
| * get rid of all bifold textKartik K. Agaram2023-03-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's just uneconomic to maintain given how little I've used it. I have a bug right now and no time to port the bugfix to all the complexities of the B side. I briefly considered tossing out the entire source editor. But I _have_ been using it to browse logs across sessions. The live editor doesn't quite cover all my use cases just yet. We now have duplication in the source editor only for: * syntax highlighting * hyperlinking [[WikiWords]] * ability to hide cursor (when showing file browser or Focus is in log browser)
* | Merge lines.loveKartik K. Agaram2023-01-311-1/+1
|\|
| * bugfix: up arrow when line above is a drawingKartik K. Agaram2023-01-311-1/+1
| | | | | | | | This bug was introduced in commit 528c64d690 on 2022-09-05 :/
* | Merge lines.loveKartik K. Agaram2023-01-131-0/+24
|\|
| * reduce use of rfindKartik K. Agaram2023-01-131-0/+24
| |
* | Merge lines.loveKartik K. Agaram2022-12-231-3/+3
|\|
| * make love event names consistentKartik K. Agaram2022-12-231-3/+3
| | | | | | | | | | I want the words to be easy to read, and to use a consistent tense. update and focus seem more timeless; let's make everything like those.
* | Merge lines.loveKartik K. Agaram2022-09-061-1/+0
|\|
| * support selections in the source editorKartik K. Agaram2022-09-061-1/+0
| | | | | | | | | | I've only tested side A so far, and included a statement of how I want side B to behave.
* | Merge lines.loveKartik K. Agaram2022-09-051-10/+12
|\|
| * support drawings in the source editorKartik K. Agaram2022-09-051-17/+22
| |
| * editing source code from within the appKartik K. Agaram2022-09-031-5/+0
| | | | | | | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
* | stray edit from source_text.luaKartik K. Agaram2022-09-031-1/+0
| |
* | editing source code from within the appKartik K. Agaram2022-09-031-5/+1
| | | | | | | | integrated from pong.love: https://merveilles.town/@akkartik/108933336531898243
* | Merge lines.loveKartik K. Agaram2022-08-231-1/+13
|\|
| * set color for each fragmentKartik K. Agaram2022-08-231-1/+1
| | | | | | | | | | In general it seems like good practice to minimize assumptions about the current color.
| * helper: trimming whitespace from stringsKartik K. Agaram2022-08-231-0/+12
| |
* | Merge lines.loveKartik K. Agaram2022-08-191-4/+4
|\|
| * fix a nameKartik K. Agaram2022-08-191-4/+4
| |
* | Merge lines.loveKartik K. Agaram2022-08-181-2/+2
|\|
| * couple of accidental globalsKartik K. Agaram2022-08-181-2/+2
| | | | | | | | Luckily they didn't bite me yet.
* | Merge lines.loveKartik K. Agaram2022-08-181-49/+36
|\|
| * get rid of some ridiculous codeKartik K. Agaram2022-08-181-15/+5
| | | | | | | | | | | | I guess I wrote it before I settled into the idiom of: * first change cursor * then scroll if necessary
| * spurious argsKartik K. Agaram2022-08-181-18/+18
| |
| * dead codeKartik K. Agaram2022-08-181-2/+0
| |
| * generalize a functionKartik K. Agaram2022-08-181-9/+10
| |
| * extract a variableKartik K. Agaram2022-08-181-2/+3
| |
| * simplifyKartik K. Agaram2022-08-181-4/+1
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-4/+5
|\|
| * move caching behavior inside compute_fragmentsKartik K. Agaram2022-08-171-6/+6
| |
| * remove some unnecessary workKartik K. Agaram2022-08-171-1/+3
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-9/+9
|\|
| * standardize scroll check in a few placesKartik K. Agaram2022-08-171-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 checkKartik K. Agaram2022-08-171-6/+6
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-5/+5
|\|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-06-28 05:32:26 +0000