You are not logged in.
Hi to everyone. I have a question. Now that the next version of XFCE has been confirmed for release with Wayland soon, do we know anything about if the inclusion of Wayland will mean actual window animations? Fade in, fade out; that kind of thing? I understand about XFCE being a "lightweight" and "classic" desktop environment, but honestly, with much of the hardware out there (including the older kind, even), I would imagine that it's mostly able enough to handle window animations, especially in a desktop environment that's already considered "lightweight" by itself. And Wayland is a whole different game, too. It's supposed to modernize desktop environments. So will that modernization be extended to window (and menu?) animations for when users close them, open them, and so on? Thanks.
Offline
All this is managed by the compositor, and Xfce doesn't yet have a compositor (a port of xfwm4 is planned, but has barely begun). So it depends on the compositor you use. With wayfire, for example, everything you're talking about is supported, I think.
Offline
In my simple opinion, it's all up to the devs if they want to implement optional effects (but simple fading, just like Budgie, not too fancy and heavy stuff) inside the actual compositor (xfwm4). I've always disliked things like Compton, Compiz and so on that requires a waste of openGL resources and you may have micro stutters on 3D full screen, or even worst, screen tearing issues.
The actual compositor is great and if you only just add a decent window tiling manager like Cortile, it's even greater. Generally, Xfce does require little or nothing more that it is. Don't forget that independently from hardware that relatively improve nowadays, Xfce respect the minimum things that server requires when, eventually, an operator need a more comfortable GUI. I think these developers want to simply keep the balance of a GUI with the lightweight efficiency of a command line
If is working, don't touch it!! :-)
Offline
[ Generated in 0.008 seconds, 7 queries executed - Memory usage: 526.02 KiB (Peak: 531.6 KiB) ]