Instead, make Layer::Paint take a new PaintContext that has just exactly
the state that it needs, mirroring PrerollContext. Also, rename
PaintContext to CompositorContext because it holds the context for the
whole compositor.

This patch makes these files better match Google C++ style.

Also, add the engine lap time when running on Mojo.

We now compute the bounds for all container layers, including clips, and
use those bounds to tighten down our clips and save layers.

Related to https://github.com/domokit/mojo/issues/684

Roll dart to ccfd19bfd775c7cfc400aeda2c08fd821616cc82.

Previously we were applying opacity in a different way than Skia
expects. Now we use the exact pattern that Skia expects so that we hit
more optimizations inside SkRecordOptimize.

After this patch, we don't actually get the optimization because we
don't yet run SkRecordOptimize over the composited tree. A later patch
will actually cause us to run SkRecordOptimize.

Previously we would hold the layer tree until the we returned from Dart. Now we
send the layer tree to the rasterizer thread immediately.

Fixes #212

This patch maps glfw's keyboard input to the raw keyboard Mojo interface.

Dart invokes Start/StopTracing callbacks within the _setVMTimelineFlags service
method whenever the embedder timeline stream toggles on or off.  Flutter's
implementation of these callbacks was modifying the set of enabled streams,
which could override the intended behavior of _setVMTimelineFlags.

Start/StopTracing will now only control Flutter's embedder-specific log.

Also needed to change the Flutter engine's --trace-startup flag to set the
corresponding timeline stream flag on the Dart VM.

Fix crashes with LastPass, Now-on-Tap, DashLane

- [x] Add the path not the url to the dependencies

Fixes https://github.com/flutter/flutter/issues/3234

The PlatformView may not receive the surfaceDestroy notification before its
activity is destroyed (this was happening on the Android emulator).

If this happens, allow the PlatformView to be detached and have it release
its window during destruction.

This is unsafe and was crashing on the Android x64 emulator

This allows us to create a separate buildbot target.

This matters when building for armv7 where we need the 32-bit snapshotter on the host.

Dart has the tendency to call `exit()` on arbitrary threads. This causes
the assertion to trip. Since this should only happen when Dart is
running the shell in non-interactive mode, we leak the message loop
without proper shutdown.

We should never hit this path on iOS.

This patch cleans up the public Java interface to the Flutter engine. The code
that we intend to be re-usable is now in the io.flutter.view package. The two
public classes are:

 * FlutterMain, which controls initialization of the system, and
 * FlutterView, which is an Android view that hosts a Flutter app.

We'll need to interate on these interface over time, but at least these names
are more reasonable.

Do not show an assertion failure if Dart_FinalizeLoading returns an error while building a snapshot (#2584)

This might happen due to errors expected during development (e.g. a mistyped

Dart class name)

Dont destroy the platform message loop on the Mac because the message pump is still not collected when the embedder state goes away.

Required by the Dart dependency.

Add an HTTP server for exporting Flutter debug info and a request han…

Fixes #3095

Fix uri canonicalization in DartLibraryProviderFiles

Update jni.dart

Currently there's no good way of synchronizing layout changes with children in

Mozart. Previously we flickered when we were out of sync with our child. Now we

jank instead because that's a more acceptable artifact while we work on

improving Mozart.



Fixes https://github.com/flutter/flutter/issues/3024

Update thread names in the Dart timeline.

Particularly, add support for blur filters to implement backdrop blur effects.

Allow third-party services to listen to openURL on iOS (needed for Google Sign-In)

Use a source_set instead of a static_lib for iOS service dylibs (fixes symbol visibility issue)