@dvargas92495 has written jScript that restores value to
"attribute tables" - a partially developed feature that seemed promising - but had a flaw, rendering it hard-to-use.
That flaw seems to have been fixed -->
2. You can now use "Attribute Tables" to bring up auto-populating, SORTABLE tables, based on lines of metadata - equally-indented series of "attributes" (defined by syntax "foo double-colon", like this - "foo::").
What can you do with this?
Start with a simple habit-tracker.
3. Under any given daily note, affix the things you are tracking: (e.g.),
(NOTE: at the SAME level of indent, 1 below page title)
Exercise::
Reading::
Music::
and jot whatever you want into any of the fields following the "::".
Type: {{attr-table::[[exercise]]}} , and VOILA
4. (One cool/useful thing about this, by the way, is that,
Now that block-level templating is possible, using "block references",
You can have a standard "set" of columns, that you pull up whenever you need them - simply by using the "apply children as text" function.)
5. Then you basically have a self-populating table, that you can add to at any time, and from anywhere.
I'll post a fun example of this later, but first just wanted to 1st give the shoutout of thanks to @dvargas92495 for doing this.
Early adopters, do your thing!
Make magic!
6. Here is David's tweet in which he links to the javaScript that he wrote:
OK, people get ready, I'm going to assay a lightning-summary of @RobertHaisfield 's webinar on further unlocking the powers of {{query}}ing in @RoamResearch .
Here are a few of the key things that I gleaned.
1. Querying allows you to have "conversations with your past self."
2. To make those conversations optimally useful, you will want to learn to be artful about what hashtags you choose, and also how you arrange those hashtags.
3. One heuristic to use as you make these decisions is, "under what conditions will future-me want to find this?"
4. It's also worth taking a moment to familiarize yourself with the different behaviors of a query under these different conditions:
a) when hashtags are all inline in the same block,
b) when they are parent-child relationship,
c) and when they are arranged as "siblings".
I had to completely stop writing "to-do"s for a while, before realizing how completely awful I was at it.
What I now appreciate: every commitment has to fit into the broader scope of my intentions, with a care equal to a craftsman fitting a single tile into an epic mosaic.
2/ This is a very Alexandrian idea (Christopher, of course) - and it raises an underexplored question -
Why aren't we applying Alexandrian design principles to the imaginary structures that we create in time, as well as space?
3/ In a sense, computer programmers, among Alexander's earliest devotees, were fastest to see this - because what is a computer program, if not a kind of design that is specifically created to unfold in time?
It's also true that Alexander, himself, is reverent towards time.
3/ the broader project that interests me is creating systems that reconcile Kairos with Chronos, (we need both), but allow and encourage Kairos to be the primary shaper, and not the other way around.
In the long run, I think this will turn Google Calendar upside down;