Bike Rows in a Table#

Editing happens one outline at a time, as it should. This is the other view of the same material: every row from every outline you have, in one table, filtered and grouped and sorted — so "everything due this week, wherever it lives" is a single question rather than a dozen files opened in turn.

It is FoldNotes' Database Views feature pointed at your Bike folder instead of your notes. Your outlines are read, never rearranged; nothing is written unless you ask for it.

Made on any device

Unlike a view of your notes, which is designed on macOS, a view of your Bike rows can be created and edited on iPhone and iPad too — filters and all.

What a view of rows contains#

Point FoldNotes at your folder of .bike outlines and a view can put every row from all of them into one table — then filter, group and sort it. Your outlines stay where they are, exactly as Bike wrote them.

A row arrives with everything it carries: its text, its status, its due date, priority, estimate and flag, any properties you have set on it, which outline it came from, and the path to it inside that outline. The last two are columns of their own — Outline and Path — so a table of a hundred rows from a dozen files still tells you where each one lives.

And a row is a way back into its outline, not just a line in a table: preview it to read it in context, or open it to edit it where it lives — on macOS, at the row itself. See Working a row below.

Filtering#

Filter offers the fields a row actually has, which is not a fixed list — it is built from your files each time:

Group	Fields
The row	its text, whether it is a task, whether it is one of Bike's log entries, which outline, the path inside it
Bike	Due, Estimate, Flagged, Priority, Status
FoldNotes	the date recorded when you tick a task, then each property you have defined
Found in your outlines	anything else present in the files — including attributes another app wrote, and Bike's own row timestamps when you have them switched on
Computed	see below

Each field offers the comparisons that suit it. A date can be overdue, today, this week, next week, before or after a date, or within a number of days. A property with a fixed set of values offers those values rather than a box to mistype into.

Leaving log entries out

If you use Bike's row logging, a table of work usually wants Log Entry is No. Log entries are ordinary outline content and are always shown by default — this only narrows what a given view lists.

Grouping#

Group by any of those fields, including one you are not showing as a column. Each group gets a heading with a count and a chevron to fold it away. Grouped by a date the groups run in date order; grouped by status they run in Bike's own order rather than alphabetically. Rows with no value for the thing you grouped by collect at the end under Unset.

Columns#

Choose which columns to show, drag to reorder them, and set their widths. The row's own text stays first and stays put while the rest scroll — it is what tells you which row you are reading.

Computed columns#

Values worked out from the row rather than stored on it:

Days Until Due — counts down, and goes negative once a task is late.
Days Since Completed — what did I finish this week. FoldNotes writes the date onto the row when you tick it, so the outline carries its own record.
Depth — how deeply the row is nested.
Your own — name it and pick any two dates, so "days from Completed to Due" tells you how early or late something finished.

A row that cannot answer shows nothing rather than a nought — a row with no due date has no number of days until it is due.

Export#

Export writes the rows exactly as you are looking at them, group headings included, as a CSV.

Working a row#

Selecting, previewing and opening a row works the same way here as in any other table, and the same on Mac and iPad: click or tap selects, Space or a long press previews, double-click, double-tap or Enter opens. A Bike row previews its whole outline scrolled to that row, and on macOS opening one lands you on the row itself.

The full model, including the keyboard, is in Database Views → Selecting, previewing and opening a row.

Opening a Bike row#

Opening a Bike row opens the outline the row lives in.

On macOS it opens at that row. The outline scrolls to it and the row flashes briefly, so you can see where you have landed. A row that has never been touched in Bike carries no identifier to aim at, so its outline opens at the top; every other row lands on the line.
On iPad and iPhone the outline opens at the top. Landing on the row needs the document's row map, which iOS builds only inside the editor — the preview is what shows you the row in place here.

Which outline is a row in?

Two columns answer that without opening anything: Outline, the file the row came from, and Path, where it sits inside that file as its chain of parent rows. Add either from the column picker.

What you can do where#

Unlike a view of your notes, a view of your Bike rows is authored on any device — the filters, the grouping, the columns and the computed columns are all editable on iPhone and iPad as well as the Mac.

	iPhone	iPad	macOS
Create a view of your rows
Edit its filter rules
Add computed columns
Export it as CSV
Preview a row	tap it	long-press, or `Space`	`Space`
Open a row's outline		opens at the top	opens at the row

Two rows there need a word of explanation:

Preview. On iPhone the table is a single-column list and a tap on a row previews it. On iPad and the Mac a tap or click selects instead, and the preview is a long press or Space — see Working a row.
Opening. Landing on the row itself needs the outline's row map, which only macOS builds outside the editor. On iPhone and iPad the preview is what shows you the row in its place.