about summary refs log tree commit diff stats
path: root/app.lua
Commit message (Collapse)AuthorAgeFilesLines
* wait, fix testsKartik K. Agaram2023-05-301-9/+19
| | | | | We had this problem because our test fakes were out of sync with reality. And just in the source app.
* primitives for writing testsKartik K. Agaram2023-04-111-1/+1
|
* include a brief reference enabling many useful appsKartik K. Agaram2023-04-091-12/+0
|
* avoid saving fragments in linesKartik K. Agaram2023-04-011-1/+1
| | | | | | | Now we render lines one screen line at a time rather than one word at a time. I can't port the source side just yet; I need to fix hyperlinks first..
* show count of test failuresKartik K. Agaram2023-04-011-1/+1
|
* no more Text allocationsKartik K. Agaram2023-04-011-9/+0
| | | | Is it just my imagination, or does the app feel lighter and more fluffy?
* App.width can no longer take a TextKartik K. Agaram2023-04-011-10/+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-1/+9
| | | | | | | | | | | | | 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
* bugfix: naming pointsKartik K. Agaram2023-03-261-1/+3
|
* remove a conditionKartik K. Agaram2023-01-221-1/+1
|
* clean up a printKartik K. Agaram2023-01-201-1/+0
|
* deduce test names on failuresKartik K. Agaram2023-01-201-1/+14
|
* link to default love.run for comparisonKartik K. Agaram2023-01-201-2/+2
|
* make love event names consistentKartik K. Agaram2022-12-231-7/+7
| | | | | 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.
* undo an ancient hack; be an idiomatic LÖVE appKartik K. Agaram2022-11-271-3/+3
|
* support mouse clicks in file navigatorKartik K. Agaram2022-09-181-0/+4
|
* get rid of ugly side-effects in testsKartik K. Agaram2022-09-171-0/+25
|
* 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.
* editing source code from within the appKartik K. Agaram2022-09-031-6/+23
| | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
* 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.
* distinguish consistently between mouse buttons and other buttonsKartik K. Agaram2022-08-231-17/+17
|
* reclaim a couple more functions after testsKartik K. Agaram2022-08-191-0/+2
|
* hardcode some assumptions about how this app uses loveKartik K. Agaram2022-08-061-18/+11
|
* formattingKartik K. Agaram2022-07-161-2/+2
|
* a more radical attempt at ignoring nil y'sKartik K. Agaram2022-07-131-3/+5
|
* .Kartik K. Agaram2022-07-121-0/+2
|
* make colors easier to editKartik K. Agaram2022-07-111-0/+4
|
* bugfix: typing should delete highlighted textKartik K. Agaram2022-06-201-2/+7
| | | | The test harness now also mimics real usage more precisely.
* autosave slightly less aggressivelyKartik K. Agaram2022-06-171-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 shapeKartik K. Agaram2022-06-141-2/+16
|
* new testKartik K. Agaram2022-06-121-0/+9
| | | | | For commit e4e12c77ad which fixed a regression caused by commit 24a0d162ef.
* override mouse state lookups in testsKartik K. Agaram2022-06-121-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 executedKartik K. Agaram2022-06-121-0/+4
|
* redundant checkKartik K. Agaram2022-06-121-4/+2
|
* 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
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-20 15:30:40 +0000