Mike Emmel schrieb: > Got It I was looking under wm not toplevel :) > > RIGHT ON ! > > This is basically the concept I'm talking about done by hand in your wm. > > Your drawing your border direct like I'm saying below each window.
Yes, it's part of the window drawing code at the moment. > So we want to make it generic so these "direct" drawing ops can be > done as a chain. > > Next I want to add real nesting/embedding of windows so we can > intermix draw/buffered windows as needed so its a tree instead of a > stack. > > Taking my approach both the border and the toplevel windows are > CoreDrawables with > DrawLists So CoreDrawable seems like a StReT region in UniQuE. > Next the DFBWindow interface is created by the WM and attached to the > right CoreDrawable > regardless of its nesting level. Seems like a good plan. If you want to merge techniques from Unique and SaWMan plus your own goods, based on SaWMan's "one process is a dedicated WM like in X11" model, that's fine :) > For the current api these must be double buffered later we can look at > how to change or add a api to removed this constraint but first lets > allow the WM to draw. > > Next this allows me to write a X11 wm thats "full screen" but > compatible with mixed dfb apps. Later I can reverse this and add a > adaptor api that allows a DFB wm to be a X11 WM. I guess I need more details to follow you on these two paragraphs ;) -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
