about summary refs log tree commit diff stats
path: root/app.lua
Commit message (Collapse)AuthorAgeFilesLines
* select text with shift + mouseclickKartik K. Agaram2022-06-041-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 dragKartik K. Agaram2022-06-031-0/+6
| | | | Doesn't yet highlight while dragging.
* test harness now supports copy/pasteKartik K. Agaram2022-06-021-0/+10
|
* update some App framework docsKartik K. Agaram2022-05-311-5/+5
|
* go through App in a couple more placesKartik K. Agaram2022-05-291-4/+4
|
* test and App helper for mouse clicksKartik K. Agaram2022-05-251-0/+6
|
* no, make sure to compute line width after screen dimensionsKartik K. Agaram2022-05-251-1/+2
|
* couple more testsKartik K. Agaram2022-05-251-0/+18
| | | | Along with the App helpers needed for them.
* one bug I've repeatedly run into while testing with Moby DickKartik K. Agaram2022-05-231-0/+1
| | | | https://www.hogbaysoftware.com/posts/moby-dick-workout
* disable all debug printsKartik K. Agaram2022-05-231-1/+1
|
* snapshotKartik K. Agaram2022-05-231-1/+8
| | | | Why the fuck is this so fucking hard?
* bugfix: don't rely on Screen_bottom1 while scrollingKartik K. Agaram2022-05-231-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 testKartik K. Agaram2022-05-231-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 implicationKartik K. Agaram2022-05-221-0/+3
|
* basic test-enabled frameworkKartik K. Agaram2022-05-221-5/+184
| | | | | Tests still have a lot of side-effects on the real screen. We'll gradually clean those up.
* renameKartik K. Agaram2022-05-221-0/+37