Well, this is also a fallacy of yours (strawman?), I was countering the argument of:
> Also, to my understanding, Wayland is still not ready for such a use case.
With an example showing how to do it.
To answer your point, this wouldn't faze any sway user, and it is perfectly scriptable, you can add a button or script to perform the three server-side steps. Of course, gnome includes a button to cast to a nearby miracast-enabled screen.
I'm not answering to my mother, I'd set it up for her with a nice shortcut. And she probably wouldn't be using sway.
You also need a complex list of tasks for miracast.
* Turn on the TV (simple enough, but since we're counting steps...)
* Make sure the miracast option is enabled, and the TV is discoverable. That one is impossible to explain over the phone -- unlike a command line -- as every TV burries this under a different menu.
* Find the right button on the "client" PC (might require enabling an option before?) and click it.
> Also, to my understanding, Wayland is still not ready for such a use case.
With an example showing how to do it.
To answer your point, this wouldn't faze any sway user, and it is perfectly scriptable, you can add a button or script to perform the three server-side steps. Of course, gnome includes a button to cast to a nearby miracast-enabled screen.
I'm not answering to my mother, I'd set it up for her with a nice shortcut. And she probably wouldn't be using sway.
You also need a complex list of tasks for miracast.
* Turn on the TV (simple enough, but since we're counting steps...)
* Make sure the miracast option is enabled, and the TV is discoverable. That one is impossible to explain over the phone -- unlike a command line -- as every TV burries this under a different menu.
* Find the right button on the "client" PC (might require enabling an option before?) and click it.