| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | undo an ancient hack; be an idiomatic LÖVE app | Kartik K. Agaram | 2022-11-27 | 1 | -3/+3 |
| | | |||||
| * | support mouse clicks in file navigator | Kartik K. Agaram | 2022-09-18 | 1 | -0/+4 |
| | | |||||
| * | get rid of ugly side-effects in tests | Kartik K. Agaram | 2022-09-17 | 1 | -0/+25 |
| | | |||||
| * | bugfix: save modified files in save directory | Kartik K. Agaram | 2022-09-05 | 1 | -2/+26 |
| | | | | | | | scenario: open app from .love file, press ctrl+e Before this change the source file showed up empty. | ||||
| * | editing source code from within the app | Kartik K. Agaram | 2022-09-03 | 1 | -6/+23 |
| | | | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243 | ||||
| * | make App.open_for_* look more like io.open | Kartik K. Agaram | 2022-08-23 | 1 | -7/+9 |
| | | | | | Now missing files will result in similar behavior: nil file handles. | ||||
| * | distinguish consistently between mouse buttons and other buttons | Kartik K. Agaram | 2022-08-23 | 1 | -17/+17 |
| | | |||||
| * | reclaim a couple more functions after tests | Kartik K. Agaram | 2022-08-19 | 1 | -0/+2 |
| | | |||||
| * | hardcode some assumptions about how this app uses love | Kartik K. Agaram | 2022-08-06 | 1 | -18/+11 |
| | | |||||
| * | formatting | Kartik K. Agaram | 2022-07-16 | 1 | -2/+2 |
| | | |||||
| * | a more radical attempt at ignoring nil y's | Kartik K. Agaram | 2022-07-13 | 1 | -3/+5 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-07-12 | 1 | -0/+2 |
| | | |||||
| * | make colors easier to edit | Kartik K. Agaram | 2022-07-11 | 1 | -0/+4 |
| | | |||||
| * | bugfix: typing should delete highlighted text | Kartik K. Agaram | 2022-06-20 | 1 | -2/+7 |
| | | | | | The test harness now also mimics real usage more precisely. | ||||
| * | autosave slightly less aggressively | Kartik K. Agaram | 2022-06-17 | 1 | -0/+13 |
| | | | | | | | | | It might reduce wear and tear on disk, and losing 3 seconds of data doesn't feel catastrophic (short of a C-z rampage). Thanks to the love2d.org community for the suggestion: https://love2d.org/forums/viewtopic.php?f=14&t=93173 | ||||
| * | test: autosave after any shape | Kartik K. Agaram | 2022-06-14 | 1 | -2/+16 |
| | | |||||
| * | new test | Kartik K. Agaram | 2022-06-12 | 1 | -0/+9 |
| | | | | | | For commit e4e12c77ad which fixed a regression caused by commit 24a0d162ef. | ||||
| * | override mouse state lookups in tests | Kartik K. Agaram | 2022-06-12 | 1 | -10/+47 |
| | | | | | | | | If I'd had this stuff in my test harness earlier, two recent commits would have failed tests and given me early warning: ff88238ff1 ff88a2a927 | ||||
| * | delete all tests once they've executed | Kartik K. Agaram | 2022-06-12 | 1 | -0/+4 |
| | | |||||
| * | redundant check | Kartik K. Agaram | 2022-06-12 | 1 | -4/+2 |
| | | |||||
| * | select text with shift + mouseclick | Kartik K. Agaram | 2022-06-04 | 1 | -0/+16 |
| | | | | | | | | It's still a bit simple-minded. Most software will keep the first bound fixed and move the second. Lines currently has the bounds in a queue of sorts. But I have a test to indicate the behavior that is definitely desired. We'll see if we need it to get more complex. | ||||
| * | select text using mouse drag | Kartik K. Agaram | 2022-06-03 | 1 | -0/+6 |
| | | | | | Doesn't yet highlight while dragging. | ||||
| * | test harness now supports copy/paste | Kartik K. Agaram | 2022-06-02 | 1 | -0/+10 |
| | | |||||
| * | update some App framework docs | Kartik K. Agaram | 2022-05-31 | 1 | -5/+5 |
| | | |||||
| * | go through App in a couple more places | Kartik K. Agaram | 2022-05-29 | 1 | -4/+4 |
| | | |||||
| * | test and App helper for mouse clicks | Kartik K. Agaram | 2022-05-25 | 1 | -0/+6 |
| | | |||||
| * | no, make sure to compute line width after screen dimensions | Kartik K. Agaram | 2022-05-25 | 1 | -1/+2 |
| | | |||||
| * | couple more tests | Kartik K. Agaram | 2022-05-25 | 1 | -0/+18 |
| | | | | | Along with the App helpers needed for them. | ||||
| * | one bug I've repeatedly run into while testing with Moby Dick | Kartik K. Agaram | 2022-05-23 | 1 | -0/+1 |
| | | | | | https://www.hogbaysoftware.com/posts/moby-dick-workout | ||||
| * | disable all debug prints | Kartik K. Agaram | 2022-05-23 | 1 | -1/+1 |
| | | |||||
| * | snapshot | Kartik K. Agaram | 2022-05-23 | 1 | -1/+8 |
| | | | | | Why the fuck is this so fucking hard? | ||||
| * | bugfix: don't rely on Screen_bottom1 while scrolling | Kartik K. Agaram | 2022-05-23 | 1 | -1/+1 |
| | | | | | | Setting up the test just right to test the thing I want to test was a rube goldberg machine of constants. | ||||
| * | first successful pagedown test, first bug found by test | Kartik K. Agaram | 2022-05-23 | 1 | -1/+11 |
| | | | | | | | | | | | | | | | | | | | | I also really need to rethink how people debug my programs. My approach of inserting and deleting print() takes a lot of commitment. I need my old trace-based whitebox testing idea. However, in my past projects I never did figure out a good framework for tweaking how verbose a trace to emit. Perhaps that's too many knobs. Perhaps we just need a way to run a single test with the most verbose trace possible. Then it's just a matter of having the trace tell a coherent story? But even if the trace stays out of program output in that situation, it's still in the programmer's face in the _code_. Ugh. Current plan: ship program with maximum tests and zero commented-out prints. If you want to debug, insert prints. This is better than previous, text-mode, projects just by virtue of the stdout channel being dedicated to debug stuff. | ||||
| * | one more implication | Kartik K. Agaram | 2022-05-22 | 1 | -0/+3 |
| | | |||||
| * | basic test-enabled framework | Kartik K. Agaram | 2022-05-22 | 1 | -5/+184 |
| | | | | | | Tests still have a lot of side-effects on the real screen. We'll gradually clean those up. | ||||
| * | rename | Kartik K. Agaram | 2022-05-22 | 1 | -0/+37 |