| commit | 83ff6a9fc9bee036c35ededb81eedb53252f9aec | [log] [tgz] |
|---|---|---|
| author | David Murphy <dave.murphy@gmail.com> | Wed Oct 30 18:30:14 2019 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Oct 30 18:30:14 2019 +0000 |
| tree | ee55e704ab1ac846b0abfb9a3b9beb3f689acfb0 | |
| parent | 8542566d1b2cfd5841e35f88ea47460345532116 [diff] |
[story shell] Add layout logic for a 'workspace' archetype
Add a 'workspace' archetype, with the following roles:
primary: the main work element
auxiliary: a helper surface (optional)
header: the optional header surface (optional)
footer: the optional footer surface (optional)
Auxiliaries can also specify a preferred visual hierarchy with respect
to the primary: either 'child' - the default, coming after the parent,
or 'parent' - preceeding the primary.
Surfaces are matched to the layout according to
a) declaring in their metadata that they are participating in the
archetype and
b) the archetype_role they claim to be playing
Surfaces in specific roles can specify a preferred behavior for
multiplexing: e.g. three surfaces want to be 'auxiliary left', and the
most focused surface's expression wins (most recently added to story).
The behaviors are:
single: the surfaces are returned as a stack
toggle: the surfaces are returned as a toggleable, and the chrome to
achieve that is left to the presenter
copresent: the surfaces are laid out using the copresentation algorithm
_iff_ they declare a copresentation relation between
themselves and the parent (e.g. the primary). This is
subtle.
Add archetype_layout_test, for testing the different archetype
permutations
Test: fx run-host-tests composition_delegate_tests
Change-Id: If7b47a7b68db26deff26139e81e03533fc4dc24a
Topaz augments system functionality by implementing interfaces defined by underlying layers. Topaz contains four major categories of software: modules, agents, shells, and runners.
For example, modules include the dashboard, and runners include the Web, Dart, and Flutter runners.
Looking for something that used to be in this repository? The list below provides a code location and sha that can be used to checkout dead code that has been removed. Please note, it is unlikely the code will build or work correctly shas are provided for reference only. Code can be checked out with:
git checkout <sha> -- $FUCHSIA_DIR/<location>