KDE Plasma 5.26 Beta Week Saw More Fixes To The Plasma Wayland Session

[Vistaus]

Yes, that's right. But I'm used to then easily deleting when I don't need / don't like it. With GIT applications, it's a bit more complicated.

Not really. sudo make uninstall is your friend.

[guglovich]

You can compile it easily.

Yes, that's right. But I'm used to then easily deleting when I don't need / don't like it. With GIT applications, it's a bit more complicated.

[Vistaus]

Looks good, too bad nobody added it to the repository.

You can compile it easily.

[guglovich]

What about Packuru? https://gitlab.com/kyeastmood/packuru

Looks good, too bad nobody added it to the repository.

[Vistaus]

Setting the compression level, for example. Encrypted archives.

What about Packuru? https://gitlab.com/kyeastmood/packuru

[ⲣⲂaggins]

What do you think happens when X.org crashes? All your apps go with it.

Hardly ever happens because it doesn't run a compositor in the same process.

[Quackdoc]

... and you are on the wrong path ... this is not lack of 'freedom' ... you have all the freedom to implement a display manager (not a display server) that implements the standard ... your movie player app has nothing to do with it -- or you want 'the freedom to implement the kenel acpi interfaces in your app too?

Wayland prevents fragmentation because defines the standards for the various functionalities/components for the desktop stack.
Fragmentation is your app implementing the X11 -- desktop composition -- part of the whole desktop stack .....

is this a joke? I just gave multiple examples of fragmentation, or things that cannot implement features due to fragmentation... bruh, at least read what I comment before replying

[Grinness]

And that's the lack of freedom I'm talking about. it's none of the business My display server to determine what I can or cannot do. I don't care if kwin implements it. I care that my app cannot feasibly implement it.

you should not have to force a user to go out of their way for a future you used to implement. like I said MPV is just one specific thing, that is easily replicatble.

this is Wayland arbitrarily restricting app and user freedom. instead of implementing the feature in a way that could possibly be safe maybe a toggle inside of the compositor. they decide to outright say no to it.

also I'm not sure how on earth relying on a composite or specific feature prevents fragmentation. That's the definition of fragmentation. everyone implementing their own way of doing things.

... and you are on the wrong path ... this is not lack of 'freedom' ... you have all the freedom to implement a display manager (not a display server) that implements the standard ... your movie player app has nothing to do with it -- or you want 'the freedom to implement the kenel acpi interfaces in your app too?

Wayland prevents fragmentation because defines the standards for the various functionalities/components for the desktop stack.
Fragmentation is your app implementing the X11 -- desktop composition -- part of the whole desktop stack .....

[Quackdoc]

Then Kwin allows to do that even if MPV does not implement it ... I would say that this is actually directly countering your statement about segmentation.
The compositor is doing properly its job, taking it off the app (that is not supposed to handle compositing, but just playing the video)

And that's the lack of freedom I'm talking about. it's none of the business My display server to determine what I can or cannot do. I don't care if kwin implements it. I care that my app cannot feasibly implement it.

you should not have to force a user to go out of their way for a future you used to implement. like I said MPV is just one specific thing, that is easily replicatble.

this is Wayland arbitrarily restricting app and user freedom. instead of implementing the feature in a way that could possibly be safe maybe a toggle inside of the compositor. they decide to outright say no to it.

also I'm not sure how on earth relying on a composite or specific feature prevents fragmentation. That's the definition of fragmentation. everyone implementing their own way of doing things.

[Grinness]

I am talking about MPVs always ontop feature, not using the compositor specific features

Then Kwin allows to do that even if MPV does not implement it ... I would say that this is actually directly countering your statement about segmentation.
The compositor is doing properly its job, taking it off the app (that is not supposed to handle compositing, but just playing the video)