diff options
| author | Laurenz <laurmaedje@gmail.com> | 2023-03-19 22:28:49 +0100 |
|---|---|---|
| committer | Laurenz <laurmaedje@gmail.com> | 2023-03-19 22:39:19 +0100 |
| commit | ab43bd802eafe33977a91893907e67553e099569 (patch) | |
| tree | af4dead92b143348f52e2e8f869df3f7dfd7322a /ARCHITECTURE.md | |
| parent | d6aaae0cea1e79eecd85dc94ab85b9ad8eff48e8 (diff) | |
Renaming and refactoring
Diffstat (limited to 'ARCHITECTURE.md')
| -rw-r--r-- | ARCHITECTURE.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md index 60254ba6..af48401d 100644 --- a/ARCHITECTURE.md +++ b/ARCHITECTURE.md @@ -94,10 +94,10 @@ items into a list that we want to layout, we don't realize the content within the list items just yet. This only happens lazily once the list items are layouted. -When we a have realized the content into a layoutable -node, we can then layout it into _regions,_ which describe the space into which -the content shall be layouted. Within these, a node is free to layout itself -as it sees fit, returning one `Frame` per region it wants to occupy. +When we a have realized the content into a layoutable element, we can then +layout it into _regions,_ which describe the space into which the content shall +be layouted. Within these, an element is free to layout itself as it sees fit, +returning one `Frame` per region it wants to occupy. **Introspection:** How content layouts (and realizes) may depend on how _it itself_ is layouted @@ -108,9 +108,9 @@ introspections stabilize after one or two iterations. However, some may never stabilize, so we give up after five attempts. **Incremental:** -Layout caching happens at the granularity of a node. This is important because -overall layout is the most expensive compilation phase, so we want to reuse as -much as possible. +Layout caching happens at the granularity of the element. This is important +because overall layout is the most expensive compilation phase, so we want to +reuse as much as possible. ## Export |
