| commit | 76c4db769d498b01ca5650ca97a35403d1a8b33d | [log] [tgz] |
|---|---|---|
| author | Gabriel Schine <thatguy@google.com> | Sat Jan 05 22:46:46 2019 -0800 |
| committer | Gabe Schine <thatguy@google.com> | Wed Jan 16 00:02:49 2019 +0000 |
| tree | 53caf4bd62d343007920291d54836f0798b00a9d | |
| parent | 0e585d990f7eb062f80d2c75a74a399b604a6148 [diff] |
[modular][storage] Don't store ModuleManifest in ModuleData. We stored ModuleManifest in ModuleData so that we could eventually send it to the StoryShell. Instead of doing that, we can look it up right before sending a Module's info to the StoryShell and thus remove a number of unnecessarily locations depending on ModuleFacetReader. Now, we always use the ModuleFacetReader to get our ModuleManifest. TEST=existing Change-Id: If7043b9663571241e28da7f8efd2a4f365a1f7a1
Peridot is a framework for composed, intelligent and distributed user experiences.
Applications not explicitly designed to interoperate (and possibly implemented in different programming languages) are ephemerally downloaded and dynamically composed to run in a shared context. The framework manages application lifecycle, resources and view hierarchy; and well as context and suggestion infrastructure.
State of Peridot experiences is transparently synchronized across user devices using a distributed offline-first storage system.