DOCSLIB.ORG

Virtual Window Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Virtual Window Systems Virtual WindowSystems: A New Approachto SuppoitingConcurrent HeterogeneousWindowing Systems RitaPascale, Jeremy Epstein - TRW SystemsDivision ABSTRACT A "virtual window systeml' (VIWS)is a simple model of a window systemwhich can be used to host other more sophisticatedwindow systems. The VWS allows the window systemsto sharethe.phys_ical 9ppl.y in a controlledfashion. A VWS is analogousto the virtual machinemonitor (vMM) [MadnickT4]concept in operatingsystems, where a single ghysical compr¡ter-canrun multiple operatingsystems, each in itõ o-*n protectiondomain. Unlike the VMM concept, the window iysiems supportedby the VWS need close cooperationto perform'tasks,such as cut and pastebetween wináows of differentwindow systems. -- . This paperdescribes the VWS concept,discusses an architecturefor a VWS, describes limitations of the \l[VS concept, discusies some lessonslearned from the design and implementationof our prototype,and describesthe use of WVSs for various application domains. Introduction MacOS and X; X-under-NeXTstepfrom pencom which Userswant to run more than one window svs_ combinesNeXT and X; and Domain from combinesApollols native tem (WS) simultaneouslyon a single platiãi.. ínr f¡to,llo_which WS and X. somesystems which combine usersare a very diverseset whose-neeãsrange from 1Ti:-*. threewin- debuggingto together(i.e., X11/l.IeWSand téachingto running a variety oiuppn *Y,tlq "."lironments catiolL ihe systeni developerneeds an r¡f;ãii* but three seemsto be.the maximum. By beingfu.nvi3¡v), debuggingtool ior window syrte*s an¿ tfreir áppfi- limited to two or three environments,-many of of the vWS are possible. cationl. lhe instructor needéa flexible .yrì"iñ'ìà llt^ :jli,.ges .not The thesesystems fulfill js the teachin as many environmenrsas possiUié-;-;;; 1l_tjln"rigl ability to run machine.The everyday userneeds'to *" .ppfU: mixed applicationsand this hasbeen argued as not tions built for more than one window system,ä'tr.h- being a great advantage. niquewhich we call applications". "mixed Goals We proposea generalsolution to allow many as many of the variousneeds of the windowing eìvironnientsto run cooperativetyf-iä ,,-.^_^t^o.meet refer to iias the "virtual window system,'iVWSj group' we need a small, but flexible :1-1t::-.usersystem conceprt. A wVS is a simple model of . ìinàoí base. To avoid the temptationof buildÍngÏÎ1?: an entire systemwhich canbe usedto hostott *orr-.ootrjr- new windowsystem' the sizeis to "t and minimal,using as few primitives titated window systems.Tltr ñ;t;ñtt..r.d'W'ú :: fj:,:tttl Deslte this minimality, we wish to are considered"'guests" on the vws prærotit'åiã 1l_l,o_ttlblt'. may be referredîo as gue.t WS. The Vws'.ir"*. flexible.The set of primitivesmust provide i:T1iT functionality disparateWSs to shareúe physicaldisplay i" ;;;;: to accommodateany window system':::.T* trolled fashion and provideì ã mecnanismfor com- municationacross Vy'Ss. The primitivesbetween the guestWSs and the c.al be into connection When comparedto similar systems,the VWS is YYI-.^tyt"m .grouped much more veisatile. Hybrid ws ånuironrJni, startupinformation, input data, and output ilglt:lll '$ority combinetwo parricularsystäms and provide,ltr'.uii: of the primitives deal with chang- Í-1t:Jn: such as requests ity ro run apitications fiom the t*ó ;Ñifiä wö, lo map and unmãp 11åjÏ.^ditptav,update onty. nxampiesof thesehybrid systemi utr ñiriãn windows, and changethe window T1i1-?:t'stacking order. trom Visior¡Vare which óombinósf"ficro.ofi'.äi-n_ ',' Overall, there are fewer than 20 primitiveswhich.is dowsand X; MacX from Macintoshwhich co, '-' -significantlyless than the 120 @bytheDefense^--".irotocolrequestsi"tr'"î''*'i[Scheifler90]. ResearchProjects Agency under Contract No. MDA 972- 89-C0029. '92 - Summer USENIX June8-Junþ LZ, Lggz - SanAntonio. TX LL7 Virtual l{indow Systems Pascale,Epstein Detalls of the Problem all supportedWSs, and this is the most common form of datatransfer. There are a number of problemsinvolved in hostingmany environmentsand protocols on a single Method platform.The main areasto addressare randomdev- ice accessesand overcomingdifferent protocols. Our solution provides a mechanismto control device accessand regulate inter-environment(and Access to the keyboard,mouse, console and intra-environment)communication. The VWS per- framebuffermust be regulated. Allowing each WS forms theseactions through three logical servers:an all input at all times would result in massconfusion input manager,an ouÞut manager,and a control since eachWS interpretsdata differently. A mouse server.The input managerroutes the input click in one environmentmay pop up a menu,while to a sin- gle designatedwindow system.The output manager in anotherit may causean applicationto exit, and in displayseach window system'soutput the yet another,the data format may not evenbe valid. on screen while handling window overlapping Unlimited access to the screen will allow guest and clipping. The control serveris inactive,except for administra- WSs2 to cause chaos by drawing on top of one tive duties.Figure 1 showsthe interactions another's windows, creating a confusing mesh between of the VWS guest partial windows. and the WSs. Each guestWS must be modified to virtualize Another difficulty is cut and pasteacross WSs. its device access. Input is receivedfrom the input Each systemsupports a differentmechanism through managerinstead of readingthe devices different protocols. A primitive method must be directly and drawing is performedin a virtual developedthat can cut across these various plat- framebufferand then sent to the output managerfor display. forms. One drawbackof being genericis that unique These modificationsare necessarysince there data formats are not supported. For example,h X is no direct accessto the hardwaredevices. The guest must resource ids (instead of the actual WS [Scheifler90], also requestservices of the threeVWS serversusing data) can be cut and pasted;this id is only useful minimal primitives. A possibledrawback to the vi¡- within that particular instantiationof the X server tualizedouÞut is that there is no advantageof using and is not meaningfulto any other WS process.At intelligentgraphics boa¡ds unless they the very least,ASCII text can be transferredbetween can utilize the virtual framebuffers. In the WVS environment,there is always one 2By guestwindow system,we mean a window system active WS which receivesall input from the input environmentthat is supportedand hostedby the vi¡tual manager. Any other running system is passive, window system. meaningit can sendupdates to the screen,but does oaaaa Figure 1: VWS Interactions 118 Summer '92 USENIX - June 8-June 12,lgg2- San Antonio, TX Pascale,Epstein VÍrtual Window Systems not receiveany input. Interpretationof the input is pasted.At a minimum,guest WSs must supporta the responsibility of the active window system, canonicaltext format for interoperability.Additional meaningit is up to the guest\VS to sendthe input formats-maybe supported,but their interoperability eventsto the appropriateclients and processthem as is less.likely. This may be a disadvantagèto sys- dictated by its own internal protocol. The input tems that have unique data forms, such as resource manager'sonly interactionwith the input is scanning ids in X. for the attentionsequence which activátesthe control The primitives sent from the guest \VS to the server. The control server is activatedstrictlv on control server are connectionrequests, cut data certainkeyboard input, not clicking on an icon.'This and paste requests.The control server respondsto the is becausemouse position (at thelime of the click) pasterequests with the most recentcut is up to interpretationper guestWS. data that meetsthe criteria specifiedby the guestWS. The only primitives f¡om the guest WS to the With minimal changes,existing WSs can input managerare connectionrequeits and requests be modifiedto work within the VIVS environment.How to ring the bellr. lnput managerprimitives to the closelythe window system'simplementation is tied guest\ryS provide keyboard and mouseinput, initial- to the hardwaredictates the amountof chanee. ization data, and notification of X is selection and very modular and encapsulates deselectionby the user. its device-usage; therefore, it was quite simple to change. We The output server controls the mapping and modifiedthe MIT X11R4 serverfor Sun ha¡ãwarerc rffSs unmappingof windows from the various as acceptinput from the input serverand displayoutput well as handlingstacking order, screenupdates and throughthe outputmanager with a few hundiedlines cursor_imaging. Becauseno sophisticatedgraphics of code. Modifying the Macintosh WS would be operationsare provided,the outputmanager is much much more complicatedbecause of its closerelation- simpler than the output componentof ãn ordinary ship with its hardware,but we believethat even this windowsystem. Performance is the costof this sim- can be overcome. plicity, but having such base primitives makes the ouÞut .managermore adoptive of other WSs. A Details on Vl{S Uses disadvantageof this schemeis that the screenback- The VWS exhibitsgreat versatility in its ability ground is not for use by any guestwindow system. to handle a wide variety of needs in a minimãl A mechanismis provided to draw helping lines for 'and amountof code. WVS neither enhancesnor detracts placing, moving resizing windows, but other from the given graphicaluser interface;if the guest applicationsthat draw directly on the screen back- WS is poor, it will remain
Load more

