Change the way you get a window

[tomaka]

On some platforms like Android, iOS, emscripten, etc. you only ever get one "window", and it is already created when you start.

Therefore the API should be more like glutin::get_window() instead of glutin::Window::new.

[milibopp]

Is this API still compatible with multi-window applications on desktop platforms?

[tomaka]

I don't really know how the API would look like yet.
I opened this issue because it's not correct to "create" a window on android, since you already have one when the program starts. The consequence is that the windows settings that you specify in the builder are ignored.

If you or someone happens to have a suggestion, that would be welcome.

[milibopp]

Well, I would say that such a fundamental difference in platform behaviour should be reflected in the API. So getting the single Android window should be something different than creating a window on a regular desktop. In my opinion either should fail on the wrong platform. On top of that we could provide a platform-agnostic wrapper function that gets the single window on Android, while it creates some default window on another platform. Let's just make sure that we do not impose any limitations of mobile apps on desktop apps.

[tomaka]

Closing for rust-windowing/winit#33

[seivan]

@tomaka You can have multiple windows (if you're referring to UIWindow) and it's not a bad idea to be able to create one if you want to switch between multiple Windows. One scenario could be toggling between Game and Menu states where Menu is using native UIKit/Swift and Game is written in Rust.

[francesca64]

@seivan your comment would have better visibility on the relevant winit issue (rust-windowing/winit#33).

[seivan]

@francesca64 Thanks! Wrote a bit more there.