Yes. The next step for package work is to add Qt/wayland. And with a demo written with Qt is better.
Thanks for the information, I will study how to build Qt-lighthouse first. I have no plan to build it for ARM platform. Maybe I will try to do it once I got an amlogic-8726 board. The repo devel:wayland is created. The packages will be put there soon. Regards, Xinyun -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kristian H?gsberg Sent: Monday, April 04, 2011 12:01 AM To: Liu, Xinyun Cc: [email protected] Subject: Re: [MeeGo-dev] Added wayland packages to MeeGo On Fri, Apr 1, 2011 at 3:38 AM, Liu, Xinyun <[email protected]> wrote: > Hello, April fools' day. You can try wayland with MeeGo in console mode now. > > After login in via console, just type "wayland-test", then you can try other > wayland apps from wayland-terminal. (/usr/bin/wayland-*) > > Q: Any preparation? > A: Yes. Change to console mode. > sed -i "s#id:5:initdefault#id:3:initdefault#" /etc/inittab > > Q: How to install/run it? > A: > a. Install MeeGo[1] with a Intel gfx card. (GenX) > b. Add the package repo[2] to /etc/zypp/repos.d/wayland.repo > c. Install related packages: > zypper in libxkbcommon mesa-libwayland-egl wayland wayland-demos cairo libdrm > libX11 mesa-dri-i915-driver mesa-libEGL mesa-libGLESv2 pixman > d. Run wayland-test > > Q: Can it use X as the backend? > A: No. It can do so but there is some bug in my rpm packages. > > Q: Any more reference? > A: http://wayland.freedesktop.org/ > > Q: Anything else? > A: Yes. More packages need to be added, bugs to be fixed, X related packages > to be cleaned up. The most important is to add devel packages to it. > But no plan. This is fantastic, thanks for setting it up. What I'm working on now is to try to move over the tablet UX, bit by bit. I've just started, but the plan is use Qt lighthouse and the QML scenegraph. I'm using the qtquick2-integration branch of the Qt lighthouse repo: git://gitorious.org/+qt-developers/qt/lighthouse.git and the plan is to make meego-ux-daemon the compositor and display server, so the idea is that we can drop X and mcompositor and just fold the compositing functionality into meego-ux-daemon. meego-ux-daemon will use something like the EGL fullscreen lighthouse plugin and evdev input to run directly on KMS. For the clients, we'll have to port meego-qml-launcher to Qt lighthouse and QML scenegraph as well, but the launcher will use the Wayland lighthouse plugin to run as a Wayland client. We'll have to define a MeeGo Tablet UX specific Wayland extension, to replace the ad-hoc use of EWMH in mcompositor and clients. Later on we can look into how to handle classic (non-QML) Qt applications and eventually legacy X clients. Anyway, that's the hand-wavey plan. I expect I'll fork the meego tablet ux repos in question on gitorious once I have something that kinda works. But from a packaging point of view the next step is to figure out how we can package the qtquick2-integration branch of Qt and add it to the Wayland repo. Kristian _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
