Re: [MeeGo-dev] Added wayland packages to MeeGo

2011-04-06 Thread Liu, Xinyun
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: hoegsb...@gmail.com [mailto:hoegsb...@gmail.com] On Behalf Of Kristian 
H?gsberg
Sent: Monday, April 04, 2011 12:01 AM
To: Liu, Xinyun
Cc: meego-dev@meego.com
Subject: Re: [MeeGo-dev] Added wayland packages to MeeGo

On Fri, Apr 1, 2011 at 3:38 AM, Liu, Xinyun  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
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Re: [MeeGo-dev] Added wayland packages to MeeGo

2011-04-03 Thread Kristian Høgsberg
On Sat, Apr 2, 2011 at 1:39 AM, Carsten Munk  wrote:
> 2011/4/1 Liu, Xinyun :
>> 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.
>>
>> [1] MeeGo Image
>>  http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-netbook-ia32/meego-netbook-ia32-1.1.99.0.20110330.3.img
>>
>>  In fact, I used a smaller image to test wayland, I added zypper, vim and 
>> created the image with this .ks file
>>        
>> http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-core-ia32-base-nodoc/meego-core-ia32-base-nodoc-1.1.99.0.20110330.3.ks
>>
>> [2] wayland rpm repo for MeeGo
>>  http://download.meego.com/live/home:/xyl:/wayland/Trunk/home:xyl:wayland.repo
> Hi,
>
> Thank you for kicking off a good initiative. I think there's many
> people and companies interested in this area - maybe we should propose
> a devel:wayland project in the MeeGo OBS? It is after all one of the
> important directions for MeeGo.
>
> I guess one of the steps would also be to have Qt Lighthouse packages
> there, enabled for Wayland?
>
> I'd be interested in ARM builds of the packages as well, to experiment
> early on on those platforms (probably similar challenges as with PVR
> in Intel devices).

Hardware enabling is something that has recently come together pretty
well.  I just post a bit of documentation about the couple of things
that Wayland needs here (scroll to the end):

  http://wayland.freedesktop.org/architecture.html

It's still a bit open-ended with respect to how to bring up the
compositor on the hardware, but that's technically not Wayland
specific, it's something that each EGL stack solves in different,
vendor specific ways.

Kristian
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Re: [MeeGo-dev] Added wayland packages to MeeGo

2011-04-03 Thread Kristian Høgsberg
On Fri, Apr 1, 2011 at 3:38 AM, Liu, Xinyun  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
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Re: [MeeGo-dev] Added wayland packages to MeeGo

2011-04-01 Thread Carsten Munk
2011/4/1 Liu, Xinyun :
> 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.
>
> [1] MeeGo Image
>  http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-netbook-ia32/meego-netbook-ia32-1.1.99.0.20110330.3.img
>
>  In fact, I used a smaller image to test wayland, I added zypper, vim and 
> created the image with this .ks file
>        
> http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-core-ia32-base-nodoc/meego-core-ia32-base-nodoc-1.1.99.0.20110330.3.ks
>
> [2] wayland rpm repo for MeeGo
>  http://download.meego.com/live/home:/xyl:/wayland/Trunk/home:xyl:wayland.repo
Hi,

Thank you for kicking off a good initiative. I think there's many
people and companies interested in this area - maybe we should propose
a devel:wayland project in the MeeGo OBS? It is after all one of the
important directions for MeeGo.

I guess one of the steps would also be to have Qt Lighthouse packages
there, enabled for Wayland?

I'd be interested in ARM builds of the packages as well, to experiment
early on on those platforms (probably similar challenges as with PVR
in Intel devices).

BR
Carsten Munk


>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines


[MeeGo-dev] Added wayland packages to MeeGo

2011-04-01 Thread Liu, Xinyun
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.

[1] MeeGo Image
  
http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-netbook-ia32/meego-netbook-ia32-1.1.99.0.20110330.3.img

  In fact, I used a smaller image to test wayland, I added zypper, vim and 
created the image with this .ks file

http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-core-ia32-base-nodoc/meego-core-ia32-base-nodoc-1.1.99.0.20110330.3.ks

[2] wayland rpm repo for MeeGo
  http://download.meego.com/live/home:/xyl:/wayland/Trunk/home:xyl:wayland.repo

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines