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. 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 Next the DFBWindow interface is created by the WM and attached to the right CoreDrawable regardless of its nesting level. 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. On 1/30/07, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > Denis Oliver Kropp schrieb: > > Denis Oliver Kropp schrieb: > >> Mike Emmel schrieb: > >>> I did not see this new window manager you mentioned. > >> Today he cometh. > > > > The SaWMan will get you, but this night he will spare you once more! > > Did you meet him on CVS? He's there :) > > -- > 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
