about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* start showing source menu file navigation state graphicallyKartik K. Agaram2022-09-182-5/+54
| | | | | | | | | | | | | | | | | | | | | | 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.
* source: up/down in file navigatorKartik K. Agaram2022-09-181-0/+68
| | | | I'm starting to use logging, but it's still easier to print textual logs.
* indentKartik K. Agaram2022-09-181-7/+7
|
* source: show all files in navigatorKartik K. Agaram2022-09-171-5/+31
| | | | | We still don't have up/down arrow keys. And we still don't have the ability to filter filenames by typing.
* 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.
* renameKartik K. Agaram2022-09-171-3/+3
|
* delete some logsKartik K. Agaram2022-09-171-3/+0
| | | | | | | One open question is how to manage logs while drawing, since they can be extremely verbose. Neither tags nor depths seem like the right metaphor here, and that gives me pause that I perhaps don't see the full space of needs yet.
* yet another bugfix in log parsingKartik K. Agaram2022-09-171-2/+6
|
* bugfix: perform matches in the right orderKartik K. Agaram2022-09-171-2/+2
|
* 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.
* bugfix: never skip files in file navigatorKartik K. Agaram2022-09-171-4/+3
|
* use existing localKartik K. Agaram2022-09-171-1/+1
|
* use a helperKartik K. Agaram2022-09-171-11/+7
|
* bugfix: log filenames can have 2 formatsKartik K. Agaram2022-09-171-1/+4
|
* some debug printsKartik K. Agaram2022-09-174-0/+8
| | | | | | 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-172-9/+34
|
* bugfix: source margins when toggling log browserKartik K. Agaram2022-09-172-1/+65
| | | | Running the tests now uglily resizes the window for a second or two.
* .Kartik K. Agaram2022-09-171-1/+2
|
* .Kartik K. Agaram2022-09-151-1/+1
|
* new testKartik K. Agaram2022-09-153-2/+21
|
* more correct absolute path detectionKartik K. Agaram2022-09-114-6/+38
|
* bugfix: path munging on WindowsKartik K. Agaram2022-09-104-6/+8
|
* self-documenting 0 Test_right_marginKartik K. Agaram2022-09-074-8/+16
|
* one issue lessKartik K. Agaram2022-09-061-3/+1
| | | | | Selecting text is also almost done. I just need to figure out what to do with bifold text.
* switch shortcuts for bifold textKartik K. Agaram2022-09-062-5/+5
| | | | | | I've been running out of ctrl+ shortcuts, and I just remembered my original idea to keep ctrl+ for drawings/mouse operations and alt+ for everything else.
* support selections in the source editorKartik K. Agaram2022-09-066-6/+708
| | | | | I've only tested side A so far, and included a statement of how I want side B to behave.
* support hyperlinks in the source editorKartik K. Agaram2022-09-053-0/+40
| | | | Integrated from the pensieve fork.
* bugfix: save modified files in save directoryKartik K. Agaram2022-09-051-2/+26
| | | | | | scenario: open app from .love file, press ctrl+e Before this change the source file showed up empty.
* .Kartik K. Agaram2022-09-051-1/+3
|
* support drawings in the source editorKartik K. Agaram2022-09-0511-128/+545
|
* include some missing source filesKartik K. Agaram2022-09-051-0/+4
|
* bugfix: cold startKartik K. Agaram2022-09-031-0/+3
|
* dedup points while loading drawing from diskKartik K. Agaram2022-09-032-13/+8
|
* set window title within each appKartik K. Agaram2022-09-032-2/+2
| | | | The main app shows the file being edited, but the programming environment does not.
* remember window positions across restart/ctrl+eKartik K. Agaram2022-09-031-3/+5
|
* duplicateKartik K. Agaram2022-09-031-10/+0
|
* bugfix: window titleKartik K. Agaram2022-09-031-2/+2
|
* editing source code from within the appKartik K. Agaram2022-09-0322-203/+5164
| | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
* bugfix: propagate mouse press if any button wouldKartik K. Agaram2022-08-241-4/+6
| | | | | Before this commit I was propagating press events only if _all_ buttons would.
* infrastructure for caching LÖVE text objectsKartik K. Agaram2022-08-243-6/+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
|
* helper: file_existsKartik K. Agaram2022-08-231-0/+10
|
* make App.open_for_* look more like io.openKartik K. Agaram2022-08-231-7/+9
| | | | Now missing files will result in similar behavior: nil file handles.
* pass all button params to the iconKartik K. Agaram2022-08-232-2/+3
|
* allow buttons to nest as wellKartik K. Agaram2022-08-231-2/+11
|
* flip return value of button handlersKartik K. Agaram2022-08-232-6/+4
| | | | | | This is compatible with Javascript, and it also seems like a better default; when people forget to think about return values in click handlers, they should be consumed.
* stop putting button state in a globalKartik K. Agaram2022-08-233-9/+13
| | | | | | | | | | | | | | | | Symptom: a test (test_click_to_create_drawing) started randomly failing after I inserted a `return` 2 commits ago. Cause: my tests call edit.draw, but button handlers only get cleared in app.draw. So my tests weren't clearing button handlers, and every call to edit.draw was accumulating states. Still unclear why those were going to different state objects after the `return`, but anyway. I'm not going to understand every last thing that happens when things go wrong, just guarantee they can't go wrong. And the way to do that is to decentralize button handlers to each state that receives them. The State object in buttons.lua doesn't have to be Editor_state. It just has to be some table that provides a Schelling Point for shared state.
* improve explanation for buttonsKartik K. Agaram2022-08-231-1/+4
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-07 23:53:15 +0000