>True, but at the same time, Design isn't something divisible into >easy component parts. Design "should" or "shouldn't" isn't at all the >way one should think about Design. It is an integrated complete >process that isn't dissectable and cannot be accomplished >formulaically. A great designer once called it "taking something from >its existing state to its preferred state". Further, "graphic design" >has or rather, must play a part as large as it needs to play, and not >a tiny one. Then you fail to recognize the goals of this project. The OS is to be functional above all else, not just look "pretty". I never said graphical design is not a part of it, but it seems both you and Thomas seem to have an idea that graphical design has the highest priority in UI design. It doesn't. >"Practitioner's Handbook" kind of scares me as a title >for a book about design. Design isn't an art or a science, Design is >Design. You need to look up "Practitioner" in the dictionary. The title implies somebody who practices UI Design. Are you saying you don't want to be a practitioner? Then you shouldn't be volunteering for a UI Design team. For a project that is promoting the idea of a better UI Design interface, it needs people that truly understand what UI Design is about. That specifically is why Darkwyrm is currently in charge of this area. Curtis