about summary refs log tree commit diff stats
path: root/source.lua
Commit message (Collapse)AuthorAgeFilesLines
* port inscript's bugfix to source editorKartik K. Agaram2023-06-041-0/+5
|
* hide cursor in log browser windowKartik K. Agaram2023-05-141-1/+1
|
* deemphasize the source editorKartik K. Agaram2023-04-091-0/+7
| | | | | | | | | This repo does not support freewheeling modification. It's a primitive to enable freewheeling modification in downstream forks. The source editor is a convenience, but it's a sharp tool and can easily leave the app in a broken state that requires dropping down to external tools (editor, file manager) to fix.
* switch source side to new screen-line-based renderKartik K. Agaram2023-04-031-3/+0
| | | | Also copy over the implementation of links from pensieve.love.
* App.width can no longer take a TextKartik K. Agaram2023-04-011-3/+1
| | | | | 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-011-8/+0
| | | | | | | | | | | | | 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
* experiment at avoiding some merge conflictsKartik K. Agaram2023-03-251-0/+14
| | | | https://merveilles.town/@akkartik/110084833821965708
* mouse wheel supportKartik K. Agaram2023-03-231-0/+9
|
* get typed in keystrokes to show on screen on iPadKartik K. Agaram2023-03-181-0/+14
| | | | 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-181-2/+2
|
* get rid of all bifold textKartik K. Agaram2023-03-171-13/+1
| | | | | | | | | | | | | | | 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)
* state validation in source editor as wellKartik K. Agaram2023-03-171-0/+1
|
* create a place for graphical log handlersKartik K. Agaram2023-01-301-1/+0
| | | | | | | | | | | | | Currently only used in pong.love, but let's keep the bad merge that had it broken since September from occurring again. To do that we'll be consistent across forks on where globals are initialized. I haven't appreciated the implications of main.lua for load order. log.lua comes first just because it's shared by both the main app and its 'source' editing environment. And it just so happens that source.lua was loading after log.lua resulting in the pong.love breakage. Now let's lean into that and enshrine that one should initialize log_render in log.lua.
* hoist out some common settingsKartik K. Agaram2023-01-161-5/+0
|
* typoKartik K. Agaram2023-01-011-1/+1
|
* consistent names in a few more placesKartik K. Agaram2022-12-231-4/+4
|
* make love event names consistentKartik K. Agaram2022-12-231-16/+16
| | | | | 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.
* save state when clearing logsKartik K. Agaram2022-12-051-0/+2
|
* source editor: clear logsKartik K. Agaram2022-12-051-0/+10
|
* consume a mouse click when switching sidesKartik K. Agaram2022-12-051-0/+2
| | | | This way we can have the log side actually take focus sometimes.
* migrate old settings, attempt #3Kartik K. Agaram2022-09-191-2/+8
| | | | | This time we have to handle absolute filenames. Now lines-polygon-experiment fork should merge successfully, at least.
* ugh, missed deleting an argKartik K. Agaram2022-09-191-1/+1
|
* handle missing cursors in settingsKartik K. Agaram2022-09-191-3/+9
|
* source: load cursor position from settingsKartik K. Agaram2022-09-191-2/+5
|
* source: no commandline argsKartik K. Agaram2022-09-191-15/+4
|
* source: remember cursor position of multiple filesKartik K. Agaram2022-09-191-4/+12
|
* source: support only relative paths within the appKartik K. Agaram2022-09-191-5/+2
|
* bugfix: mouse clicks on file navigator above log browser sideKartik K. Agaram2022-09-181-0/+5
|
* delete a duplicate filename candidateKartik K. Agaram2022-09-181-1/+0
|
* filter candidates in file navigatorKartik K. Agaram2022-09-181-1/+4
|
* hide editor cursor while in file navigatorKartik K. Agaram2022-09-181-1/+1
|
* bugfix: disable typing while file navigator is openKartik K. Agaram2022-09-181-0/+3
|
* start showing source menu file navigation state graphicallyKartik K. Agaram2022-09-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | I'm a bit leery of going down this road: - If there's a bug in how I render logs graphically that could be extremely misleading. Perhaps this suggests that the code to log things should be significantly simpler than the code that might be debugged. If writing the debug helper requires all my smarts I'm not smart enough to debug using the helper, etc. Given this idea, the fact that I'm copying production code into the logging helper is concerning. - There's a question of what code it's ok for logging helpers to depend on. This is an issue shared with tests. I often implicitly (and without meaning to) assume the presence of some well-tested helpers when writing tests. If those helpers ever break I can get into a rabbit hole of debugging. This problem might be even more insidious with logging helpers that will give me no indication when they break. Still and all, it's cool to see menus in my logs. Let's see if it's useful.
* bugfix: draw menu after everything elseKartik K. Agaram2022-09-171-1/+1
| | | | This is stupid; I did it right in pensieve.love to begin with.
* easy way to make file switching more convenientKartik K. Agaram2022-09-171-1/+0
| | | | | | | | In the fullness of time, I'll want to remember previous file, type to filter, etc. But for now just don't forget where you were. This is helpful because I'm often working on either the run side or the source side, and just starting out on the right side shaves off a lot of keypresses.
* some debug printsKartik K. Agaram2022-09-171-0/+2
| | | | | | I'm starting to edit the sources from within the app in ernest. First question: why does the file navigation menu skip some files? These prints answer the question.
* isolate some tests from settingsKartik K. Agaram2022-09-171-1/+3
|
* get rid of ugly side-effects in testsKartik K. Agaram2022-09-171-9/+9
|
* bugfix: source margins when toggling log browserKartik K. Agaram2022-09-171-1/+4
| | | | Running the tests now uglily resizes the window for a second or two.
* new testKartik K. Agaram2022-09-151-1/+1
|
* more correct absolute path detectionKartik K. Agaram2022-09-111-3/+2
|
* bugfix: path munging on WindowsKartik K. Agaram2022-09-101-2/+3
|
* support drawings in the source editorKartik K. Agaram2022-09-051-1/+1
|
* include some missing source filesKartik K. Agaram2022-09-051-0/+4
|
* set window title within each appKartik K. Agaram2022-09-031-0/+2
| | | | The main app shows the file being edited, but the programming environment does not.
* editing source code from within the appKartik K. Agaram2022-09-031-0/+358
integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-23 19:12:48 +0000