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

	Commit message (Collapse)	Author	Age	Files	Lines
*	make love event names consistent	Kartik K. Agaram	2022-12-23	1	-2/+2
\| \| \| \| \|	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.
*	source editor: clear logs	Kartik K. Agaram	2022-12-05	1	-0/+1
\|
*	show partial items in the menu	Kartik K. Agaram	2022-11-06	1	-1/+1
\| \| \| \| \|	Seeing a partial item can nudge someone to try resizing the window and so learn about more shortcuts.
*	source: show files in MRU order	Kartik K. Agaram	2022-09-19	1	-4/+8
\| \| \| \| \|	I'm not going to save this MRU order across sessions for now. It's good enough to save cursor positions for individual files, I think.
*	extract a couple of functions	Kartik K. Agaram	2022-09-19	1	-13/+16
\|
*	filter candidates in file navigator	Kartik K. Agaram	2022-09-18	1	-0/+42
\|
*	support mouse clicks in file navigator	Kartik K. Agaram	2022-09-18	1	-2/+9
\|
*	start showing source menu file navigation state graphically	Kartik K. Agaram	2022-09-18	1	-5/+53
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I'm a bit leery of going down this road: - If there's a bug in how I render logs graphically that could be extremely misleading. Perhaps this suggests that the code to log things should be significantly simpler than the code that might be debugged. If writing the debug helper requires all my smarts I'm not smart enough to debug using the helper, etc. Given this idea, the fact that I'm copying production code into the logging helper is concerning. - There's a question of what code it's ok for logging helpers to depend on. This is an issue shared with tests. I often implicitly (and without meaning to) assume the presence of some well-tested helpers when writing tests. If those helpers ever break I can get into a rabbit hole of debugging. This problem might be even more insidious with logging helpers that will give me no indication when they break. Still and all, it's cool to see menus in my logs. Let's see if it's useful.
*	source: up/down in file navigator	Kartik K. Agaram	2022-09-18	1	-0/+68
\| \| \| \|	I'm starting to use logging, but it's still easier to print textual logs.
*	indent	Kartik K. Agaram	2022-09-18	1	-7/+7
\|
*	source: show all files in navigator	Kartik K. Agaram	2022-09-17	1	-5/+31
\| \| \| \| \|	We still don't have up/down arrow keys. And we still don't have the ability to filter filenames by typing.
*	rename	Kartik K. Agaram	2022-09-17	1	-3/+3
\|
*	delete some logs	Kartik K. Agaram	2022-09-17	1	-3/+0
\| \| \| \| \| \| \|	One open question is how to manage logs while drawing, since they can be extremely verbose. Neither tags nor depths seem like the right metaphor here, and that gives me pause that I perhaps don't see the full space of needs yet.
*	bugfix: never skip files in file navigator	Kartik K. Agaram	2022-09-17	1	-4/+3
\|
*	use existing local	Kartik K. Agaram	2022-09-17	1	-1/+1
\|
*	use a helper	Kartik K. Agaram	2022-09-17	1	-11/+7
\|
*	some debug prints	Kartik K. Agaram	2022-09-17	1	-0/+4
\| \| \| \| \| \|	I'm starting to edit the sources from within the app in ernest. First question: why does the file navigation menu skip some files? These prints answer the question.
*	switch shortcuts for bifold text	Kartik K. Agaram	2022-09-06	1	-3/+3
\| \| \| \| \| \|	I've been running out of ctrl+ shortcuts, and I just remembered my original idea to keep ctrl+ for drawings/mouse operations and alt+ for everything else.
*	support drawings in the source editor	Kartik K. Agaram	2022-09-05	1	-1/+1
\|
*	editing source code from within the app	Kartik K. Agaram	2022-09-03	1	-0/+100
	integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243