On Oct 8, 2012, at 3:39 PM, Shane Dobbins <shanedobb...@gmail.com> wrote:
> Jeremy, > > My build output from running "make": Everything else comes out nice and > clean. > ####### START ################################ > <snip /> > ####### END ################################ > seems to operate just fine. Yeah, it looks right. > I want to just make sure I have my concept of how this all works together. > 1. The X-server handles the window events and internal workings of the window. > 2. Xquartz layer glues the Aqua to the Xserver XQuartz *is* the X11 server. It uses libXplugin to render the windows. > 3. from the exports in the Xplugin, we are able to create window frame > handlers in the AppleWM. AppleWM is an X11 protocol extension. Much of libXplugin is exposed to X11 clients (quartz-wm) via AppleWM. > 4. From what I can tell is the the AppleWM is what draws the frame around > the window. quartz-wm uses AppleWM to tell the server what to do. The server then calls into libXplugin to do it. > 5. The Quartz-WM then controls the behavior. _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
