1/5 If you use LIVE PREVIEW or DAILY NOTES POPUP feature of Roam42, you will want to read this thread. I am making an important change to the Roam42 behavior. These features will be DISABLED by default. So if you want to use them, you just need to turn them on. #roamcult#roam42
2/5 To enable DAILY NOTES POPUP, simply add the following text to a block anywhere in your graph database and refresh the browser:
3/5 If you use LIVE PREVIEW feature of Roam42, just add the following text to any block in your graph database to enable the feature and refresh your browser:
5/5 These changes optimize performance of Roam42 & help with some of the sync issues @conaw mentioned a few days back. Finally I just want to thank @filipematossilv & the rest of the support @RoamResearch team for their help to Roam42. RR has great support engineers
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Roam backup terminologies & strategies. Recently in the Slack channels a discussion was started about backup. When you do an Export you have 3 options. Markdown, JSON and EDN. These terms can be confusing.
I want to provide an opinionated view & some basic guidance. #roamcult
2/ my basic strategy is to export in EDN & Markdown. These two formats give me (1) ability to fully restore my graph & (2) to restore the text of individual pages.
JSON is JavaScript Object Notation and mostly is intended for programmers & isn't as useful for a backup strategy.
3/ EDN (from the developer documentation) is Extensible Data Notation. A superset of edn is used by Clojure to represent programs, and it is used by Datomic and other applications as a data transfer format.
1/ Roam Milestone: Write API
Today is important day in Roam history. Many users will likely not be aware of it, but those building tools & integrations on Roam have lots reason for joy. Team RR is working on extending their API allowing for some important capabilities. #roamcult
2/ History lesson, the past: Roam already has a wonderful query API. This means we can read data from a graph database with relative ease. For the most part they don't hide anything from us. The database is truly exposed to the developer. It is powerful & is graph based.
3/ Roam is currently working on a large and important project: a new scalable database backend and also a new API (client and server side). However, this is a big task, one that should not be rushed, and one we should not put pressure on Roam to rush.
@tracyplaces Journalling sensei on a Friday Roam hangouts. Live tweeting some of her insights sprinkled with southern wisdom and good story telling. #roamcult#roamos
She was inspired to transition from paper to "digital" journalling via Roam by @MamanLunettes kid's YouTube videos. Violeta was so impressed by how her kids adapted Roam to their specific styles, different approaches, but Roam being a common denominator.
Young Sofia doing live demo of her approach to addressing her feelings with prompts. Using block refs to link to questions & then writing out what happened. Sofia is so articulate. Her prompts help her to have a conversation with herself to resolve the problem.
1/3 @Conaw the new CSS stuff is really great. The intentional surfacing of data elements and visual structure is going to be a big help as we move forward. I have one recommendation: Change the roam/css model to be like {{[[roam/js]]}}.
Recommendation: {{[[roam/css]]}}
2/3 The current one page model works very well, but gets difficult to manage as the number of customization grows since everything has to be on one page.
Second, it would be nice to prototype visual designs right in the context of what you are working on.
3/3 Additionally, it would give roam/js developers flexibility in providing UI customization.
So if we had {{[[roam/css]]}} that could be defined any where, this would be useful.
@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
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.)