Hi, I'm having a look at SaWMan and its samples and at the same time trying to understand what Denis and Mike were saying: http://mail.directfb.org/pipermail/directfb-dev/2007-February/002727.html
I think I got an idea, but I still have a lot of questions... Denis, Mike, thanks for being patience with newbies! Since I was not familiarized with DirectFB internals, I started with fusion as Mike recommended (I updated the old fusion examples in the wiki: http://directfb.org/wiki/index.php/Fusion:Example ). AFAIK, the current stack of apps is the following: testrun | v testman | v SaWMan | v DirectFB The CoreDrawable that contains each drawable element such as borders and windows would become part of SaWMan. I can see the CoreDrawable as a list of all the elements that must be drawn by a given chain of drawing ops. Is this correct? Why should it be a tree? How would this tree be organized? Is an element of a CoreDrawable a DFB region? For example, if I have a given app in GTK+ over DFB, currently GDK calls directly DFB funcs. If we want that this app and others be managed by SaWMan, GDK should talk directly to the SaWMan that in turn pass the info to DFB, right? If I got it, the whole WM functionality is split in two: a low-level module SaWMan that is the responsible for drawing regions (the CoreDrawable) and a high-level module "testman" that talks directly to the apps . Eventually, could testman implement a layer to which all apps talks, no matter if it's a DFB app or an X11 app? In other words, could this module implement the layer that would allow an X11 app talk to DFB an the other way around? Is there an IRC? Could help for avoiding sending these long emails? Thanks! Regards, Pedro Aguilar _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
