Hmm, gets me thinking computationally.
Dynalist is essentially an n-dimensional array of individual items.
Computers flatten n-dimensions of items to 1 dimension to store (along with every other data or instruction) as a string. Think {{{a1j,a2j},{a1k,a2k}},{{b1j,b2j},{b1k,b2k}}}. Somewhere deep in dynalist/workflowy’s database it is thought of this way.
With pixels you can flatten to 2d and see n-dimensions of items as a hierarchical list or as a mindmap or a tree. But not a table.
If you want a table, you can’t see any items deeper than 2 dimensions. One parent one child, in dynalist/workflowy terms. You leave deeper items out. Or you invent a holographic display and get to 3 dimensions of item cells, but not n. So a table is sort of a 2-array that lives in an item of the n-array and renders seperately.
So how would it expand to be edited, in the current WYSIWYG-less dynalist/workflowy?
You’d have to edit it in one of these two ways. Javascript would render it as a table when you click a non-table item.
renders when focus is lost to
Suddenly I wonder if @Piotr already implemented all this in their tampermonkey powerpack
I don’t actually have any desire to see tables in dynalist, I am just distracting myself at work with this thought puzzle.