The {{table}} model is revealing. At once reveals the strengths and weaknesses of the nested list as first-class citizen. You're reducing 2d to 1d, so you have to choose whether it will be row-dominant or column-dominant. At the moment they have row-dominant as a design choice.
-
-
The only thing that I suspect isn't quite a clean paradigm fit is the diagram feature. It overloads the basic nested blocks structure in opaque ways and I'm not sure I trust it yet.
Show this thread -
One simmering tension I can see here is whether Roam naturally wants to be a visual tool or a textual tool that's like a beefed up command-line paradigm. I think it wants to be both, but that means really pulling 2d visuals into the nested blockref paradigm properly
Show this thread -
Possibly one way to do that is build native viewport control which should be straightforward with html5/svg. Something like canned viewpoints. * {{view}} * xcenter ycenter * xspan y span This is going to get into css like attributes and declarative nocode though :(
Show this thread
End of conversation
New conversation -
-
-
You should also shop around the {{[[roam/js]]}}} stuff... e.g.,
@roamhacker ‘s Roam42 suite of little enhancements. Initial foray into the inevitable explosion of extensions that will ensue post-API release. -
I'm avoiding that for the moment, too unstable
- Show replies
New conversation -
-
-
daily notes is a must for me, though requires some patience and routine around it. still actively refining workflow though
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
"the only thing I haven't tried is daily notes" Roam: you don't have to precommit to structure, categories emerge bottom-up, just start writing in daily notes Venky: I've explored everything! (except not precommiting to structure)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.