pothi.love/0026-on.draw

on.draw = function()
	Global_state.button_handlers = {}
	if Global_state.root == nil then
		-- TODO: use surface for file picker as well
		draw_file_picker()
	else
		draw_surface()
	end
end
HUD indicator for failing tests Now you can tell something failed even if the test is out of view. I think this is the whole of the test-visualization feature -- EXCEPT that it doesn't quite work yet. Hitting <F4> currently causes lots of tests to fail. Failures are slowly non-deterministic. If I get a failure I'll tend to see the failure immediately after. But I might get up tomorrow and see everything passing. So I don't understand this, and it's possible this whole approach of juggling two copies of the App variable is totally busted. Even if we need to dramatically change how we run tests, though, the UI around tests is looking pretty good. 2023-01-24 00:38:48 +00:00			`on.draw = function()`
load in-memory data for a thread Nothing displayed yet. I need to convert threads to Surface nodes. 2023-06-19 04:10:20 +01:00			`Global_state.button_handlers = {}`
start rendering the initialized thread This required a little more restructuring of Global_state. It's not flat now, it's hierarchical again, but in a different way. after commit 3d89b8eb9d: post \- reply A \- reply B \- reply C after commit f9f7dab9b7: post reply A reply B reply C after this commit: row \- col \- indent 0 \- post \- col \- indent 1 \- reply A \- col \- indent 2 \- reply B \- col \- indent 1 \- reply C The indents are just invisible rectangles of different widths with 0 height. One change I had to make was to initialize_editor. Neither luaML and driver load lines from disk, but that's arguably the common scenario to support. 2023-06-21 03:35:32 +01:00			`if Global_state.root == nil then`
load in-memory data for a thread Nothing displayed yet. I need to convert threads to Surface nodes. 2023-06-19 04:10:20 +01:00			`-- TODO: use surface for file picker as well`
			`draw_file_picker()`
			`else`
			`draw_surface()`
HUD indicator for failing tests Now you can tell something failed even if the test is out of view. I think this is the whole of the test-visualization feature -- EXCEPT that it doesn't quite work yet. Hitting <F4> currently causes lots of tests to fail. Failures are slowly non-deterministic. If I get a failure I'll tend to see the failure immediately after. But I might get up tomorrow and see everything passing. So I don't understand this, and it's possible this whole approach of juggling two copies of the App variable is totally busted. Even if we need to dramatically change how we run tests, though, the UI around tests is looking pretty good. 2023-01-24 00:38:48 +00:00			`end`
start rendering the initialized thread This required a little more restructuring of Global_state. It's not flat now, it's hierarchical again, but in a different way. after commit 3d89b8eb9d: post \- reply A \- reply B \- reply C after commit f9f7dab9b7: post reply A reply B reply C after this commit: row \- col \- indent 0 \- post \- col \- indent 1 \- reply A \- col \- indent 2 \- reply B \- col \- indent 1 \- reply C The indents are just invisible rectangles of different widths with 0 height. One change I had to make was to initialize_editor. Neither luaML and driver load lines from disk, but that's arguably the common scenario to support. 2023-06-21 03:35:32 +01:00			`end`