I suspect we'll want to remove CustomCursorSource altogether, and provide ActiveEventLoop::create_custom_cursor_from_rgba|animation|url instead.

No, it doesn't require anything running and should be loadable without event loop. The CustomCursor on the other side, is a handle to what you've loaded before, while source is a raw data.

I suspect we'll want to remove CustomCursorSource altogether, and provide ActiveEventLoop::create_custom_cursor_from_rgba|animation|url instead.

No, it doesn't require anything running and should be loadable without event loop. The CustomCursor on the other side, is a handle to what you've loaded before, while source is a raw data.

I meant for these proposed methods to directly return CustomCursor (which isn't loadable without the event loop (as that doesn't work on WASM)).

Our custom cursors work in a way that we create a source and then load into the event loop so cursor is not slow. The methods like from_rgba, etc, are needed to do initial data sanitation and prepare the assets ahead of time, like we do in the app example.

So I don't see how we'd move away from it or what for. We may eventually figure out how to merge source and cursor so the loading is transparent, but that's a different matter, if that's what you've asked about, indeed.

We may eventually figure out how to merge source and cursor so the loading is transparent, but that's a different matter, if that's what you've asked about, indeed.

Yeah, that's what I was discussing, and it's indeed a different matter.