2011/1/8 Dana Jansens <[email protected]>: > On Sat, Jan 8, 2011 at 9:22 AM, Simon Friis <[email protected]> wrote: >> 2011/1/8 Joakim Sindholt <[email protected]> >>> >>> On Sat, 2011-01-08 at 12:26 +0100, Simon Friis wrote: >>> > Thanks. I will check them out. >>> > >>> > >>> > I do know that a Wayland wm will have to be a compositor. But I don't >>> > really know how complicated making a compositor is. What will I have >>> > to know? >>> It's not really that complex. Wayland is pretty much just a buffer >>> management system, and your job in writing a compositor will be to take >>> the buffers given to you by applications and render them appropriately. >>> The protocol is intentionally vague in order to allow you to do pretty >>> much whatever you please with the buffers. That means you could write a >>> window manager that operates in 3D space, or allows rotation of windows. >>> As long as you can still redirect input to the correct surfaces >>> (windows) you're all set. >> I will give it a try then. We'll see if I can figure out how to render >> the buffers appropriately ;) . > > I think its important to point out that before a WM can fully be > implemented, protocols need to be defined for app<->compositor/wm > communication. There have been a thread or two about this on the list > you could look up. > > - Dana > Thanks for mentioning that too. As I understand it the protocol is partly defined right? And I suppose it will be finished before Natty Narwhal.
>>> PS. when replying to a mailing list, you should do a group reply. >> Ups! I'm sorry. I though GMail did that automatically. >> >>> > 2011/1/7 Joakim Sindholt <[email protected]> >>> > On Fri, 2011-01-07 at 17:22 +0100, Simon Friis wrote: >>> > > Hi! >>> > > >>> > > >>> > > >>> > > I'm interested in creating a window manager for Wayland. >>> > I've a basic >>> > > understanding of how it's done in X.org with Xlib. Does >>> > there exist >>> > > any documentation on how to create a window manager for >>> > Wayland? >>> > > >>> > > >>> > > Best >>> > > - paldepind >>> > >>> > >>> > Look in compositor/compositor-*.c to see how the current ones >>> > are >>> > implemented. Just in case you don't know: you're going to be >>> > implementing a compositor, not just a wm. >>> > >>> > >>> > >>> > >>> >>> >> _______________________________________________ >> wayland-devel mailing list >> [email protected] >> http://lists.freedesktop.org/mailman/listinfo/wayland-devel >> > _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
