So today @dvargas92495 brought up a really good question. Many are using SmartBlocks to not just build workflows for daily activities, but some are building very complex SmartBlocks with the JavaScript (connections to YouTube, GDrive, poetry and Shakespeare API's - wild stuff)
So while SmartBlocks has JS support, its not a primary goal. So his question was: why are people using it that way since you could just do roam/js. I have also wondered the same thing. I asked @shawnpmurphy8 (maker of famous attributes table extension) & he had strong opinions.
He said: Here is my thoughts on why folks are gravitating so heavily to SmartBlocks.
+ because it is simple
+ it is easy to develop/test as you go
+ it is easy to do hybrid... JS + SB COMMANDs + some general template stuff (indent / unindent etc.)
+ all in one place... don't have to think about whether to do a SB or whether to create a roam/js ext
+ roam/js gets messy. What is turned on, what isn't... how to nest it... is it conflicting with something else.
+ easy way to call the JS with the ;; menu and the SB buttons
+ basically overall the most important is low barrier to entry. No real friction.
+ it is like a ad-hoc sandboxed environment that allows for quick development/testing etc.
Now for why I think others are gravitating towards it (and not just reasons I like to use SmartBlocks):
+ first off roam42 community
+ people get responses quickly. so if someone has some crazy idea and don't really know how to code it, they can post to roam42 and know they'll get an answer pretty quickly.
+ I think it is easy for folks to conceptualize because of the "hybrid" ability of mixing SB engine / workflow / COMMANDs with sprinkling in JS too. So it is an attractive entry point for them to start learning JS.
+ Again, one place to do "all your cool stuff"... just type ;;
+ If you want to edit/modify something, you know where to go. # 42SmartBlock page and look at linked references to see all your smartblocks / "code".
• • •
Missing some Tweet in this thread? You can try to
force a refresh
@RoamResearch Starting a thread that we can build on (@CatoMinor3@AbhayPrasanna@gottalead and others) with some early feedback. First enjoying the new things, But while you are messing with the code, a few ideas.
RECOMMENDATION
.rm-title-display is title page. If it is a Daily Notes Page, it would be nice if there was an attribute indicating its a DNP. Lots of us modify based on context: standard page or DNP. class="rm-title-display rm-title-dnp" otherwise no attrib. (In sidebar as well)
PRAISE
Loving the concept of these classes representing structuee:
.rm-block-main
.rm-block-children
Live tweeting from the Roam impromptu zoom call with @Conaw. #roamcult
They want to make Roam very programmable. From easy to advanced, to simple extensions and more. Hope for lots of devs using Roam Depot in future.
Future of creators in Roam: very important that people can build off other peoples graphs. Multi-player, many contributing & sharing. Lower barrier to create very large content databases (even without a lot of tech knowledge). Want them to be build businesses of their work.
Coming to you Live from the Roam Hangouts with @cortexfutura Algorithm of Thought guru. Live tweeting his thoughts.
When @cortexfutura was asked about his background with note-taking software, he said “Been around the block” — no pun intended.
Demonstrating interfacing @zotero with Roam. I think this is a very popular concept for many researcher. He has designed a meta data export to make this happen. He will share his code. He has rolled his own solution to this problem.
Can't wait to try! Queries was one of those features when I started Roam I said to myself "this is not possible with notes, but it is!" Never thought anything other than search, but queries show a promise of a new dimension possibilities. I like new toys. #roamcult unite!
Man I am excited about this. Great work Team @RoamResearch. Query like tools are fundamental if the notes we write today will still be useful in 30 years. People often think the key feature of a note-taking app is full-text search. But that is only (small) part of the equation.
As your corpus of knowledge/information/writing/research grows to massive-multi-year database you need more advanced tools to get to what your looking for.
In this video @rjnestor discusses crucial concepts that every @RoamResearch user should know: INDENTATION. This is one of the best videos I have seen in a long time. #roamcult@roamresearch
2/ I am very thankful he put this together. Indentation is a key facet & concept from the art of outlining, not to be confused with “outlining” as a summary of something, rather outlining as in a document with structure, resembling a tree: (Parent/child/siblings relationships).
3/ This is not new & there is a fine legacy of Outliners (software for tree structure type documents.) Example: @davewiner 1979 and VisiText. Learn more about outlining at en.wikipedia.org/wiki/Outline_(… Roam goes step further as it is a graph db (trees connecting to trees endlessly)
2/ Example one: Project Xanadu (Structuring data, bidirectional links) first hypertext project in 1960 by @TheTedNelson
+ nonsequential writing (writing with block refs, no folders)
+ zippered lists (Roam Multiplayer)
+ tumblers: any part of a file to be referenced (Block UID)
3/ Example two: (1960's, 70's) Graph databases (Roam under the hood)
+ Nodes (Blocks)
+ Edges (Bidirectional links/block refs)
+ Properties (Creation/edit dates, user, block characteristics: open, closed, heading)