DOCSLIB.ORG

Pv3 Server User's Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pv3 Server User's Reference Manual pV3 Server User's Reference Manual Rev. 2.05 for use with the following OpenGL workstations: Compaq ALPHAs HP workstations (HPUX 10.20 ACE) RedHat LINUX (Rev 6.1 or higher) IBM RS/6000 workstations (AIX 4.3 or higher) Silicon Graphics SUNs (Solaris 2.6 or higher) WindowsNT/2000 Bob Haimes Massachusetts Institute of Technology December 12, 2001 1 License This software is being provided to you, the LICENSEE, by the Massachusetts Institute of Technology (M.I.T.) under the following license. By obtaining, using and/or copying this software, you agree that you have read, understood, and will comply with these terms and conditions: Permission to use, copy, modify and distribute, this software and its documentation for any purpose and without fee or royalty is hereby granted, provided that you agree to comply with the following copyright notice and statements, including the disclaimer, and that the same appear on ALL copies of the software and documentation: Copyright 1993-2001 by the Massachusetts Institute of Technology. All rights reserved. THIS SOFTWARE IS PROVIDED \AS IS", AND M.I.T. MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITA- TION, M.I.T. MAKES NO REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE LICENSED SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. The name of the Massachusetts Institute of Technology or M.I.T. may NOT be used in advertising or publicity pertaining to distribution of the software. Title to copyright in this software and any associated documentation shall at all times remain with M.I.T., and USER agrees to preserve same. 2 Contents 1 Introduction 5 1.1 pV3 Startup . 5 1.1.1 Server Startup . 6 1.1.2 Environment Variables . 6 1.1.3 Special Files . 7 1.1.4 Notes on the Common Desktop Environment { CDE . 9 1.2 pV3 Time-Outs and Error Recovery . 9 2 The pV3 Server Users Interface 11 2.1 Surfaces . 11 2.2 Windows . 11 2.2.1 Text Window . 11 2.2.2 3D Window . 12 2.2.3 2D Window . 12 2.2.4 1D Window . 12 2.2.5 Key Window . 12 2.2.6 Dialbox Window . 13 2.3 Scalar Visualization Tools . 15 2.3.1 Surface rendering . 15 2.3.2 Planar Cutting plane . 15 2.3.3 Program-defined cutting plane . 16 2.3.4 Iso-surfaces . 16 2.4 Vector Visualization Tools . 17 2.4.1 Bubbles . 17 2.4.2 Instantaneous Streamlines . 18 2.4.3 Tufts . 19 2.4.4 Arrows . 19 2.4.5 Vector Clouds . 20 2.5 Grid . 20 2.6 Thresholding . 20 2.7 Probes . 21 2.8 Help Menus . 22 2.8.1 3D Window . 22 3 2.8.2 2D Window . 23 2.8.3 1D Window . 24 2.8.4 Key Window . 25 2.8.5 Dials Window . 26 2.9 Dialbox Functions . 28 3 Multi-Disciplinary Visualization 29 4 Collaboration 30 4.1 Help Menus . 31 4.1.1 Servers Window . 31 4.1.2 Servers Extract Window . 31 5 Post-Processing 33 5.1 tab2ps . 33 5.2 img2tiff . 33 5.3 img2ps . 34 5.4 img2X . 35 6 User Interface Differences with Visual3 36 7 Warning and Error Messages 38 4 1 Introduction pV3 is the newest in a series of graphics and visualization tools to come out of the Department of Aeronautics and Astronautics at MIT. Like it's predecessors Visual3, Visual2 and Grafic, pV3 is a software package aimed at aiding in the analysis of a particular suite of problems. In this case it is the real time visualization of 3D large scale solutions of transient (unsteady) systems. pV3 (which stands for parallel Visual3), is a completely new and different system, but builds heavily on the technology developed for Visual3. It has been designed specifically for co-processing visualization of data generated in a distributed compute arena. It is also designed to allow the solver to run as independently as possible. If the solution procedure takes hours to days, pV3 can `plug-into' the calculation, allow viewing of the data as it changes, then can `unplug' with the worst side-effect being the temporary allocation of memory and a possible load imbalance. pV3 provides the same kind of functionality as Visual3 with the same suite of tools and probes. The data represented to the investigator (the 3D, 2D and 1D windows with cursor mapping) is the same. Also the same Graphical User Interface (GUI) is used. pV3 programming is very Visual3-like. For the desired flexibility and the merging of the visualization with the solver, some programming is required. The coding is simple; like Visual3, all that is required of the programmer is the knowledge of the data. Learning the details of the underlying graphics, data extraction, and movement (for the visualization) is not needed. If the data is distributed in a cluster of machines, pV3 deals with this, resulting in few complications to the user. 1.1 pV3 Startup The PVM daemon(s) and with co-processing, the solver, must be executing. Without a pV3 server running, every time the solution is updated, a check is made for the number of members in the PVM group pV3Server (Note: this name can be changed for multiple jobs running under the same user ID { see the Section 1.1.2 for the environment variable `pV3 Group'). If no servers are found, no action is taken. When a pV3 server starts (usually from an interactive xterm session on the graphics workstation), it enrolls in the specified group. The next time the solution is updated, an initialization message is processed and the visualization session begins. Each subsequent time in the solver completes a time step, visualization state messages and extract requests are gathered, the appropriate data calculated, collected and sent to the active server(s). When the user is finished with the visualization, the server sends a termination message and exits. The clients receive the message, and if no other servers are running, cleans up any memory allocations used for the visualization. Then the scheme reverts to looking for server initialization, if termination was not specified at pV3 client initialization. 5 1.1.1 Server Startup The interactive server, pV3Server, takes three arguments at the command line (all optional). The first is the setup file with the default of `pV3.setup'. The second argument is the color file to be used at startup (the default is `spec.col'). The third argument is the extract start-up file. There is no default. An argument of ` ' is a place holder, allowing the default to be used. − examples: % pV3Server case.setup % pV3Server pV3.setup bw.col % pV3Server % pV3Server case.setup case.startup − 1.1.2 Environment Variables The pV3 server uses six Unix environment variables. Some are the same as the ones used for Visual3. The variable `Visual3 CP' defines the file path to be searched for color files, if they are not in the user's current directory. This allows all of the color files to be kept in one system directory. The second variable, `Visual KB' is optional. This variable, if defined, must point to a file that contains alternate keyboard bindings for the special keys used by pV3. The file is ASCII. The first column is the key name (10 characters) and the second is the X-keysym value in decimal (use `xev' to determine the appropriate values for the key strokes). The third is `pV3 TO' and should be used to change the internal Time-Out constant. If the variable is set, it must be an integer string which is the number of seconds to use for the Time-Out constant (the server's default is 60). This may be required if the time between solution updates is long. See Time-Outs and Error Recovery, Section 1.2. The fourth is `pV3 Threading'. This is used to specify how the interactive Server and the post- processing Viewer handles the handshaking between their active threads. There are two methods; (1) `Hard' where the thread sits in a hard loop (with a thread yeild) looking for a change of state, or (2) `Flag' where the threads use Semaphores for waiting until the state changes. The advantage of `Hard' is interactivity, the advantage for `Flag' is less processor time consumed. By default, this variable is set to `Hard' for most situations with single processor workstations and `Flag' for multi- processors. Exceptions: ALPHA's default is `Hard', SUN's default is `Flag', reguardless of number of processors. The fifth is `pV3 Group'. This is usefull for differentiating multiple PVM jobs running under the same user ID. If this variable is set for the solver (client-side) before execution, it overrides the default client side group name pV3Client. The name used is the string assigned to this variable with Client appended. By setting this variable before server execution, it will set the server group to the variable's string with Server appended instead of using pV3Server. Only clients with the appropraite matching group name will be connected to this session. The last is `pV3 Warning'. If this variable is set (to anything except a NULL string) warning messages about ACK and maximum streamline segments are not reported. 6 1.1.3 Special Files Window Manager Resource File • By default, all modern Xwindows Managers allow the closing or deleting of windows by either double-clicking on the menu pull-down or selecting `Close' or `Quit' from the pull-down.
Load more

