FYI I share the same opinion as you, Dominig.
Tiago
On 06/29/2014 07:41 PM, Dominig ar Foll (Intel OTC) wrote:
Hello,
the main driver to use Wayland is the optimisation of Graphic resource
versus X. Adding X emulation directly does against that objective.
We have spent a great man power to remove all X dependencies in Common,
I doubt that we want themback by the side door.
I would rather invest in the time to fix the issue properly under
Wayland than to add X Wayland.
Obviously platform developers still have the freedom to do what ever
they want.
Good news if for QT, X is not required, what you describe looks like an
input event bug.
Dominig ar Foll
Senior Architect
Intel Open Source Technology Centre
Le 27/06/2014 13:29, Roman Kubiak a écrit :
I was wondering is Xwayland going to be part of the Tizen:Common image.
I was able to build it myself and run some basic Xorg native apps
(xterm, blackbox) so it works. I built it on our M0 target
(ARM/Exynos4412) so i guess X86 should not be an issue. The only part
that did not work on ARM was GLX support, there seems to be no OpenGL
support on Exynos/MALI, open GLES and that's not the same thing. Did
anyone try this at all ?
Also i saw some QT5 apps on the current Common image, but did you
notice that QT does not react to touch events on either the M0 target
(other wayland apps react to touch events) or on the emulator, all
those apps are dead, only keyboard works on the emulator, but you
can't move the window or interact with it's content.
best regards
--
--------------
Roman Kubiak
--------------
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
