3fb93b4f83
Creating window when event loop is not running generally doesn't work, since a bunch of events and sync OS requests can't be processed. This is also an issue on e.g. Android, since window can't be created outside event loop easily. Thus deprecate the window creation when event loop is not running, as well as other resource creation to running event loop. Given that all the examples use the bad pattern of creating the window when event loop is not running and also most example existence is questionable, since they show single thing and the majority of their code is window/event loop initialization, they wore merged into a single example 'window.rs' example that showcases very simple application using winit. Fixes #3399.
47 lines
2.1 KiB
Rust
47 lines
2.1 KiB
Rust
// Brief introduction to the internals of the web backend:
|
|
// The web backend used to support both wasm-bindgen and stdweb as methods of binding to the
|
|
// environment. Because they are both supporting the same underlying APIs, the actual web bindings
|
|
// are cordoned off into backend abstractions, which present the thinnest unifying layer possible.
|
|
//
|
|
// When adding support for new events or interactions with the browser, first consult trusted
|
|
// documentation (such as MDN) to ensure it is well-standardised and supported across many browsers.
|
|
// Once you have decided on the relevant web APIs, add support to both backends.
|
|
//
|
|
// The backend is used by the rest of the module to implement Winit's business logic, which forms
|
|
// the rest of the code. 'device', 'error', 'monitor', and 'window' define web-specific structures
|
|
// for winit's cross-platform structures. They are all relatively simple translations.
|
|
//
|
|
// The event_loop module handles listening for and processing events. 'Proxy' implements
|
|
// EventLoopProxy and 'WindowTarget' implements ActiveEventLoop. WindowTarget also handles
|
|
// registering the event handlers. The 'Execution' struct in the 'runner' module handles taking
|
|
// incoming events (from the registered handlers) and ensuring they are passed to the user in a
|
|
// compliant way.
|
|
|
|
mod r#async;
|
|
mod cursor;
|
|
mod device;
|
|
mod error;
|
|
mod event_loop;
|
|
mod keyboard;
|
|
mod main_thread;
|
|
mod monitor;
|
|
mod window;
|
|
|
|
#[path = "web_sys/mod.rs"]
|
|
mod backend;
|
|
|
|
pub use self::device::DeviceId;
|
|
pub use self::error::OsError;
|
|
pub(crate) use self::event_loop::{
|
|
ActiveEventLoop, EventLoop, EventLoopProxy, OwnedDisplayHandle,
|
|
PlatformSpecificEventLoopAttributes,
|
|
};
|
|
pub use self::monitor::{MonitorHandle, VideoModeHandle};
|
|
pub use self::window::{PlatformSpecificWindowAttributes, Window, WindowId};
|
|
|
|
pub(crate) use self::keyboard::KeyEventExtra;
|
|
pub(crate) use crate::icon::NoIcon as PlatformIcon;
|
|
pub(crate) use crate::platform_impl::Fullscreen;
|
|
pub(crate) use cursor::CustomCursor as PlatformCustomCursor;
|
|
pub(crate) use cursor::CustomCursorBuilder as PlatformCustomCursorBuilder;
|
|
pub(crate) use cursor::CustomCursorFuture;
|