Recommended publications
  • X Window System Version 6.4.2 Release Notes
    X Window System Version 6.4.2 Release Notes October 2000 0890298-6.4.2 READREAD MEME BEFOREBEFORE INSTALLINGINSTALLING THISTHIS PRODUCTPRODUCT Copyright Copyright 2000 by Concurrent Computer Corporation. All rights reserved. This publication or any part thereof is intended for use with Concurrent Computer Corporation products by Concurrent Computer Corporation personnel, customers, and end–users. It may not be reproduced in any form without the written permission of the publisher. Disclaimer The information contained in this document is subject to change without notice. Concurrent Computer Corporation has taken efforts to remove errors from this document, however, Concurrent Computer Corporation’s only liability regarding errors that may still exist is to correct said errors upon their being made known to Concurrent Computer Corporation. Concurrent Computer Corporation assumes no responsibility for the use or reliability of software if used on equipment that is not supplied by Concurrent Computer Corporation. License The software described in this document is furnished under a license, and it can be used or copied only in a manner permitted by that license. Any copy of the described software must include any copyright notice, trademarks or other legends or credits of Concurrent Computer Corporation and/or its suppliers. Title to and ownership of the described software and any copies thereof shall remain in Concurrent Computer Corporation and/or its suppliers. The licensed software described herein may contain certain encryptions or other devices which may prevent or detect unauthorized use of the Licensed Software. Temporary use permitted by the terms of the License Agreement may require assistance from Concurrent Computer Corporation.
    [Show full text]
  • No Slide Title
    Embedded Systems Class overview, Embedded systems introduction, Raspberry Pi, Linux OS, X-windows, Window manager, Desktop Environment Prof. Myung-Eui Lee (A-405) [email protected] Embedded Systems 1-1 KUT Embedded Systems Class Overview ⚫ Embedded Systems Class Operations » Past : 3 (credit) -2 (lecture) -2 (practice) » Now : 3 (credit) -1 (lecture) -1 (design) -2 (practice) » Future : 4 (credit) -2 (lecture) -2 (design) -0 (practice) ⚫ PBL : Problem or Project Based Learning » Problem : 4 problems » Project : 2 projects ⚫ 4 hours Class » 1 hour (lecture) + 1 hour (lecture or design) + 2 hours (practice) ▪ 1 hour (lecture) + 1 hour (lecture or design) : me ▪ 2 hours (practice) : Ph.D Park ⚫ Target Board : Raspberry Pi 3 » ARM + Linux Embedded Systems 1-2 KUT Embedded Systems Class Overview ⚫ Class Grade : » Mid Term Exam : 15 % [30 %] » Final Term Exam : 15 % [30 %] » Peer Evaluation : 10 % (Project #1 : 5% + Project #2 : 5%) » Project #1 Evaluation : 10 % » Project #2 Evaluation : 15 % » Experimental Lab. : 20 % [20 %] » Class Participation : 15 % [20 %] » Social Problem (Project #2) Optional : +5 % ⚫ Lecture Notes: http://microcom.koreatech.ac.kr Embedded Systems 1-3 KUT Embedded Systems ⚫ Definition of embedded system » Embedded system = H/W + S/W ▪ H/W = CPU + Memory + I/O ▪ S/W = Device driver + OS (or non OS) + Application program » Any electronic system that uses a CPU chip, but that is not a general-purpose workstation, desktop or laptop computer. » In embedded systems, the software typically resides in memory device, such as a flash memory or ROM chip. In contrast to a general-purpose computer that loads its programs into RAM each time. » Sometimes, single board and rack mounted general-purpose computers are called "embedded computers" if used to control.
    [Show full text]
  • The Virtualization Cookbook for SLES 10
    z/VM and Linux on IBM System z: The Virtualization Cookbook for z/VM 6.2 RHEL 6.2 and SLES 11 SP2 A “cookbook” for installing and customizing z/VM 6.2, RHEL 6.2 and SLES 11 SP2 on the mainframe Michael MacIsaac Brad Hinson Marian Gasparovic . Contents Preface . xi Parts of this book . xi Summary of changes in the July 2012 version . xi Summary of changes in the January 2012 version . xii Conventions . xiii Operating system releases used . xiii The team that wrote this book . xiii Special thanks . xiii Comments welcome. xiv Part 1. Introduction and z/VM . 1 Chapter 1. Introduction to z/VM and Linux . 1 1.1 What is virtualization? . 3 1.2 A philosophy adopted in this book . 4 1.3 Choices and decisions made in this book . 4 1.4 Single System Image design. 4 1.5 Infrastructure design . 5 1.6 Usability tests performed. 6 Chapter 2. Planning . 7 2.1 Planning for an SSI and LGR . 7 2.1.1 Hints and Tips . 7 2.1.2 Need for ECKD DASD . 9 2.2 Bill of materials . 9 2.2.1 Hardware resources . 9 2.2.2 Software resources . 9 2.2.3 Networking resources . 10 2.3 z/VM conventions . 10 2.3.1 Volume labeling convention . 10 2.3.2 Backup file naming convention . 11 2.3.3 The command retrieve convention . 11 2.4 Disk planning. 12 2.5 Memory planning. 13 2.6 Password planning . 13 2.7 Planning worksheets . 14 2.7.1 z/VM resources used in this book .
    [Show full text]
  • Bonus Chapter B Programming for X
    Bonus Chapter B Programming for X In this chapter and the next, we’ll take a look at writing programs to run in the usual Linux graphical environment, the XWindow System or X, http://www.x.org/Xorg.html. Modern UNIX systems and nearly all Linux distributions are shipped with a version of X. We’ll be concentrating on the programmer’s view of X, and we’ll assume that you are already comfortable with configuring, running, and using X on your system. We’ll cover ❑ X concepts ❑ X Windows managers ❑ X programming model ❑ Tk—its widgets, bindings, and geometry managers In the next chapter, we’ll move on to the GTK+ toolkit, which will allow us to program user interfaces in C for the GNOME system. What Is X? X was created at MIT as a way of providing a uniform environment for graphical programs. Nowadays it should be fair to assume that if you’ve used computers, you’ve come across either Microsoft Windows, X, or Apple MacOS before, so you’ll be familiar with the general concepts underlying a graphical user interface, or GUI. Unfortunately, although a Windows user might be able to navigate around the Mac interface, it’s a different story for programmers. Each windowing environment on each system is programmed differently. The ways that the display is handled and the programs communicate with the user are different. Although each system provides the programmer with the ability to open and manipulate windows on the screen, the functions used will be different. Writing applications that can run on more than one system (without using additional toolkits) is a daunting task.
    [Show full text]
  • Common Desktop Environment 1.0 Programmer's Overview
    Common Desktop Environment 1.0 Programmer’s Overview This edition of the Common Desktop Environment Advanced User’s and System Administrator’s Guide applies to AIX Version 4.2, and to all subsequent releases of these products until otherwise indicated in new releases or technical newsletters. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19. THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The code and documentation for the DtComboBox and DtSpinBox widgets were contributed by Interleaf, Inc. Copyright 1993, Interleaf, Inc. Copyright 1993, 1994, 1995 Hewlett-Packard Company Copyright 1993, 1994, 1995 International Business Machines Corp. Copyright 1993, 1994, 1995 Sun Microsystems, Inc. Copyright 1993, 1994, 1995 Novell, Inc. All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization. All rights reserved. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and AR 52.227-19. Part 1 —Common Desktop Environment Architectural Overview 1. Architectural Overview. 1 Conceptual Overview. 1 Data Interaction GUIs. 2 Multiuser Collaboration. 3 Desktop Management.
    [Show full text]
  • Abkürzungs-Liste ABKLEX
    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
    [Show full text]
  • 007-2006-100 Contributors
    Indigo Magic™ Desktop Integration Guide Document Number 007-2006-100 CONTRIBUTORS Written by Beth Fryer, Jed Hartman, Ken Jones, and Pete Sullivan Illustrated by Beth Fryer and Seth Katz Edited by Christina Cary Production by Derrald Vogt, Cindy Stief, and Linda Rae Sande Engineering contributions by Bob Blean, Susan Dahlberg, Susan Ellis, John Krystynak, Chandra Pisupati, Jack Repenning, CJ Smith, Dave Story, Steve Strasnick, Rebecca Underwood, Steve Yohanan, and Betsy Zeller St Peter’s Basilica image courtesy of ENEL SpA and InfoByte SpA. Disk Thrower image courtesy of Xavier Berenguer, Animatica. © Copyright 1994, 1995, 1996 Silicon Graphics, Inc.— All Rights Reserved The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311. Silicon Graphics, the Silicon Graphics logo, and IRIS are registered trademarks and IRIS, IRIS GL, IRIS IM, IRIS InSight, IRIS ViewKit, IRIX, GoldenGate, IconSmith, Indigo Magic, the Graphics Library, OpenGL, Open Inventor, and RapidApp are trademarks of Silicon Graphics, Inc. Apple is a registered trademark and Apple Quicktime is a trademark of Apple Computer, Inc.
    [Show full text]
  • An Introduction to X Window Application Development
    Calhoun: The NPS Institutional Archive Theses and Dissertations Thesis Collection 1992-03 An introduction to X Window application development. Rust, David Michael Monterey, California. Naval Postgraduate School http://hdl.handle.net/10945/23933 FV KNOX LIBRARY •Ud SCHOOL SivAL POSTGRADUATE SoNTEHEV.CAUFORN.AG^^ CURITY CLASSIFICATION OF THIS PAGE REPORT DOCUMENTATION PAGE 1b. RESTRICTIVE MARKINGS REPORT SECURITY CLASSIFICATION UNCLASSIFIED a SECURITY CLASSIPICAT I6M AUTH6RITV 3. bisTRiBuTi6N7AVAlLABiUTY 6P REP5RT Approved for public release; b. dECLAssIFICATIoN/doWNgRADINg SCHEDULE distribution is unlimited PERFORMING ORGANIZATION REP6RT NUM&ER(S) 5. M6niT6Ring6Rgani2aTi6n rep6rT numbER(S) *. NAME 6F PERFORMING 6R6ANIZATI6N 6b OFFICE SYMBOL 7a. NAME 6E M6NIT6R1NG ORGANIZATION vdministrative Sciences Department (if applicable) Naval Postgraduate School Javal Postgraduate School AS :. ADDRESS (City, State, and ZIP Code) 7b. ADDRESS (City, State, and ZIP Code) /lonterey, CA 93943-5000 Monterey, CA 93943-5000 NAME OF FUNDING/SPONSORING 8b. OFFICE SYMBOL g PROCURE M E N T I NST RUMEN T ID E N T I FI CATION NUMBE R ORGANIZATION (if applicable) 6. ADDRESS (City, State, and ZIP Code) 10. SOURCE OF FUNDING NUMBERS PROGRAM 1 PR6JECT TTa^R" WoRkUNiT ELEMENT NO. NO. NO. ACCESSION NO. 1 . TITLE (Include Security Classification) ^N INTRODUCTION TO X WINDOW APPLICATION DEVELOPMENT (U) 2 PERSONAL AUTHOR(S) lust, David M. 3a. type of report 13b. time covered 14. DATE OF REPORT (Year, Month, Day) 16. PAGE COUNT Master's Thesis from 10/90 to 03/92 1992, March, 23 70 supplementary notation 6 The views expressed in this ^sis ^ those of the author md do not reflect the official policy or position of the Department of Defense or the United States Government.
    [Show full text]
  • Operációs Rendszerek III. Az X Window Rendszer Működése Kliens-Szerver Modell Használata
    Operációs rendszerek III. X WindowSystem Az X Window rendszer Grafikus alkalmazások felhasználói felületének megjelenítése. · 1983-84: a Massachusetts Institute of Technology- n (MIT, USA). · Azonos kezelői felületet különböző operációs rendszereken. · Működés: az alkalmazás és a kezelői felület szétválasztása. · Forráskódja publikus. (Elsősorban a UNIX rendszerek támogatják.) vasárnap, 2005. november Dr. BenyóBalázs 27. Operációs rendszerek III. X WindowSystem X munkahely X protokoll X szerver Távoli kliens képernyő képernyő alkalmazás vasárnap, 2005. november Dr. BenyóBalázs 27. Operációs rendszerek III. X WindowSystem vasárnap, 2005. november Dr. BenyóBalázs 27. Operációs rendszerek III. Az X Window rendszer működése Kliens-szerver modell használata. A szerver kezeli az ún. grafikus munkahelyet, melynek részei: · képernyő (ill. képernyők), · billentyűzet (alfanumerikus bemeneti eszköz), · egy grafikus bemeneti eszköz. A kliens egy grafikus kimenetű (általában vasárnianp, 2t00era5. novembkert ív) folyamDr.a Benyt.óBalázs 27. Operációs rendszerek III. Az X protokoll Az X protokoll •A rendszer magja az X protokoll: · Definiálja a kliens és a szerver együttműködésének módját. •A protokoll kétirányúaszinkron kommunikációt tesz lehetővé. vasárnap, 2005. november Dr. BenyóBalázs 27. Operációs rendszerek III. Az üzenetek típusai · Kérés (kliens küldi a szervernek). · Válasz (szerver küldi a kliensnek). · Esemény (szerver küldi a kliensnek). · Hiba (szerver küldi a kliensnek). vasárnap, 2005. november Dr. BenyóBalázs 27. Operációs rendszerek III. A hálózati kommunikáció mérséklése · Kliens: · üzenetek összegyűjtött csomagját küldi át · Szerver: · helyben kezel egyszerű eseményeket (pl. egérmozgatás). · szoftver erőforrásokat hoz létre · pl. palettát, grafikus környezetet, betűtípushoz tartozóleírást, stb. · erőforrás kezelése: · létrehozás kliens kérésére · a kliens folyamat egyszerű hivatkozással érhet el vasárnap, 2005. november Dr. BenyóBalázs 27. Operációs rendszerek III. X Windowrendszer működése Az X Window rendszer koncepciója Alapvető elem a grafikus, ún.
    [Show full text]
  • Technical Standard X/Open Common Desktop Environment (XCDE
    Technical Standard X/Open Common Desktop Environment (XCDE) Services and Applications NICAL H S C T A E N T D A R D [This page intentionally left blank] X/Open CAE Specification X/Open Common Desktop Environment (XCDE) Services and Applications X/Open Company Ltd. March 1995, X/Open Company Limited 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, without the prior permission of the copyright owners. X/Open CAE Specification X/Open Common Desktop Environment (XCDE) Services and Applications ISBN: 1-85912-074-1 X/Open Document Number: C323 Published by X/Open Company Ltd., U.K. Any comments relating to the material contained in this document may be submitted to X/Open at: X/Open Company Limited Apex Plaza Forbury Road Reading Berkshire, RG1 1AX United Kingdom or by Electronic Mail to: [email protected] ii X/Open CAE Specification Contents Chapter 1 Window Management Services..................................................... 1 1.1 Introduction ................................................................................................. 1 1.2 Data Formats................................................................................................ 2 Chapter 2 Workspace Management Services ............................................... 3 2.1 Introduction ................................................................................................. 3 2.2 Functions .....................................................................................................
    [Show full text]
  • Motif Reference Manual for Openmotif 2.3
    THE DEFINITIVE GUIDES TO THE X WINDOW SYSTEM VOLUME SIX B Motif Reference Manual for OpenMotif 2.3 Open Source Edition Based upon the manual writted by Antony Fountain and Paula Ferguson, O’Reilly and Associates Updated and Published by Peter Winston and the Technical Staff of Integrated Computer Solutions, Inc. Motif Reference Manual, Open Source Edition for OpenMotif version 2.3 Copyright ©2005 by Integrated Computer Solutions, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). December 2001 Copyright ©1993, 2000, 2001 by O’Reilly & Associates, Inc. and Antony Fountain. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). This is an updated version of the Motif Reference Manual, Open Source Edition for Motif 2.1, published by Imperial Software Technology in December 2001. The source files for this version of the document are available at http://www.motifzone.org. The source files for the Open Source Edition can be found at http://www.ist.co.uk/motif/motif_refs.html. A description of the modifications is contained in the Preface to the Open Source Edition. The Open Source Edition is a modified version of the Motif Reference Manual, Second Edition, published by O’Reilly & Associates in February 2000. The source files for the Second Edition can be found at http://www.oreilly.com/openbook/motif/.
    [Show full text]
  • Motif Programming Manual 1 Preface
    Motif Programming Manual 1 Preface...........................................................................................................................................................................1 1.1 The Plot..........................................................................................................................................................1 1.2 Assumptions...................................................................................................................................................2 1.3 How This Book Is Organized........................................................................................................................3 1.4 Related Documents........................................................................................................................................5 1.5 Conventions Used in This Book....................................................................................................................6 1.6 Obtaining Motif.............................................................................................................................................6 1.7 Obtaining the Example Programs..................................................................................................................7 1.7.1 FTP.................................................................................................................................................7 1.7.2 FTPMAIL......................................................................................................................................7
    [Show full text]