I just sent a email to Denis and he has not responed yet but I'll outline my proposal for the list.
1.) Refactor the code so all of the current wm is loaded as a shared library. Once this is done its up to the WM to provide the DFBWindow interface implementation. 2.) Consider expanding the concept of a window to be two parts first a region for events. This is not so important. Next consider the current back buffer flip only one operation that can be performed to show a window. I'd like to expand this to be a operator chain of primitives thats executed to show a window. The design would be similar to opengl. The default operator is to flip a back buffer but other operations are possbile. The only restriction is that any needed resources such as images would need to allocated in shared memory. The base set of operators would be all the core drawing ops of directfb. For "secure" apps one operator would be a custom callback that exists in a shared library loaded into the root process. Libraries like cairo could be used to generate advanced drawing/blitting chains. Comments . On 12/1/06, Sharma Nitin-A21652 <[EMAIL PROTECTED]> wrote: > Hi, > > I am in. > I have collected all the information that I could lay my hands on, in > this regard on DFB discussion groups. > Please find it attached. > > Regards, > Nitin Sharma > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Pedro Aguilar > Sent: Friday, December 01, 2006 2:29 PM > To: Arvind Ayyangar > Cc: [email protected] > Subject: Re: [directfb-dev] window mnager for directfb > > Hi, > > If you try to port any X based Window Manager you will find a lot of > problems because the way X works is completely different to DFB. They > were designed with different paradigms in mind. > > I had a look at different WM, the ones that I think were more suitable > for being ported: WindowMaker, Blackbox, Openbox and Matchbox. Since > Matchbox was designed for PDAs it seemed the better choice, but at the > end all of them have the problem of being designed for X. > > Mike Emmel had a similar problem with Metacity: > http://mail.directfb.org/pipermail/directfb-dev/2006-November/002455.htm > l > > DFB has a windowing system that could be a good starting point for a WM. > I'm interested in giving it a try. > > Regards, > > Pedro Aguilar > > > hi, > > i am trying to port the matchbox window manager which is designed > > specifically for the embedded environment and ran int a lot of > > conceptual issues. As I posted earlier, i tried to send these event > > through a socket and then tried to use the current dfb api's to manage > > > windows. But the problem is that both the default window manager and > > my WM are handling the events and after a period of time I find either > > > more than one window in focus or no window in focus at all. > > Can someone plz throw some light on this? > > > > also, si it possible to disable the default WM in DFB? > > any recommendation/tip? > > > > > > > > > > Regards > > ARviND AyyangaR > > _______________________________________________ > > directfb-dev mailing list > > [email protected] > > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > > > > > > _______________________________________________ > directfb-dev mailing list > [email protected] > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > > > _______________________________________________ > directfb-dev mailing list > [email protected] > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > > > > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
