Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@xster
Copy link
Member

@xster xster commented Jun 16, 2019

No description provided.

* <p>
* A custom Dart entrypoint or Flutter route can also be specified by using an existing {@link
* FlutterEngine}. A {@link FlutterEngine} can be provided by implementing the
* {@link #getFlutterEngine} method. Creating a {@link FlutterEngine} before showing a {@code
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should probably hold off with this explanation until my current PR is merged. I've renamed this method to provideFlutterEngine because it turns out there were 2 methods called getFlutterEngine for 2 different purposes. I've also made FlutterActivity implement FlutterEngineProvider so that devs no longer have to worry about adding that interface themselves - instead they can just override provideFlutterEngine in their subclass.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ya sure, let's get your PR through first.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@matthew-carroll @xster is the PR in question now merged?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the PR was merged. There have also been other non-trivial changes to FlutterActivity so its probably worth re-checking all language in this PR against the latest.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, I can revise this one at some point this week.

@xster xster requested a review from matthew-carroll August 14, 2019 22:05
Copy link
Contributor

@matthew-carroll matthew-carroll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for Android doc

@xster xster merged commit 5e155c6 into flutter:master Aug 14, 2019
@xster xster deleted the doc-1 branch August 14, 2019 23:35
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Aug 15, 2019
engine-flutter-autoroll added a commit to flutter/flutter that referenced this pull request Aug 15, 2019
[email protected]:flutter/engine.git/compare/c5e30553cd1a...5e155c6

git log c5e3055..5e155c6 --no-merges --oneline
2019-08-14 [email protected] some drive-by docs while I was reading the embedding classes (flutter/engine#9341)
2019-08-14 [email protected] Initialize the engine in the running state to match the animator's default state (flutter/engine#11011)
2019-08-14 [email protected] Trace RasterCacheResult::Draw (flutter/engine#11004)
2019-08-14 [email protected] Rename macOS FLE* classes to Flutter* (flutter/engine#11010)
2019-08-14 [email protected] [Windows] Alternative Windows shell platform implementation (flutter/engine#9835)

The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff ([email protected]), and stop
the roller if necessary.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants