@lotics/cli 0.321.113 → 0.321.114
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/src/cli.js +9 -6
- package/docs/design.md +1 -1
- package/package.json +1 -1
package/docs/design.md
CHANGED
|
@@ -491,7 +491,7 @@ an app (`app_architecture`).
|
|
|
491
491
|
|
|
492
492
|
#### Sections
|
|
493
493
|
|
|
494
|
-
A record is a head, its parts and at most one Side.
|
|
494
|
+
A record is a head, its parts and at most one Side. Its parts stack, one scroll with each headed; state `parts: "tabs"`, or a `tab` on a Section, to show one part at a time, and Sections stating one `tab` share a tab. A part is one area of the record's data a person comes to for its own job, like the tabs of a settings page; its related lists and field groups sit inside it under their headings. A status's stages are not areas: their acts stand at the foot of the rows they move, and a stage that holds something of its own — fields, blocks, acts, a note — is a Section inside `Steps`, one `Steps` to a record. State each
|
|
495
495
|
part whole for the work there: a field may stand in any number of parts, and a field an Act requires draws beside it
|
|
496
496
|
unstated. A stage that holds nothing needs no Section: the path draws it by its name. What a person needs in view at every part (who it is for, how to reach
|
|
497
497
|
them) goes in a Side: it leaves the head and stays on the rows; what only a stage's Act writes (an invoice's number,
|