Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re: LXDE Wayland support #14

Open
jleclanche opened this issue Apr 19, 2014 · 3 comments
Open

Re: LXDE Wayland support #14

jleclanche opened this issue Apr 19, 2014 · 3 comments

Comments

@jleclanche
Copy link

Hi! This is some fine work :-)

In your announcement post three days ago, you mention that LXDE does not support Wayland. I just wanted to bring up that we are in fact working on it (in our Qt branches) and contributions are more than welcome.
We also collaborate with the Maui project which you may have heard of... http://www.maui-project.org/ - They are a wayland-only lightweight and Qt-based desktop shell.
If you opt to look at Qt as a toolkit in the future, please drop by our mailing list or contact me directly. We're not just doing all this for us, we want our work to actually be useful for other potential desktops. :)

PS: I'm in Cambridge as well; if you want to meet up to discuss this, ping me.

@nocnokneo
Copy link

So is the only reason for the two separate projects that Maynard opted to build upon GTK while Maui/hawaii-shell opted to use Qt Quick? As far as I can tell the project goals and motivations are identical. Seems like a joint effort makes sense...

IMHO, Qt Quick seems like the superior solution, especially for creating smooth fluid interfaces with low CPU utilization that take advantage of the Raspberry Pi's GPU capabilities.

@fooishbar
Copy link
Contributor

@jleclanche Great, I'm really glad to hear it! As you've probably gathered, Maynard is fairly quiet since it fulfills our initial needs, and the entire Raspberry Pi graphics driver stack is being rewritten (GL shim -> full Mesa driver, DispManX -> full KMS driver for the HVS), so their attention is understandably focused on getting a solid underlying stack, rather than encouraging everyone to rely on the current setup.

I'm actually in London, but will let you know next time I head up.

@nocnokneo At the time we started this, QtWayland was in a much worse state than it is now.

@jleclanche
Copy link
Author

@fooishbar I met up with Eben Upton a while back about Maynard and we exchanged some ideas around this. I moved to Stockholm since I first wrote this though.

My understanding is that Maynard is actually on the shelves for now. When wayland needs resurface, you can contact us on the LXDE list or me directly (email on my profile) and we can figure something out. We're still looking at Wayland compatibility for 1.0 and we're much closer to it than we were when I filed this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants