You are talking like if Wayland is supposed to implement some general guidelines to the rest of the applications , but in reality , most applications should not care if wayland exist at all .
Applications should care about what they are running on. You can abstract it, but eventually, some layer will deal with it. And yes, Wayland is supposed to implement some general guidelines: how you communicate with the compositor or display server.You are talking like if Wayland is supposed to implement some general guidelines to the rest of the applications , but in reality , most applications should not care if wayland exist at all .
The app only needs to know whether it needs to render or not. Everything else is up to the compositor.
An IM client might show you as "away" when minimized, a RSS reader might optimize by not checking as often when minimized, and so on. It doesn't have to be rendering-related.
That is none of your business nor Wayland's business nor the compositor's business . "Separation of concerns " See?. That's a choice made by the developer, it does not matters if you like to or not. And what do you meant by "standard API"?Things like that are exactly why people get so pissed off with skype. It is not up to the app to decide those sorts of things. If the compositor wants to provide that sort of thing, then it can provide it. But apps should not be fighting the user to prevent them from minimizing or closing their apps. That sort of thing can be provided by a standard API and leave it up to the compositor to decide exactly how it should be represented, if at all.Quote Originally Posted by uid313 View Post
When Skype is minimized it displays the camera in a little widget on the corner of the screen.