Query imports for user scipts in networked #toolsforthought . Yay or nay? Is it worth monkeying with javascript to allow user code to behave in a more networked fashion? @Conaw @codexeditor @RoamResearch (Using Roam-like query syntax at the moment)

And editing annotations is actually reasonably quick with keyboard shortcuts despite my slow typing speed.

One big advantage of using annotations instead of markup is that you can place links in blocks of code. You also get to avoid the mode differences between blocks with focus and blocks without focus. There's no markup display/hide. @Conaw @codexeditor #toolsforthought

Use Spaces as code modules with a literate programming interface (if you're so inclined). #toolsforthought

Using #sinuous components with `import` and `export` #toolsforthought. At the moment, this only works to produce output between blocks. But eventually, you'll be able to use the widgets you write in conjunction with slash commands within your blocks.

Starting to add user-programming #toolsforthought

You can now edit what an annotation points to. One step closer to being usable! #toolsforthought

Messing with previews and highlighting all annotations that point to the same content on hover. #toolsforthought

Here's a useless notebook implementation in roam/js @RoamResearch

Some hotkey navigation (zoom in, zoom out, follow the link under the cursor, and the like):

Blocks meet annotations

#roamcult, @RoamResearch, & @Conaw, have you seen @codexeditor 's SPEEDy editor? This thing is amazing: piped.video/watch?v=-G8YmRJ_… . There's an interesting conversation to be had here regarding resolution (block entity vs text annotation). 1/12