text.love - Fork of lines.love without drawings; useful starting point for further forks

	Commit message (Collapse)	Author	Age	Files	Lines
*	line.y -> line_cache.starty in a few more places	Kartik K. Agaram	2022-07-27	1	-2/+2
\| \| \| \| \| \|	Disquieting that none of my tests caught these. On the other hand, I also haven't noticed any issues in practice. Perhaps cache invalidation is often unnecessary.
*	separate data structure for each line's cache data	Kartik K. Agaram	2022-07-17	1	-0/+11
\| \| \| \|	I have no idea what the performance implications of this are..
*	add state arg to a few functions	Kartik K. Agaram	2022-07-12	1	-24/+24
\| \| \| \| \| \| \|	- record_undo_event - undo_event - redo_event - snapshot
*	group all editor globals	Kartik K. Agaram	2022-07-12	1	-20/+20
\| \| \| \|	We're still accessing them through a global. But we'll change that next.
*	stop saving the entire file when modifying drawings	Kartik K. Agaram	2022-06-10	1	-4/+2
\| \| \| \|	Now we just disallow that entirely.
*	undo creating new drawings	Kartik K. Agaram	2022-06-10	1	-0/+5
\|
*	crisp font rendering	Kartik K. Agaram	2022-06-02	1	-1/+0
\|
*	more efficient undo/redo	Kartik K. Agaram	2022-06-02	1	-2/+35
\| \| \| \| \|	Now the bottleneck shifts to applying undo/redo in large files. But things should be snappy if you don't use the sluggish feature.
*	rename	Kartik K. Agaram	2022-06-02	1	-1/+1
\|
*	after much struggle, a brute-force undo	Kartik K. Agaram	2022-06-02	1	-0/+78
	Incredibly inefficient, but I don't yet know how to efficiently encode undo mutations that can span multiple lines. There seems to be one bug related to creating new drawings; they're not spawning events and undoing past drawing creation has some weird artifacts. Redo seems to consistently work, though.