Mike Emmel wrote: > This allows us to do tons of things. > It gives use the equivalent of XNest since you can run a wm in another > window. > It allows rootless mode with special root surfaces i.e now I can write > a x11 driver > where the main display is not accessible by default. MDI works. > Note that getting the directfb api to run on other OS and WM is > important for wide adoption. > > > If you don't want windows you don't carry the baggage the windowing > api can now evolve at its own pace. And most important Core Directfb > is defined it provides surfaces input and multiapplication support for > surfaces period.
I like the ideas in general, had something similar a while back when doing StReT, but I think we should leave DirectFB as it is before 1.0 and start flipping top and bottom in 1.1 :) > Short term we can just push the software cursor which is a window now > up into the wm. > Later it should work without one but its tied now anyway. I'm working on a software cursor implementation which uses a surface instead of a window. A big advantage will be that you can't reveal changes within windows that are not yet commited, i.e. Flip()ed. That's because I'm going to implement a backing store for the region under the cursor. The cursor can be handled in the core completely, but I'm not sure yet if that's the best option. -- 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
