Navigation during table creation is a bit unintuitive
No way to see whether a bullet (a cell) has children
Can’t double click to automatically resize columns to fit width
Sometimes the column width expands to fit as I type new text, other times it does not
Perhaps a bit too easy to overwrite existing content in a cell by dragging another cell on top of it
Conclusion: My first impression is that this is a niche tool, but I appreciate having a new display. I have a feeling others will find this very useful.
I’d like to see the table transposed (1st level child nodes = lines in table)
Context of each record relies on the order of 2nd level children. When the view changes to board, bullet list, or dashboard the context changes (to list of the same property x all objects). Also the way it is now it looks pretty much like a board (see the s/s below)
Do I miss any advantage of this setup?
Additionally: It would be great to have in/export to/from CSV
Nicely presented, @smallgrip6167 . There was a lively debate about this topic on the Workflowy User Group slack channel. This morning, Phil from Workflowy posted:
Thanks for all the feedback on Tables, and as a result we’re shifting from a columns-first approach to row-first.
Why? We went back and forth on this and columns-first was the fastest way to get something real in your hands. Your insights about data integrity made it clear that row-first was the right approach.
As a result, existing tables are likely to be fragile, so, for now, we’d recommend not building anything important with them. More soon.
Maybe? Or rely on folks like me who check the slack group often. I go there in part because I enjoy Workflowy and the community. I also go there for a healthier break: I open the slack page so that I don’t open Reddit.
Just having tables as superficial formating is a huge step that im very thankfull for
Definitely row-first is the way to go, and nodes having both row and column association is the end goal
A big quality of life improvement would be having copied tables being pasted into WF as tables - but I realise this is probably way easier said than done and therefore something that will happen later in the process
