about summary refs log tree commit diff stats
path: root/file.lua
Commit message (Collapse)AuthorAgeFilesLines
* bugfix: drawings in source editorKartik K. Agaram2023-05-301-5/+10
| | | | | | | | | | | | | | | Broken since 2022-09 X-( Scenario: * switch to source editor * draw a line * wait 3 seconds Before this commit the app would crash and then fail to restart until you deleted the created .lua file from save dir. This is not the first time I've confused Lua's files and LÖVE's droppedFile objects. Just never rely on multiple args in file:write().
* fix support for absolute paths in WindowsKartik K. Agaram2022-09-261-0/+1
|
* more correct absolute path detectionKartik K. Agaram2022-09-111-0/+17
|
* support drawings in the source editorKartik K. Agaram2022-09-051-1/+2
|
* dedup points while loading drawing from diskKartik K. Agaram2022-09-031-8/+8
|
* editing source code from within the appKartik K. Agaram2022-09-031-1/+0
| | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
* helper: file_existsKartik K. Agaram2022-08-231-0/+10
|
* have file API operate on state objectKartik K. Agaram2022-07-251-8/+7
|
* stop pretending globals are localKartik K. Agaram2022-07-111-2/+0
| | | | | One advantage of this approach: we don't end up with multiple lexical scopes containing duplicates of the same modules.
* better error messageKartik K. Agaram2022-07-051-0/+3
| | | | https://tildegit.org/akkartik/lines.love/issues/1
* test: autosave after any shapeKartik K. Agaram2022-06-141-1/+1
|
* avoid some string concatenationsKartik K. Agaram2022-06-101-6/+6
| | | | | | | | file:write can write multiple args one after another; no need to concatenate them first. I'm starting to pay attention to memory usage after the experience of turning off the JIT.
* ignore 'deleted' shapes when saving to diskKartik K. Agaram2022-05-301-0/+6
|
* typosKartik K. Agaram2022-05-251-2/+2
|
* couple more testsKartik K. Agaram2022-05-251-1/+1
| | | | Along with the App helpers needed for them.
* first successful pagedown test, first bug found by testKartik K. Agaram2022-05-231-3/+9
| | | | | | | | | | | | | | | | | | | 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.
* first test!Kartik K. Agaram2022-05-221-0/+56
|
* support for naming pointsKartik K. Agaram2022-05-211-1/+11
| | | | There's still an absence of affordance showing when you're in naming mode.
* bugfix: rectangles and squares are now savedKartik K. Agaram2022-05-211-2/+8
|
* several more modulesKartik K. Agaram2022-05-171-0/+88
This is probably not ideal; let's see how it goes..