Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Merge lines.love | Kartik K. Agaram | 2023-03-23 | 1 | -0/+9 |
|\ | |||||
| * | mouse wheel support | Kartik K. Agaram | 2023-03-23 | 1 | -0/+9 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2023-03-18 | 1 | -12/+30 |
|\| | |||||
| * | get typed in keystrokes to show on screen on iPad | Kartik K. Agaram | 2023-03-18 | 1 | -0/+14 |
| | | | | | | | | Many thanks to Myte for helping test this! | ||||
| * | extract a function | Kartik K. Agaram | 2023-03-18 | 1 | -10/+14 |
| | | |||||
| * | consistently use App names for methods everywhere | Kartik K. Agaram | 2023-03-18 | 1 | -2/+2 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2023-03-17 | 1 | -13/+1 |
|\| | |||||
| * | get rid of all bifold text | Kartik K. Agaram | 2023-03-17 | 1 | -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) | ||||
* | | Merge lines.love | Kartik K. Agaram | 2023-03-17 | 1 | -0/+1 |
|\| | |||||
| * | state validation in source editor as well | Kartik K. Agaram | 2023-03-17 | 1 | -0/+1 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2023-01-30 | 1 | -1/+0 |
|\| | |||||
| * | create a place for graphical log handlers | Kartik K. Agaram | 2023-01-30 | 1 | -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. | ||||
* | | Merge lines.love | Kartik K. Agaram | 2023-01-16 | 1 | -5/+0 |
|\| | |||||
| * | hoist out some common settings | Kartik K. Agaram | 2023-01-16 | 1 | -5/+0 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2023-01-01 | 1 | -1/+1 |
|\| | |||||
| * | typo | Kartik K. Agaram | 2023-01-01 | 1 | -1/+1 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2022-12-23 | 1 | -20/+20 |
|\| | |||||
| * | consistent names in a few more places | Kartik K. Agaram | 2022-12-23 | 1 | -4/+4 |
| | | |||||
| * | make love event names consistent | Kartik K. Agaram | 2022-12-23 | 1 | -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. | ||||
* | | Merge lines.love | Kartik K. Agaram | 2022-12-05 | 1 | -0/+2 |
|\| | |||||
| * | save state when clearing logs | Kartik K. Agaram | 2022-12-05 | 1 | -0/+2 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2022-12-05 | 1 | -0/+12 |
|\| | |||||
| * | source editor: clear logs | Kartik K. Agaram | 2022-12-05 | 1 | -0/+10 |
| | | |||||
| * | consume a mouse click when switching sides | Kartik K. Agaram | 2022-12-05 | 1 | -0/+2 |
| | | | | | | | | This way we can have the log side actually take focus sometimes. | ||||
* | | Merge lines.love | Kartik K. Agaram | 2022-09-19 | 1 | -23/+37 |
|\| | |||||
| * | migrate old settings, attempt #3 | Kartik K. Agaram | 2022-09-19 | 1 | -2/+8 |
| | | | | | | | | | | This time we have to handle absolute filenames. Now lines-polygon-experiment fork should merge successfully, at least. | ||||
| * | ugh, missed deleting an arg | Kartik K. Agaram | 2022-09-19 | 1 | -1/+1 |
| | | |||||
| * | handle missing cursors in settings | Kartik K. Agaram | 2022-09-19 | 1 | -3/+9 |
| | | |||||
| * | source: load cursor position from settings | Kartik K. Agaram | 2022-09-19 | 1 | -2/+5 |
| | | |||||
| * | source: no commandline args | Kartik K. Agaram | 2022-09-19 | 1 | -15/+4 |
| | | |||||
| * | source: remember cursor position of multiple files | Kartik K. Agaram | 2022-09-19 | 1 | -4/+12 |
| | | |||||
| * | source: support only relative paths within the app | Kartik K. Agaram | 2022-09-19 | 1 | -5/+2 |
| | | |||||
| * | bugfix: mouse clicks on file navigator above log browser side | Kartik K. Agaram | 2022-09-18 | 1 | -0/+5 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2022-09-18 | 1 | -4/+11 |
|\| | |||||
| * | delete a duplicate filename candidate | Kartik K. Agaram | 2022-09-18 | 1 | -1/+0 |
| | | |||||
| * | filter candidates in file navigator | Kartik K. Agaram | 2022-09-18 | 1 | -1/+4 |
| | | |||||
| * | hide editor cursor while in file navigator | Kartik K. Agaram | 2022-09-18 | 1 | -1/+1 |
| | | |||||
| * | bugfix: disable typing while file navigator is open | Kartik K. Agaram | 2022-09-18 | 1 | -0/+3 |
| | | |||||
| * | start showing source menu file navigation state graphically | Kartik K. Agaram | 2022-09-18 | 1 | -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 else | Kartik K. Agaram | 2022-09-17 | 1 | -1/+1 |
| | | | | | | | | This is stupid; I did it right in pensieve.love to begin with. | ||||
| * | easy way to make file switching more convenient | Kartik K. Agaram | 2022-09-17 | 1 | -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 prints | Kartik K. Agaram | 2022-09-17 | 1 | -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. | ||||
* | | Merge lines.love | Kartik K. Agaram | 2022-09-17 | 1 | -1/+3 |
|\| | |||||
| * | isolate some tests from settings | Kartik K. Agaram | 2022-09-17 | 1 | -1/+3 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2022-09-17 | 1 | -11/+14 |
|\| | |||||
| * | get rid of ugly side-effects in tests | Kartik K. Agaram | 2022-09-17 | 1 | -9/+9 |
| | | |||||
| * | bugfix: source margins when toggling log browser | Kartik K. Agaram | 2022-09-17 | 1 | -1/+4 |
| | | | | | | | | Running the tests now uglily resizes the window for a second or two. | ||||
| * | new test | Kartik K. Agaram | 2022-09-15 | 1 | -1/+1 |
| | | |||||
* | | Merge lines.love | Kartik K. Agaram | 2022-09-11 | 1 | -3/+2 |
|\| | |||||
| * | more correct absolute path detection | Kartik K. Agaram | 2022-09-11 | 1 | -3/+2 |
| | |