These new PerformanceView classes are transforms over PerformanceViews.
The first is a cheap way to tell code that expects a performance to not
animate after all, and the other is a way to replace a view of a
performance going in one direction with a view of a performance going in
the other direction.
See also https://github.com/flutter/engine/issues/1708
Assert at build time that PageRoute route builders do not return null
widget trees.
Also very minor new code comments and code reorg to help make the heroes
patch easier to review.
(These are changes that are unrelated to Heroes but that were part of
the Heroes patch.)
The 0.2.1 release of the mojo package isn't actually compatible with Flutter
despite claiming to be a minor release. The real fix is to make Flutter
compatible with that release, but there are several yak shaves involved.
Introduces a new Widget that lays its child out, but does not render it.
Also, moves RenderOverflowBox to its own file since it has nothing to do
with proxy box really.
Provide a way to schedule a callback for immediately after the current
frame has been sent to the GPU thread. This is useful for times where
you want to immediately schedule yourself for another build or layout
because, for instance, you just displayed frame zero of an animation and
you want to use the metrics from that layout to set up the actual
animation to begin immediately, such that the very next frame is frame 1.
Adds a step to the updater to verify that the new .flx package is signed and
untampered.
Each .flx contains a signed manifest file. The manifest contains a SHA-256 hash
of the .flx contents. See bundle.dart for a description of the new .flx format.
It turns out that an AnimatedContainer with a BoxDecoration would
start animating every single time it was built, whether or not the
container's decoration had changed.
This widget is slow and not commonly used. The original reason we added it was
to colorize images, but now that feature is built into the image and background
image widgets.
Fixes#1646
