DOCSLIB.ORG

The X Window System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The X Window System The X Window System Version y z x James Gettys Philip L Karlton and Scott McGregor Digital Equipment Corp oration Silicon Graphics Computer Systems CRL Decemb er Abstract The X Window System has b ecome widely accepted by manymanufac turers X provides network transparent access to displayservers allowing lo cal and remote client programs to access a users display X is used on high p erformance workstation displays as well as terminals and client programs run on everything from micro to sup er computers This pap er describ es the tradeos and basic design decisions made during the design of X Version We presume familiarity with the pap er describing XVersion Keywords X Window System interactivehumancomputer interface sys tem distributed systems c Digital Equipment Corp oration and Silicon Graphics Computer Systems All rights reserved The X Window System is a Massachusetts Institute of Technology trademark This pap er will app ear in a sp ecial issue of SoftwarePractice and Experience y Digital Equipment Corp oration Cambridge ResearchLab One Kendall Square Bldg Cambridge MA USA jgcrldeccom z Silicon Graphics Computer Systems Systems Software Division N Shore line Boulevard Mountain View CA USA karltonsgicom x Formerly at Digital Equipment Corp oration now at The Santa Cruz Op eration Encinal Street PO Box Santa Cruz CA USA mcgregorscocom The X Window System Version 11 JAMES GETTYS Digital Equipment Corporation, Cambridge Research Laboratory One Kendall Square, Bld 700 Cambridge, MA 02139, U.S.A. [email protected] PHILIP L. KARLTON Silicon Graphics Computer Systems, Systems Software Division, 2011 N. Shoreline Boulevard Mountain View, CA 94039-7311, U.S.A. [email protected] SCOTT MCGREGOR1 Digital Equipment Corporation [email protected] SUMMARY The X Window System2 has become widely accepted by many manufacturers. X pro- vides network transparent access to display servers, allowing local and remote client pro- grams to access a user’s display. X is used on high performance workstation displays as well as terminals, and client programs run on everything from micro to super computers. This paper describes the tradeoffs and basic design decisions made during the design of X Version 11. We presume familiarity with the paper describing X Version 101. KEY WORDS X Window System Interactive Human-computer interface system Distributed Systems 1Now at The Santa Cruz Operation, 400 Encinal Street, P.O. Box 1900, Santa Cruz, California 95061 2The X Window System is a trademark of the Massachusetts Institute of Technology. © by Digital Equipment Corporation and Silicon Graphics Computer Systems, all rights reserved. This paper will appear in a special issue of Software Practice and Experience. 2 J. GETTYS, P. L. KARLTON, S. MCGREGOR Contents Introduction ............................................................................................................ 3 Goals of Version 11 Design .................................................................................... 4 Lessons Learned from Previous X Versions.......................................................... 5 Display Support ...................................................................................................... 7 Windows .................................................................................................................. 9 Atoms, Property Lists and Selections ................................................................. 12 Atoms ........................................................................................................... 13 Properties..................................................................................................... 13 Selections ..................................................................................................... 14 Primary ........................................................................................................ 15 Secondary..................................................................................................... 16 Events ................................................................................................................... 17 Window Management Functions ......................................................................... 19 Graphics ................................................................................................................ 23 Graphics Operations ................................................................................... 25 Graphics Contexts ....................................................................................... 26 Text Painting and Font Support.......................................................................... 29 Extensions............................................................................................................. 31 Keyboards ............................................................................................................. 31 Distributed Systems Architecture ....................................................................... 33 Lessons Learned and Results ............................................................................. 33 Future Topics ........................................................................................................ 37 Acknowledgments................................................................................................. 38 References ............................................................................................................. 39 November 21, 1990 THE X WINDOW SYSTEM - VERSION 11 3 Introduction The X Window System has become widely used over the last several years. After the release of Version 10 of X (hereafter called X10) from MIT in the fall of 1985, and its release as a product under Ultrix1 the following January, many people at several corporations and universities requested extensions to X to support their favorite application or hardware. X10 had been limited to what several people could implement, and these limitations were typi- cally well known (and even documented). For example, X10 could only support displays with no more than 16 bits/pixel, and this limitation was inherent in many areas of the wire protocol. Design of Version 11 started late in the spring of 1986. A larger set of contributors added expertise and experience in areas where it had been lacking in X10. The design was circulated for public comment and review that summer. A sample implementation of the protocol design started that fall, and became available in the fall of 1987. Feedback from reviewers and alpha and beta testers resulted in significant design changes to the core protocol, and deletions of some functions which were found to be poorly designed. (These functions were left to future extensions to X11). A brief history of events is available in The X Window System2. The X11 protocol was designed with little idea of how it would be implemented and was fully specified before the implementation began. It is of course true, however, that if we did not un- derstand how to implement something in a reasonable amount of time and effort (since timeli- ness was critical) we did not add it to the design; for example, non-rectangular windows have been added as an extension since the original release. We did not understand at the time how easy they would be to implement, and therefore explicitly rejected them during the design meet- ing. The specification was changed during alpha and beta test as we learned from the imple- mentation; often errors in the specification or design flaws were uncovered as the implementa- tion proceeded. We are very skeptical of systems that have never been implemented before widespread adoption; similarly, systems that have not been carefully specified before imple- mentation begins are also suspect. Somewhat after the base window system work, other groups began design of a number of toolkits and window managers for X.4,30 Feedback from these groups was particularly impor- tant to the base window system design. In this paper, X10 and X11 are used to refer to specific X versions, when we must distinguish between them. 1 Ultrix is a trademark of Digital Equipment Corporation. November 21, 1990 4 J. GETTYS, P. L. KARLTON, S. MCGREGOR Goals of Version 11 Design “The only thing worse than generalizing from a single example is generalizing from no exam- ples at all.” - Phil Karlton We realized at the first design meeting that it was impossible to design a protocol that was both upward compatible with X10 and able to support the different kinds of display hardware we could foresee. Additionally, we wished to support many window management policies that X10 could not support, such as window “decoration” and tiling. This fact and the long “wish list” required a complete redesign of X. The major goals for X11 included: • Redesign of the basic protocol encoding to increase efficiency and reduce server round trips • Support for deep frame buffers (more than 16 bits per pixel) • Support for a wider variety of color maps • Clean basic pixel-oriented graphics • Text capabilities for WYSIWYG editors • Clean up and generalization of facilities (a laundry list from X10) • Extensible protocol • Facilities for clients to exchange information (cut and paste of arbitrary information) At the first design meeting, we decided that at initial release the X11 core protocol would NOT support: • Three dimensional graphics • Sub-pixel graphics and anti-aliasing • World coordinate systems • Video, speech, high-fidelity
Load more