Recommended publications
  • 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]
  • A Political History of X Or How I Stopped Worrying and Learned to Love the GPL
    A Political History of X or How I Stopped Worrying and Learned to Love the GPL Keith Packard SiFive [email protected] Unix in !"# ● $SD Everywhere – $'t not actually BS% ● )*+* want, to make Sy,tem V real – S'rely they still matter ● .o Free So/tware Anywhere The 0rigins of 1 ● $rian Reid and Pa'l Asente at Stan/ord – - kernel → VGTS → W window system – Ported to VS100 at Stan/ord ● $o4 Scheifler started hacking W→ X – Working on Argus with Barbara Liskov at LCS – 7ade it more Unix friendly (async9, renamed X -AXstation 00 (aka v, 339 Unix Workstation Market ● Unix wa, closed source ● Most vendors ,hipped a proprietary 0S 4ased on $SD #.x ● S'n: HP: Digita(: )po((o: *ektronix: I$7 ● ;congratu(ation,: yo'<re not running &'nice=. – Stil(: so many gratuito', di/ference, -AXstation II S'n >?@3 Early Unix Window Systems ● S'n-iew dominated (act'al commercial app,A De,ktop widget,A9 ● %igital had -WS/UIS (V7S on(y9 ● )pollo had %omain ● *ektronix demon,trating Sma((*alk 1 B1@ ● .onB/ree so/tware ● U,ed internally at MIT ● Shared with friend, in/ormally 1 3 ● )(mo,t u,able ● %elivered by Digital on V)1,tation, ● %i,trib'tion was not all free ,o/tware – Sun port relied on Sun-iew kernel API – %igital provided binary rendering code – IB7 PC?2T support act'ally complete (C9 Why 1 C ● 1 0 had wart, – rendering model was pretty terrible ● ,adly, X1 wa,n't m'ch better... – External window management witho't borders ● Get everyone involved – Well, at lea,t every workstation vendor willing to write big checks X as Corporate *ool ● Dim Gettys and Smokey
    [Show full text]
  • Solaris 2.5 Software Developer Kit Introduction
    Solaris 2.5 Software Developer Kit Introduction 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. A Sun Microsystems, Inc. Business 1995 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from UNIX Systems Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s Suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, Sun Microsystems, the Sun logo, SunSoft, the SunSoft logo, Solaris, SunOS, OpenWindows, DeskSet, ONC, ONC+, NFS, SunExpress, ProCompiler, XView, ToolTalk, XGL, XIL, Solaris VISUAL, Solaris PEX, and AnswerBook are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CatalystSM is a service mark of Sun Microsystems, Inc.
    [Show full text]
  • Sunscreen SKIP Open Issues and Late-Breaking News, Release 1.1.1
    SunScreen SKIP Open Issues and Late-breaking News, Release 1.1.1 Sun Microsystems, Inc. 901 N. San Antonio Road Palo Alto, CA 94303-4900 U.S.A. Part No: 805-6051–10 June 1998, Revision A Copyright 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, SunSoft, SunDocs, SunExpress, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.
    [Show full text]
  • UNIX® Systel11 V 1386 Release
    UNIX® Systel11 V1386 Release 3.2 Foundation Set and User Interface Utilities The UNIX System V/386 Release 3.2 Foundation Set provides the highly portable, multitasking and mUlti-user UNIX System V environment permitting many users to simultaneously run application software and share programs and data. It features a hierar­ chical file system, system access and file security, job control, interprocess communication, 1/0 redirection, and a versatile command set providing numerous tools for information retrieval, data manipulation, report generation, and task scheduling. Release 3.2 enhancements enable the system to run application software developed to XENIX® System V/386 (Release 2.2.0 and later) and XENIX System V/286 (Release 2.0 and later) as well as the many programs developed for UNIX System V/386 (Release 3.0 and later) and 6300 PLUS UNIX System V (Release 2.0 and later). The system also supports AT&T's Simul-Task 386 and XWIN Graphical Windowing System featuring AT&T OPEN LOOJ(TM Window Manager. Included with each Foundation Set product are the AT&T User Interface Utilities, FMLI and FACE, providing the user with a logical view of the UNIX System V environment. It presents easy-to-use menus to commonly used commands, task scheduling, program services, arid administration. The UNIX System V/386 Release 3.2 Foundation Set and User Interface Utilities is supported by AT&T for use on the 6386 and 6386E WorkGroup Systems. The product requires a minimum of 2 megabytes of random access memory and a hard disk drive with 30 megabytes of free space for installation and operation.
    [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]
  • SYSTEM V RELEASE 4 Migration Guide
    - ATlaT UN/~ SYSTEM V RELEASE 4 Migration Guide UNIX Software Operation Copyright 1990,1989,1988,1987,1986,1985,1984,1983 AT&T All Rights Reserved Printed In USA Published by Prentice-Hall, Inc. A Division of Simon & Schuster Englewood Cliffs, New Jersey 07632 No part of this publication may be reproduced or transmitted in any form or by any means-graphic, electronic, electrical, mechanical, or chemical, including photocopying, recording in any medium, tap­ ing, by any computer or information storage and retrieval systems, etc., without prior permissions in writing from AT&T. IMPORTANT NOTE TO USERS While every effort has been made to ensure the accuracy of all information in this document, AT&T assumes no liability to any party for any loss or damage caused by errors or omissions or by state­ ments of any kind in this document, its updates, supplements, or special editions, whether such er­ rors are omissions or statements resulting from negligence, accident, or any other cause. AT&T furth­ er assumes no liability arising out of the application or use of any product or system described herein; nor any liability for incidental or consequential damages arising from the use of this docu­ ment. AT&T disclaims all warranties regarding the information contained herein, whether expressed, implied or statutory, including implied warranties of merchantability or fitness for a particular purpose. AT&T makes no representation that the interconnection of products in the manner described herein will not infringe on existing or future patent rights, nor do the descriptions contained herein imply the granting or license to make, use or sell equipment constructed in accordance with this description.
    [Show full text]
  • Solaris Advanced User's Guide
    Solaris Advanced User’s Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 806–7612–10 May 2002 Copyright 2002 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, SunOS, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • Download UNIX System V, Release 4: Programmer's Guide
    UNIX System V, release 4: programmer's guide : X11/NeWS graphical windowing system NeWS., Volume 1, , Prentice-Hall, 1990, 0139318259, 9780139318252, . DOWNLOAD HERE http://bit.ly/1aeO97C UNIX System V/386, release 4 MULTIBUS reference manual, , 1990, Computers, . Unix System V Release 4: Migration Guide, Volume 7 Migration Guide, , Jan 1, 1990, Computers, . System V Application Binary Interface Sparc Processor Supplement, , May 1, 1990, Computers, . System V Binary Compatibility Specification WE 32000 Processor Supplement, , May 1, 1990, Computers, . UNIX System V, release 4 Programmer's guide, STREAMS, UNIX System Laboratories, 1992, Computers, 608 pages. A full explanation of the STREAMS I/O facilities, this guide details how to use those facilities for writing UNIX System V kernel modules and device drivers. STREAMS is a .... System V interface definition , AT & T, UNIX System Laboratories, 1991, Computers, 528 pages. Specifies an operating system environment that allows users to create applications software that is independent of any particular computer hardware.. Unix System V/386, release 4: programmer's reference manual, Page 77 programmer's reference manual, American Telephone and Telegraph Company, 1990, Computers, 1160 pages. Unix System V Release 4 The Complete Reference, Stephen Coffin, Oct 1, 1990, Computers, 905 pages. No other reference available today can give you as much detailed information on all the new features and many enhancements of UNIX System V Release 4.. XView reference manual, Volume 7 , Thomas Van Raalte, Sep 8, 1991, Computers, 311 pages. XView was developed by Sun Microsystems and is derived from Sun's proprietary programming toolkit, SunView. It is an easy-to-use object-oriented toolkit that provides an OPEN ...
    [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]
  • MIT 150 | Project Athena - X Window System Users and Developers Conference, Day 1 [3/4] 1/14/1987
    MIT 150 | Project Athena - X Window System Users and Developers Conference, Day 1 [3/4] 1/14/1987 [MUSIC PLAYING] PALAY: My name is Andrew Palay I work at the Information Technology Center at Carnegie Mellon University. For those who don't know, the Information Technology Center is a joint project between Carnegie Mellon University and IBM. It also has some funding from the National Science Foundation. This talk is going to cover the Andrew toolkit. I'd like to begin this talk by providing a short example of what the toolkit's all about. In particular, how I made this slide. And actually some of the other slides. So I basically had the editor. In this case, I had typed in the text. And I selected a spot of the text and essentially asked to add a raster. This particular place, I added a raster. This object that we add into these will be referred to, and are referred to by the toolkit, as insets. The inset comes up as its default size, given that I've added nothing to it. I then request to read a known raster from the file, And this point, in this case the ITC logo. If you note, the actual inset itself hasn't increased in size to accommodate the raster image. The user has control over that size, can actually make it larger or smaller. Later in the talk, another slide you will see actually has a drawing. In this case, I selected areas that I wanted the drawing, actually created the drawing in place.
    [Show full text]
  • Porting X Windows System to Operating System Compliant with Portable Operating System Interface
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 11, No. 7, 2020 Porting X Windows System to Operating System Compliant with Portable Operating System Interface Andrey V. Zhadchenko1, Kirill A. Mamrosenko2, Alexander M. Giatsintov3 Center of Visualization and Satellite Information Technologies Scientific Research Institute of System Analysis Moscow, Russia Abstract—Now-a-days graphical interface is very important separated process contexts [4]. Current graphical subsystem for any operating system, even the embedded ones. Adopting is server-client X windows system implementation named existing solutions will be much easier than developing your XFree86 with version 4.8.0. Although XFree86 [5] supports up own. Moreover, a lot of software may be reused in this case. to the X11R6.6 protocol version, which is barely enough to run This article is devoted to X Window System adaptation for modern applications, absence of many important extensions, Portable Operating System Interface (POSIX) compliant real- for example, Xrender [6], implies heavy limits upon software. time operating system Baget. Many encountered problems come from the tight connection between X and Linux, therefore it is expected to encounter these issues during usage of X on non- Nowadays existing free software solutions in display Linux systems. Discussed problems include, but not limited to servers for operating systems are limited to two options: X the absence of dlopen, irregular file paths, specific device drivers. Windows System and Wayland [7]. However, there is a big Instructions and recommendations to solve these issues are given. ideological difference between them. X started it’s history a A comparison between XFree86 and Xorg implementations of X long time ago in the ’80s and was developed as an all-around is discussed.
    [Show full text]