Support lightweight engines for desktop shells #95076
Labels
a: desktop
Running on desktop
c: new feature
Nothing broken; request for a new capability
c: proposal
A detailed proposal for a change to Flutter
engine
flutter/engine repository. See also e: labels.
fyi-linux
For the attention of the Linux platform team
fyi-windows
For the attention of the Windows platform team
P3
Issues that are less important to the Flutter project
platform-linux
Building on or for Linux specifically
platform-mac
Building on or for macOS specifically
platform-windows
Building on or for Windows specifically
team-macos
Owned by the macOS platform team
triaged-macos
Triaged by the macOS platform team
Comments
ColdPaleLight
added
a: desktop
|
cc @cbracken |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
We are currently working on multi-window support, which will enable you to render to multiple views using a single Dart isolate & Flutter engine. You can track our progress here: https://github.com/orgs/flutter/projects/39 |
cbracken
added
fyi-macos
|
The |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the official multi-window solution has not yet been implemented, the current workaround in the community is that one window corresponds to one engine，such as native shell : https://nativeshell.dev/
So if the desktop can also support lightweight engines like mobile, we can improve window opening performance and reduce overhead for each window. It is also helpful for communication between windows.
If we can go further and let multiple lightweight engines share a root isolate, then we can also completely solve the problem of data sharing. #94995
related issue:
#30701
/cc @stuartmorgan @gspencergoog @knopp
The text was updated successfully, but these errors were encountered: