I'm thinking that we could isolate all XCB-related functions into a small library, and then create an alternative library (implementing the same API as the XCB one) containing the equivalent wayland functions instead.
Of course, the API would have to be designed with both in mind, since both work in slightly different ways. On Tue, Dec 2, 2014 at 10:52 AM, Joel Leclerc <lkj...@ubuntu.com> wrote: > I have only done one small test in wayland ... I know the basics of how it > works, but I'm not very experienced. > > But I'll read through, try to get familiar with the codebase, and see what > I can do for now. > > On Tue, Dec 2, 2014 at 2:55 AM, Alexis Brenon <brenon.ale...@gmail.com> > wrote: > >> Hi blastmaster, >> >> I don't know Wayland at all (just by name). I'm more and more common with >> X11 since time I use it, and thanks to this very good website : Xplain - >> Explaining X11 for the rest of us >> <http://magcius.github.io/xplain/article/> >> Maybe you can start with this ! >> >> It's obvious that porting Awesome to wayland is not a so easy job !! But >> maybe it can be feasible, if a motivated team is build. >> >> Regards, >> Alexis >> >> >> Le Tue Dec 02 2014 at 10:38:37, Sebastian Oeste <blastmas...@tuxcode.org> >> a écrit : >> >> Alexis Brenon wrote: >>> > Maybe, feel free to contribute : https://github.com/awesomeWM/awesome >>> > >>> > Le Mon Dec 01 2014 at 23:30:20, MohsenPahlevanzadeh < >>> > moh...@pahlevanzadeh.org> a écrit : >>> > >>> > > Gnome 3.14 has been ported to wayland, but i don't know why awesome >>> still >>> > > X11 stay..... >>> >>> I'am neither a X11 nor a Wayland expert, but i would think to port >>> awesome to wayland it is necessary to port all the xcb stuff in awesome >>> to wayland. >>> >>> When grepping over the C source the following files seems to be affeced. >>> >>> $ ack --cc -lc 'xcb' >>> >>> event.h:4 >>> systray.c:44 >>> color.c:3 >>> property.c:65 >>> mousegrabber.h:2 >>> color.h:3 >>> common/xcursor.c:5 >>> common/atoms.h:3 >>> common/atoms.c:6 >>> common/xcursor.h:6 >>> common/xutil.h:11 >>> common/xembed.h:28 >>> common/xutil.c:20 >>> common/xembed.c:19 >>> keygrabber.h:3 >>> objects/client.c:74 >>> objects/drawin.c:13 >>> objects/drawin.h:1 >>> objects/button.h:3 >>> objects/client.h:12 >>> objects/window.h:4 >>> objects/window.c:12 >>> objects/screen.c:46 >>> objects/key.h:2 >>> objects/drawable.c:5 >>> objects/drawable.h:1 >>> systray.h:6 >>> root.c:50 >>> awesome.c:82 >>> luaa.c:9 >>> keyresolv.h:5 >>> selection.c:21 >>> spawn.c:1 >>> mouse.h:4 >>> keyresolv.c:13 >>> event.c:78 >>> mouse.c:11 >>> ewmh.c:68 >>> mousegrabber.c:8 >>> draw.h:11 >>> keygrabber.c:6 >>> xwindow.c:72 >>> ewmh.h:8 >>> xwindow.h:22 >>> globalconf.h:18 >>> draw.c:28 >>> property.h:4 >>> stack.c:6 >>> >>> So thats not a trivial change. I'am really interessted in the wayland - >>> x11 thing. But still have a lack of knowledge. >>> >>> If someone has more detailed ideas about the topic, or a good starting >>> point please let me know. >>> >>> best regards, >>> blastmaster >>> >> > > > -- > Joel Leclerc > -- Joel Leclerc
