Open matthew-carroll opened 1 year ago
I am currently waiting for Flutter’s multi-window support to drop before implementing this. This way I will know what the Swift side is going to look like while designing the API. Plus, I would like to avoid breaking changes until then.
WindowManipulator
is completely based on static methods. This seems to create at least three limitations:Developers can't use Dart's built-in builder syntax:
It seems unlikely that this API will work in a world with multiple windows.
The implementation can't be replaced with a fake version for tests.
All of these issues could be alleviated by using a typical singleton implementation:
WindowManipulator.instance
orWindowManipulator.primary
, etc.