public static class FlutterFragment.NewEngineFragmentBuilder extends Object
FlutterFragment
with arguments
that correspond
to the values set on this NewEngineFragmentBuilder
.
To create a FlutterFragment
with default arguments
, invoke
FlutterFragment.createDefault()
.
Subclasses of FlutterFragment
that do not introduce any new arguments can use this
NewEngineFragmentBuilder
to construct instances of the subclass without subclassing
this NewEngineFragmentBuilder
.
MyFlutterFragment f = new FlutterFragment.NewEngineFragmentBuilder(MyFlutterFragment.class)
.someProperty(...)
.someOtherProperty(...)
.build<MyFlutterFragment>();
Subclasses of FlutterFragment
that introduce new arguments should subclass this
NewEngineFragmentBuilder
to add the new properties:
FlutterFragment
subclass has a no-arg constructor.NewEngineFragmentBuilder
.NewEngineFragmentBuilder
's no-arg constructor and invoke the
super constructor to set the FlutterFragment
subclass: public MyBuilder() {
super(MyFlutterFragment.class);
}
createArgs()
, call through to the super method,
then add the new properties as arguments in the Bundle
.NewEngineFragmentBuilder
subclass is defined, the FlutterFragment
subclass can be instantiated as follows.
MyFlutterFragment f = new MyBuilder()
.someExistingProperty(...)
.someNewProperty(...)
.build<MyFlutterFragment>();
Constructor and Description |
---|
NewEngineFragmentBuilder()
Constructs a
NewEngineFragmentBuilder that is configured to construct an instance of
FlutterFragment . |
NewEngineFragmentBuilder(Class<? extends FlutterFragment> subclass)
Constructs a
NewEngineFragmentBuilder that is configured to construct an instance of
subclass , which extends FlutterFragment . |
Modifier and Type | Method and Description |
---|---|
FlutterFragment.NewEngineFragmentBuilder |
appBundlePath(String appBundlePath)
The path to the app bundle which contains the Dart app to execute, defaults
to
FlutterMain.findAppBundlePath() |
<T extends FlutterFragment> |
build()
Constructs a new
FlutterFragment (or a subclass) that is configured based on
properties set on this Builder . |
protected Bundle |
createArgs()
Creates a
Bundle of arguments that are assigned to the new FlutterFragment . |
FlutterFragment.NewEngineFragmentBuilder |
dartEntrypoint(String dartEntrypoint)
The name of the initial Dart method to invoke, defaults to "main".
|
FlutterFragment.NewEngineFragmentBuilder |
flutterShellArgs(FlutterShellArgs shellArgs)
Any special configuration arguments for the Flutter engine
|
FlutterFragment.NewEngineFragmentBuilder |
initialRoute(String initialRoute)
The initial route that a Flutter app will render in this
FlutterFragment ,
defaults to "/". |
FlutterFragment.NewEngineFragmentBuilder |
renderMode(FlutterView.RenderMode renderMode)
Render Flutter either as a
FlutterView.RenderMode.surface or a
FlutterView.RenderMode.texture . |
FlutterFragment.NewEngineFragmentBuilder |
shouldAttachEngineToActivity(boolean shouldAttachEngineToActivity)
Whether or not this
FlutterFragment should automatically attach its
Activity as a control surface for its FlutterEngine . |
FlutterFragment.NewEngineFragmentBuilder |
transparencyMode(FlutterView.TransparencyMode transparencyMode)
Support a
FlutterView.TransparencyMode.transparent background within FlutterView ,
or force an FlutterView.TransparencyMode.opaque background. |
public NewEngineFragmentBuilder()
NewEngineFragmentBuilder
that is configured to construct an instance of
FlutterFragment
.public NewEngineFragmentBuilder(@NonNull Class<? extends FlutterFragment> subclass)
NewEngineFragmentBuilder
that is configured to construct an instance of
subclass
, which extends FlutterFragment
.@NonNull public FlutterFragment.NewEngineFragmentBuilder dartEntrypoint(@NonNull String dartEntrypoint)
@NonNull public FlutterFragment.NewEngineFragmentBuilder initialRoute(@NonNull String initialRoute)
FlutterFragment
,
defaults to "/".@NonNull public FlutterFragment.NewEngineFragmentBuilder appBundlePath(@NonNull String appBundlePath)
FlutterMain.findAppBundlePath()
@NonNull public FlutterFragment.NewEngineFragmentBuilder flutterShellArgs(@NonNull FlutterShellArgs shellArgs)
@NonNull public FlutterFragment.NewEngineFragmentBuilder renderMode(@NonNull FlutterView.RenderMode renderMode)
FlutterView.RenderMode.surface
or a
FlutterView.RenderMode.texture
. You should use surface
unless
you have a specific reason to use texture
. texture
comes with
a significant performance impact, but texture
can be displayed
beneath other Android View
s and animated, whereas surface
cannot.@NonNull public FlutterFragment.NewEngineFragmentBuilder transparencyMode(@NonNull FlutterView.TransparencyMode transparencyMode)
FlutterView.TransparencyMode.transparent
background within FlutterView
,
or force an FlutterView.TransparencyMode.opaque
background.
See FlutterView.TransparencyMode
for implications of this selection.
@NonNull public FlutterFragment.NewEngineFragmentBuilder shouldAttachEngineToActivity(boolean shouldAttachEngineToActivity)
FlutterFragment
should automatically attach its
Activity
as a control surface for its FlutterEngine
.
Control surfaces are used to provide Android resources and lifecycle events to
plugins that are attached to the FlutterEngine
. If shouldAttachEngineToActivity
is true then this FlutterFragment
will connect its FlutterEngine
to the
surrounding Activity
, along with any plugins that are registered with that
FlutterEngine
. This allows plugins to access the Activity
, as well as
receive Activity
-specific calls, e.g., Activity.onNewIntent(Intent)
.
If shouldAttachEngineToActivity
is false, then this FlutterFragment
will not
automatically manage the connection between its FlutterEngine
and the surrounding
Activity
. The Activity
will need to be manually connected to this
FlutterFragment
's FlutterEngine
by the app developer. See
FlutterEngine.getActivityControlSurface()
.
One reason that a developer might choose to manually manage the relationship between the
Activity
and FlutterEngine
is if the developer wants to move the
FlutterEngine
somewhere else. For example, a developer might want the
FlutterEngine
to outlive the surrounding Activity
so that it can be used
later in a different Activity
. To accomplish this, the FlutterEngine
will
need to be disconnected from the surrounding Activity
at an unusual time, preventing
this FlutterFragment
from correctly managing the relationship between the
FlutterEngine
and the surrounding Activity
.
Another reason that a developer might choose to manually manage the relationship between the
Activity
and FlutterEngine
is if the developer wants to prevent, or explicitly
control when the FlutterEngine
's plugins have access to the surrounding Activity
.
For example, imagine that this FlutterFragment
only takes up part of the screen and
the app developer wants to ensure that none of the Flutter plugins are able to manipulate
the surrounding Activity
. In this case, the developer would not want the
FlutterEngine
to have access to the Activity
, which can be accomplished by
setting shouldAttachEngineToActivity
to false
.
@NonNull public <T extends FlutterFragment> T build()
FlutterFragment
(or a subclass) that is configured based on
properties set on this Builder
.