about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2023-04-0218-250/+116
|\
| * avoid saving fragments in linesKartik K. Agaram2023-04-013-69/+48
| | | | | | | | | | | | | | 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..
| * show count of test failuresKartik K. Agaram2023-04-011-1/+1
| |
| * minor cleanup and a todo for laterKartik K. Agaram2023-04-012-14/+4
| |
| * clean up some final bifold codeKartik K. Agaram2023-04-012-19/+3
| |
| * start thinking of compute_fragments as a detailKartik K. Agaram2023-04-012-2/+2
| | | | | | | | | | | | | | | | | | | | 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.
| * update documentation on fragmentsKartik K. Agaram2023-04-012-2/+2
| | | | | | | | | | | | I see a path to at least maintain a single fragment per screen line. But can we do better? It even seems unnecessary to maintain two copies of the data, chopped up into lines and screen lines.
| * stop creating a singleton table for every wordKartik K. Agaram2023-04-012-22/+22
| |
| * clean up some debug printsKartik K. Agaram2023-04-012-16/+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-015-41/+18
| | | | | | | | 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-0111-71/+28
| | | | | | | | | | 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.
| * get rid of to_textKartik K. Agaram2023-04-017-42/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | I've been misunderstanding what Text objects are. They can render a lot of text with a given line height, word wrap, colors in various places. And I've been creating one for every word :facepalm: Unwinding this will take some time. This is just a first baby step for ad hoc text objects. Turns out I don't need to convert to Text to get something's rendered width, just the Font can do that. Thanks to the LÖVE Discord for educating me: https://discord.com/channels/329400828920070144/330089431379869708/1091535487333826580
* | Merge lines.loveKartik K. Agaram2023-03-300-0/+0
|\|
| * .Kartik K. Agaram2023-03-301-1/+0
| |
* | Merge lines.loveKartik K. Agaram2023-03-301-11/+8
|\|
| * obsolete manual testKartik K. Agaram2023-03-301-4/+0
| |
| * better formattingKartik K. Agaram2023-03-281-9/+11
| |
* | Merge lines.loveKartik K. Agaram2023-03-262-11/+17
|\|
| * update stale source X-(Kartik K. Agaram2023-03-262-11/+17
| |
* | Merge lines.loveKartik K. Agaram2023-03-263-5/+76
|\|
| * bugfix: naming pointsKartik K. Agaram2023-03-264-5/+44
| |
| * bugfixKartik K. Agaram2023-03-262-4/+37
| |
| * bugfixKartik K. Agaram2023-03-261-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | scenario: open a file starting with a drawing After this commit the program doesn't crash. Error: [string "edit.lua"]:127: attempt to get length of field 'data' (a nil value) stack traceback: [love "boot.lua"]:345: in function '__len' [string "edit.lua"]:127: in function 'invalid1' [string "edit.lua"]:116: in function 'check_locs' [string "run.lua"]:35: in function 'initialize' main.lua:96: in function 'initialize' [string "app.lua"]:144: in function 'run_tests_and_initialize' [string "app.lua"]:16: in function <[string "app.lua"]:13> [C]: in function 'xpcall' [love "boot.lua"]:361: in function <[love "boot.lua"]:348> [C]: in function 'xpcall'
* | Merge lines.loveKartik K. Agaram2023-03-251-2/+2
|\|
| * clean up some absolute coordinatesKartik K. Agaram2023-03-252-3/+3
| |
* | Merge lines.loveKartik K. Agaram2023-03-252-3/+3
|\|
| * update stale informationKartik K. Agaram2023-03-252-3/+3
| |
* | Merge lines.loveKartik K. Agaram2023-03-251-1/+2
|\|
| * stop reusing cursor locations between filesKartik K. Agaram2023-03-251-1/+2
| |
* | Merge lines.loveKartik K. Agaram2023-03-252-0/+27
|\|
| * experiment at avoiding some merge conflictsKartik K. Agaram2023-03-252-0/+27
| | | | | | | | https://merveilles.town/@akkartik/110084833821965708
* | Merge lines.loveKartik K. Agaram2023-03-236-12/+84
|\|
| * some minor cleanupKartik K. Agaram2023-03-234-5/+5
| | | | | | | | | | I can't see the mouse wheel ever setting dx, but it's more obvious now that the editor doesn't support panning left/right.
| * mouse wheel supportKartik K. Agaram2023-03-236-12/+84
| |
* | Merge lines.loveKartik K. Agaram2023-03-210-0/+0
|\|
| * mention a new toolKartik K. Agaram2023-03-211-0/+2
| |
* | Merge lines.loveKartik K. Agaram2023-03-192-6/+6
|\|
| * give a test a unique nameKartik K. Agaram2023-03-192-6/+6
| |
* | Merge lines.loveKartik K. Agaram2023-03-183-20/+45
|\|
| * get typed in keystrokes to show on screen on iPadKartik K. Agaram2023-03-182-0/+21
| | | | | | | | Many thanks to Myte for helping test this!
| * extract a functionKartik K. Agaram2023-03-181-10/+14
| |
| * consistently use App names for methods everywhereKartik K. Agaram2023-03-182-9/+9
| |
| * move default file locationKartik K. Agaram2023-03-181-1/+1
| | | | | | | | | | | | | | | | This works better on mobile platforms while seeming about as useful anywhere else. I've verified that anyone who already edited a file will continue to use its path from settings.
* | Merge lines.loveKartik K. Agaram2023-03-171-2/+0
|\|
| * remove a stale issueKartik K. Agaram2023-03-171-2/+0
| |
* | Merge lines.loveKartik K. Agaram2023-03-177-909/+210
|\|
| * more bugfixKartik K. Agaram2023-03-173-6/+4
| | | | | | | | Don't crash on showing the log browser.
| * bugfixKartik K. Agaram2023-03-174-18/+72
| | | | | | | | Thanks Mikoláš Štrajt.
| * get rid of all bifold textKartik K. Agaram2023-03-174-874/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
| * bring a few things in sync between run and sourceKartik K. Agaram2023-03-173-8/+29
| |