OK quick @RoamResearch experiment with new, stabilized block-embeds and "attribute tables".
If you want to keep the attribute table columns in a particular order, this is how... (read on)
Usually the ordering moves the "most recently edited" entry to the far right column.
2/ This is a problem if you "need" the columns to be in a certain order (see below pic) because you can't edit them without reshuffling.
HOWEVER if you just put a block embed in the place you want, you can edit into that block embed with no change to table order
NOTE, though ->
3/ you can't directly edit within-table but you CAN click on the entry in an attr-table to bring it up in side window... you can edit its block-embed there, AND use it to navigate to wherever it "lives"
(thus, attr-tables become "indexes" ... one of their secret superpowers).
4/ correction/addendum (for completeness):
The leftmost column is always the attribute that you used to call up the table, e.g. {{attr-table::[[avocado]]}} will always have avocado as leftmost
The remaining columns are L-->R by "last-edited"
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Today is my first day of trying to really hone-down a "prediction-based workflow" and so far I'm really loving it.
The basic premise: at 8PM last night I gave myself fifteen minutes to run an imaginary preview of today, highlighting tasks and challenges I thought I'd face.
2/ Key - I also wrote all this down, to keep myself accountable
One way to conceptualize this is with the "managing self-creative self" split.
I was giving my "manager" fifteen minutes to "coach the team" last night. White board, chalk arrows the whole deal.
3/ This AM, I woke, slonked some vitamins and coffee, and the "prediction" was fresh in my mind.
Good to go!
The first and probably most interesting observation was that I then became acutely aware of exactly when I was at risk of diverging from the predicted plan.
@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 "::".
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".