Slashdot Mirror
LibreOffice Ported To Run On Wayland
An anonymous reader writes: LibreOffice has lost its X11 dependency on Linux and can now run smoothly under Wayland. LibreOffice has been ported to Wayland by adding GTK3 tool-kit support to the office suite over the past few months. LibreOffice on Wayland is now in good enough shape that the tracker bug has been closed and it should work as well as X11 except for a few remaining bugs. LibreOffice 5.0 will be released next month with this support and other changes outlined by the 5.0 release notes.
But something is better than nothing. Currently wayland is only offering the latter.
Your comment is two years out of date, Wayland has offered remote protocol since 2013 in the main branch, further its expected to be better supported than X11 (ie perfect alpha blending on shading at 60fps over a network link) all while using less resources than X11 and without degrading features.
https://www.youtube.com/watch?...
Most Wayland-compatible applications would likely not render things by directly communicating with the Wayland protocol. Instead, they will likely use a higher-level UI toolkit. Toolkits like GTK+ and Qt are able to switch between Wayland and X11 based on which server they detect to be available. If you need to run a Wayland-compatible application from a server to which you are logged in via ssh, you would likely be able to do so as long as X11 compatibility is retained. As long as there is no convenient way to use Wayland over network, it might well make sense to keep using X11 in that role even if otherwise the default in some distros ended up being Wayland.
On the downside, the user might encounter some uncommon bugs due to using a non-default backed. But in my experience, the situation already is that there are bugs that mostly exist in cases where X11 is used over network. Differences in performance and feature availability between X11 over network and local X11 server is quite large, so already continued availability of remotely usable GUI applications depends on people testing for and fixing issues that are specific to the over-network use case.
In fact, not wanting to give up on "proper hardware acceleration" is the number one reason I despise Wayland.
Lies, lies, lies, yeah:
https://www.phoronix.com/scan.php?page=news_item&px=mtgxmde
No, it is not dependent on systemd. You've posted this same comment before whenever Wayland comes up.
Grow the fuck up.
As an actual user, not just a developer talking about protocols try actually setting that up and using it. Supposedly that code is in the main branch but there is ZERO documentation about how to make it work. From what I have heard one of the developers wrote it in order to try to shut up all the people who were rightly complaining that a major feature from X was being taken away. Once he had a single demo it then went by the wayside. Does that code even work any more? Who knows, how would one even find out?
As far as I can tell remote Wayland was developed only far enough to be a publicity stunt and doesn't really exist in a usable state.