Recommended publications
  • R&S®BBA100 Broadband Amplifier Open
    R&S®BBA100 Broadband Amplifier Open Source Acknowledgment 5353.8300.00 – 01 /RL/1/EN 01.00 / Broadcasting 3575.4620.02 M: - T - PAD Open Source Acknowledgment R&S BBA100 Introduction Contents 1 Introduction ......................................................................................... 3 1.1 Disclaimer ..................................................................................................................... 3 1.2 How to obtain the source code .................................................................................. 3 2 Software packages ............................................................................. 4 3 Verbatim license texts ........................................................................ 7 3.1 Apache License 2.0 ..................................................................................................... 7 3.2 GNU Library General Public License, Version 2.0 (LGPL 2.0) ..............................10 3.3 Boost Software License ............................................................................................18 3.4 GNU General Public License, Version 2.0 (GPL 2.0) ..............................................18 3.5 GNU Lesser General Public License, Version 2.1 (LGPL 2.1) ...............................24 3.6 Mozilla Public License, Version 1.1 (MPL 1.1) ........................................................32 3.7 MIT ...............................................................................................................................40 3.8 JDOM License
    [Show full text]
  • Release Notes for X11R6.8.2 the X.Orgfoundation the Xfree86 Project, Inc
    Release Notes for X11R6.8.2 The X.OrgFoundation The XFree86 Project, Inc. 9February 2005 Abstract These release notes contains information about features and their status in the X.Org Foundation X11R6.8.2 release. It is based on the XFree86 4.4RC2 RELNOTES docu- ment published by The XFree86™ Project, Inc. Thereare significant updates and dif- ferences in the X.Orgrelease as noted below. 1. Introduction to the X11R6.8.2 Release The release numbering is based on the original MIT X numbering system. X11refers to the ver- sion of the network protocol that the X Window system is based on: Version 11was first released in 1988 and has been stable for 15 years, with only upwardcompatible additions to the coreX protocol, a recordofstability envied in computing. Formal releases of X started with X version 9 from MIT;the first commercial X products werebased on X version 10. The MIT X Consortium and its successors, the X Consortium, the Open Group X Project Team, and the X.OrgGroup released versions X11R3 through X11R6.6, beforethe founding of the X.OrgFoundation. Therewill be futuremaintenance releases in the X11R6.8.x series. However,efforts arewell underway to split the X distribution into its modular components to allow for easier maintenance and independent updates. We expect a transitional period while both X11R6.8 releases arebeing fielded and the modular release completed and deployed while both will be available as different consumers of X technology have different constraints on deployment. Wehave not yet decided how the modular X releases will be numbered. We encourage you to submit bug fixes and enhancements to bugzilla.freedesktop.orgusing the xorgproduct, and discussions on this server take place on <[email protected]>.
    [Show full text]
  • Desktop Migration and Administration Guide
    Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Last Updated: 2021-05-05 Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Marie Doleželová Red Hat Customer Content Services [email protected] Petr Kovář Red Hat Customer Content Services [email protected] Jana Heves Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • THINC: a Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices
    THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Graduate School of Arts and Sciences COLUMBIA UNIVERSITY 2011 c 2011 Ricardo A. Baratto This work may be used in accordance with Creative Commons, Attribution-NonCommercial-NoDerivs License. For more information about that license, see http://creativecommons.org/licenses/by-nc-nd/3.0/. For other uses, please contact the author. ABSTRACT THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto THINC is a new virtual and remote display architecture for desktop computing. It has been designed to address the limitations and performance shortcomings of existing remote display technology, and to provide a building block around which novel desktop architectures can be built. THINC is architected around the notion of a virtual display device driver, a software-only component that behaves like a traditional device driver, but instead of managing specific hardware, enables desktop input and output to be intercepted, manipulated, and redirected at will. On top of this architecture, THINC introduces a simple, low-level, device-independent representation of display changes, and a number of novel optimizations and techniques to perform efficient interception and redirection of display output. This dissertation presents the design and implementation of THINC. It also intro- duces a number of novel systems which build upon THINC's architecture to provide new and improved desktop computing services. The contributions of this dissertation are as follows: • A high performance remote display system for LAN and WAN environments.
    [Show full text]
  • Using a Next Workstation As a Development Platform for Version 5 Sas Applications
    USING A NEXT WORKSTATION AS A DEVELOPMENT PLATFORM FOR VERSION 5 SAS APPLICATIONS Joseph E St Sauver, Office of University Computing, University of Oregon ABSTRACT Similarly. there is liUle sense in tieing up a PC for hours (or days) running a large statistical analysis when a sha.red SAS Institute has yet to announce any firm plans to port the mainframe will often have abundant horsepower to handle just SAS System* to NeXT* workstations. Nonetheless, a NeXT those sorts of CPU-intensive jobs. workstation can serve as an excellent platform for developing VAXNMS· (or other mainframe) SAS System code for remote The PC version of SAS atte~s to explott this philosophy by execution. giving the user the option of either processing SAS code locally using the SUBMIT command, or processing SAS code on a The combination of a strong windowing environment, display remote mainframe SAS host using the RSUBMIT command. In a PostScript support. a built-in athemet interlace and copious perfect world. this approach would allow the user to elect the slorage eapacny bundled on lOP of more-or-Iess BSD 4.3 UNIX" best mix of local and remote resources to achieve his or her make development of SAS System code on the NeXT for objectives in a timely and cost effective manner. remote execution on another mainframe quite easy. Unfortunately, in my experience, the happy symbiosis The author's experience with use of a NeXT as a remote code envisioned between the PC version of the SAS System and the development plaHorm for SAS and SAS/Graph" on a VAXNMS mainframe version of the SAS system often breaks down.
    [Show full text]
  • Sun Ultratm 5 Workstation Just the Facts
    Sun UltraTM 5 Workstation Just the Facts Copyrights 1999 Sun Microsystems, Inc. All Rights Reserved. Sun, Sun Microsystems, the Sun logo, Ultra, PGX, PGX24, Solaris, Sun Enterprise, SunClient, UltraComputing, Catalyst, SunPCi, OpenWindows, PGX32, VIS, Java, JDK, XGL, XIL, Java 3D, SunVTS, ShowMe, ShowMe TV, SunForum, Java WorkShop, Java Studio, AnswerBook, AnswerBook2, Sun Enterprise SyMON, Solstice, Solstice AutoClient, ShowMe How, SunCD, SunCD 2Plus, Sun StorEdge, SunButtons, SunDials, SunMicrophone, SunFDDI, SunLink, SunHSI, SunATM, SLC, ELC, IPC, IPX, SunSpectrum, JavaStation, SunSpectrum Platinum, SunSpectrum Gold, SunSpectrum Silver, SunSpectrum Bronze, SunVIP, SunSolve, and SunSolve EarlyNotifier are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. OpenGL is a registered trademark of Silicon Graphics, Inc. Display PostScript and PostScript are trademarks of Adobe Systems, Incorporated, which may be registered in certain jurisdictions. Netscape is a trademark of Netscape Communications Corporation. DLT is claimed as a trademark of Quantum Corporation in the United States and other countries. Just the Facts May 1999 Positioning The Sun UltraTM 5 Workstation Figure 1. The Ultra 5 workstation The Sun UltraTM 5 workstation is an entry-level workstation based upon the 333- and 360-MHz UltraSPARCTM-IIi processors. The Ultra 5 is Sun’s lowest-priced workstation, designed to meet the needs of price-sensitive and volume-purchase customers in the personal workstation market without sacrificing performance.
    [Show full text]
  • A Font Family Sampler
    A Font Family Sampler Nelson H. F. Beebe Department of Mathematics University of Utah Salt Lake City, UT 84112-0090, USA 11 February 2021 Version 1.6 To assist in producing greater font face variation in university disser- tations and theses, this document illustrates font family selection with a LATEX document preamble command \usepackage{FAMILY} where FAMILY is given in the subsection titles below. The body font in this document is from the TEX Gyre Bonum family, selected by a \usepackage{tgbonum} command in the document preamble, but the samples illustrate scores other font families. Like Computer Modern, Latin Modern, and the commercial Lucida and MathTime families, the TEX Gyre families oer extensive collections of mathematical characters that are designed to resemble their companion text characters, making them good choices for scientic and mathemati- cal typesetting. The TEX Gyre families also contain many additional spe- cially designed single glyphs for accented letters needed by several Euro- pean languages, such as Ð, ð, Ą, ą, Ę, ę, Ł, ł, Ö, ö, Ő, ő, Ü, ü, Ű, ű, Ş, ş, T,˚ t,˚ Ţ, ţ, U,˚ and u.˚ Comparison of text fonts Some of the families illustrated in this section include distinct mathemat- ics faces, but for brevity, we show only prose. When a font family is not chosen, the LATEX and Plain TEX default is the traditional Computer Mod- ern family used to typeset the Art of Computer Programming books, and shown in the rst subsection. 1 A Font Family Sampler 2 NB: The LuxiMono font has rather large characters: it is used here in 15% reduced size via these preamble commands: \usepackage[T1]{fontenc} % only encoding available for LuxiMono \usepackage[scaled=0.85]{luximono} \usepackage{} % cmr Lorem ipsum dolor sit amet, aenean nulla tellus metus odio non maecenas, pariatur vitae congue laoreet semper, nulla adipiscing cursus neque dolor dui, faucibus aliquam quis.
    [Show full text]
  • An Introduction to the X Window System Introduction to X's Anatomy
    An Introduction to the X Window System Robert Lupton This is a limited and partisan introduction to ‘The X Window System’, which is widely but improperly known as X-windows, specifically to version 11 (‘X11’). The intention of the X-project has been to provide ‘tools not rules’, which allows their basic system to appear in a very large number of confusing guises. This document assumes that you are using the configuration that I set up at Peyton Hall † There are helpful manual entries under X and Xserver, as well as for individual utilities such as xterm. You may need to add /usr/princeton/X11/man to your MANPATH to read the X manpages. This is the first draft of this document, so I’d be very grateful for any comments or criticisms. Introduction to X’s Anatomy X consists of three parts: The server The part that knows about the hardware and how to draw lines and write characters. The Clients Such things as terminal emulators, dvi previewers, and clocks and The Window Manager A programme which handles negotiations between the different clients as they fight for screen space, colours, and sunlight. Another fundamental X-concept is that of resources, which is how X describes any- thing that a client might want to specify; common examples would be fonts, colours (both foreground and background), and position on the screen. Keys X can, and usually does, use a number of special keys. You are familiar with the way that <shift>a and <ctrl>a are different from a; in X this sensitivity extends to things like mouse buttons that you might not normally think of as case-sensitive.
    [Show full text]
  • Encapsulated Postscript Application Guide for Mac And
    Encapsulated PostScript Encapsulated PostScript Application Guide for the Macintosh and PCs Peter Vollenweider Manager User Services Universi1y of Zurich A ·Carl Hanser .Verlag :II Prentice Hall First published in German 1989 by Carl Hanser Verlag under the title EPS-Handbuch: Encapsulated PostScript First published in English 1990 by Prentice Hall International (UK) Ltd 66 Wood Lane End, Hemel Hempstead Hertfordshire HP2 4RG A division of Simon & Schuster International Group ©Carl Hanser Verlag, Munich and Vienna 1989 ©Carl Hanser Verlag and Prentice Hall 1990 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording or otherwise, witliout prior permission, in writing, from the publisher. For permission within the United States of America contact Prentice Hall, Inc., Englewood Cliffs, NJ 07632. The Sonata clef design on the cover shows the mixing of randomly placed Sonata font types, smoothed curves and patterns; courtesy of John F. Sherman, ND Design Program, University of Notre Dame, Indiana 46556, USA. Printed and bound in Great Britain by Dotesios Printers Ltd, Trowbridge, Wiltshire. Library of Congress Cataloging-in-Publication Data Vollenweider, Peter. (Encapsulated PostScript. English) Encapsulated PostScript : application guide for the Macintosh and PC's I Peter Vollenweider. p. em. Includes bibliographical references. ISBN 0-13-275843-1 1. PostScript (Computer program language) I. Title. QA76.73.P67V65 1990 005 .265-dc20 90-35469 CIP British Library Cataloguing-in-Publication Data Vollenweider, Peter Encapsulated PostScript : application guide for the Macintosh and PC's. 1. Microcomputer systems. Software packages I.
    [Show full text]
  • Oracle® Secure Global Desktop Platform Support and Release Notes for Release 4.7
    Oracle® Secure Global Desktop Platform Support and Release Notes for Release 4.7 E26357-02 November 2012 Oracle® Secure Global Desktop: Platform Support and Release Notes for Release 4.7 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S.
    [Show full text]
  • Security at Extreme Scales
    SECURITY AT EXTREME SCALES Recommended Citation Eric Grosse, "SECURITY AT EXTREME SCALES", NAPSNet Special Reports, May 30, 2019, https://nautilus.org/napsnet/napsnet-special-reports/security-at-extreme-scales/ ERIC GROSSE MAY 30, 2019 I. INTRODUCTION 1 In this paper, Eric Grosse argues: “Much of the security progress over the past decade has been at large-scale, finding and patching vulnerabilities in widely used applications or defending networks of millions of machines containing high-value data. The lessons there may help military systems, but for the very highest security needs such as NC3, we ought to return to basics and harden small-scale systems. And we ought to do it as a joint effort, even between adversaries.” Eric Grosse was Google's VP Security & Privacy Engineering. Before Google, Eric was a Research Director and Fellow at Bell Labs. He has a Ph.D. in Computer Science from Stanford. Acknowledgments: The workshop was funded by the John D. and Catherine T. MacArthur Foundation. This report is published simultaneously here by Technology for Global Security and here by Nautilus Institute and is published under a 4.0 International Creative Commons License the terms of which are found here. The views expressed in this report do not necessarily reflect the official policy or position of the Nautilus Institute. Readers should note that Nautilus seeks a diversity of views and opinions on significant topics in order to identify common ground. A podcast with Eric Grosse, Peter Hayes, and Philip Reiner on NC3 and security at extreme scales is found here. The views expressed in this report do not necessarily reflect the official policy or position of the Nautilus Institute.
    [Show full text]
  • A Successor to the X Window System
    Y: A Successor to the X Window System Mark Thomas <[email protected]> Project Supervisor: D. R¨uckert <[email protected]> Second Marker: E. Lupu <[email protected]> June 18, 2003 ii Abstract UNIX desktop environments are a mess. The proliferation of incompatible and inconsistent user interface toolkits is now the primary factor in the failure of enterprises to adopt UNIX as a desktop solution. This report documents the creation of a comprehensive, elegant framework for a complete windowing system, including a standardised graphical user interface toolkit. ‘Y’ addresses many of the problems associated with current systems, whilst keeping and improving on their best features. An initial implementation, which supports simple applications like a terminal emulator, a clock and a calculator, is provided. iii iv Acknowledgements Thanks to Daniel R¨uckert for supervising the project and for his help and advice regarding it. Thanks to David McBride for his assistance with setting up my project machine and providing me with an ATI Radeon for it. Thanks to Philip Willoughby for his knowledge of the POSIX standard and help with the GNU Autotools and some of the more obscure libc functions. Thanks to Andrew Suffield for his help with the GNU Autotools and Arch. Thanks to Nick Maynard and Karl O’Keeffe for discussions on window system and GUI design. Thanks to Tim Southerwood for discussions about possible features of Y. Thanks to Duncan White for discussions about the virtues of X. All company and product names are trademarks and/or registered trademarks of their respective owners.
    [Show full text]