Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flutter runner multiple windows #357

Closed
kirill-21 opened this issue Feb 5, 2022 · 3 comments
Closed

Flutter runner multiple windows #357

kirill-21 opened this issue Feb 5, 2022 · 3 comments
Labels
question Further information is requested

Comments

@kirill-21
Copy link

kirill-21 commented Feb 5, 2022

Hi, i've found this pull request(#287) in this repository and want to ask why didn't you add this functionally and closed the request? It seems to be the only easy-to-use solution for multiple windows on Windows platform, there aren't any packages or official solutions for this task from flutter team (except of course creating a whole separate app and spawning it as a child window of the current process)

@timsneath
Copy link
Contributor

timsneath commented Feb 7, 2022

Hi there! It looks like it lives on here: https://github.com/ilopX/win

After chatting with @ilopX, we aligned on the general philosophy that it was better to keep the low-level win32 package separate from any potential higher-level idiomatic wrapper libraries. That lets those packages evolve at their own pace and experiment without worrying about API changes breaking semver, and also keeps win32 smaller and more focused than it would otherwise be.

I'm also taking a similar approach, for example: https://github.com/timsneath/win32_registry, which provides a high-level class wrapper over the underlying win32 registry APIs. I've also been experimenting a little with a Dart runner for Flutter apps, which is here: https://github.com/timsneath/win32_runner, although mine is designed more as a one-to-one replacement of the Flutter C++ runner, rather than adding new features like multiple windows.

Hopefully over time there will be a growing collection of win32_* libraries that wrap win32 with higher-level alternatives that are well-suited for Dart developers to use without requiring any knowledge of FFI or C.

@timsneath timsneath added the question Further information is requested label Feb 7, 2022
@kirill-21
Copy link
Author

kirill-21 commented Feb 7, 2022

Hi there! It looks like it lives on here: https://github.com/ilopX/win

After chatting with @ilopX, we aligned on the general philosophy that it was better to keep the low-level win32 package separate from any potential higher-level idiomatic wrapper libraries. That lets those packages evolve at their own pace and experiment without worrying about API changes breaking semver, and also keeps win32 smaller and more focused than it would otherwise be.

I'm also taking a similar approach, for example: https://github.com/timsneath/win32_registry, which provides a high-level class wrapper over the underlying win32 registry APIs. I've also been experimenting a little with a Dart runner for Flutter apps, which is here: https://github.com/timsneath/win32_runner, although mine is designed more as a one-to-one replacement of the Flutter C++ runner, rather than adding new features like multiple windows.

Hopefully over time there will be a growing collection of win32_* libraries that wrap win32 with higher-level alternatives that are well-suited for Dart developers to use without requiring any knowledge of FFI or C.

The problem is that his package supports only Flutter 2.2 and the current stable flutter version is already 2.10

@timsneath
Copy link
Contributor

Yup. Code maintenance isn't free, unfortunately.

All the more reason why it should be in a separate package, since it makes it easier for folk to update on their timescales. I don't have the capacity to own or update all the code that builds on top of win32, unfortunately, as excited as I am to see it come into existence. I'm focused on keeping the core of win32 to be a high-quality package, which is a significant evening / weekend time commitment in itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants