Jeremy, My build output from running "make": Everything else comes out nice and clean. ####### START ################################ shanes-MacBook-Pro:quartz-wm shane$ make make all-recursive Making all in lib cp libquartz-wm-ds.apsl.dylib libquartz-wm-ds.1.dylib install_name_tool -id /opt/X11/lib/libquartz-wm-ds.1.dylib libquartz-wm-ds.1.dylib rm -f libquartz-wm-ds.dylib ln -s libquartz-wm-ds.1.dylib libquartz-wm-ds.dylib Making all in src OBJC dock-support-handler.o OBJC frame.o OBJC main.o main.m: In function ‘x_error_handler’: main.m:135: warning: format not a string literal, argument types not checked main.m:146: warning: format not a string literal, argument types not checked OBJC utils.o utils.m: In function ‘x_get_string_property’: utils.m:110: warning: ‘stringWithCString:’ is deprecated (declared at /System/Library/Frameworks/Foundation.framework/Headers/NSString.h:363) OBJC x-input.o CC x-list.o OBJC x-screen.o x-screen.m: In function ‘window_level_less’: x-screen.m:307: warning: cast discards qualifiers from pointer target type x-screen.m:307: warning: cast discards qualifiers from pointer target type OBJC x-window.o CC x11-geometry.o OBJCLD quartz-wm Making all in man GEN quartz-wm.1 make[2]: Nothing to be done for `all-am'. shanes-MacBook-Pro:quartz-wm shane$ ####### END ################################ seems to operate just fine.
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 3. from the exports in the Xplugin, we are able to create window frame handlers in the AppleWM. 4. From what I can tell is the the AppleWM is what draws the frame around the window. 5. The Quartz-WM then controls the behavior. how close am I to all of this?
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
