DOCSLIB.ORG

Qnx® Photon® Microgui® V6.3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Qnx® Photon® Microgui® V6.3 QNX® PHOTON® MICROGUI® V6.3 PROGRAMMER’S GUIDE QNX Neutrino Realtime Operating System Photon microGUI Programmer’s Guide For QNX Neutrino 6.3.0 2005, QNX Software Systems 1995 – 2005, QNX Software Systems. All rights reserved. Printed under license by: QNX Software Systems Co. 175 Terence Matthews Crescent Kanata, Ontario K2M 1W8 Canada Voice: +1 613 591-0931 Fax: +1 613 591-3579 Email: [email protected] Web: http://www.qnx.com/ Publishing history November 1995 First edition December 1996 Second edition April 1998 Third edition July 2004 Fourth edition Electronic edition published 2005. Technical support options To obtain technical support for any QNX product, visit the Technical Support section in the Services area on our website (www.qnx.com). You’ll find a wide range of support options, including our free web-based Developer Support Center. QNX, Momentics, Neutrino, and Photon microGUI are registered trademarks of QNX Software Systems in certain jurisdictions. All other trademarks and trade names belong to their respective owners. Contents About This Guide xxxi Typographical conventions xxxiii Note to Windows users xxxiv What you’ll find in this guide xxxv What’s new in Photon for QNX Neutrino 6.3 xxxvii New content xxxvii What’s new in Photon for QNX Neutrino 6.2.1xxxviii New contentxxxviii Errataxxxviii What’s new in Photon for QNX Neutrino 6.2.0 xxxix New content xxxix What’s new in Photon for QNX Neutrino 6.0 xxxix 1 Introduction 1 Overview of the Photon architecture 3 Photon Application Builder (PhAB) 6 Widget concepts 8 Widget life cycle 13 Widget geometry 14 Programming paradigm 17 Text-mode application 18 Non-PhAB application 19 PhAB application 20 Photon libraries 21 API categories and libraries 21 October 6, 2005 Contents iii 2005, QNX Software Systems Versions and platforms 23 Building applications with PhAB — an overview 24 Step 1: Create modules 25 Step 2: Add widgets 25 Step 3: Attach callbacks 26 Step 4: Generate code 27 Step 5: Run your application 27 Step 6: Repeat any previous step 28 Writing applications without PhAB 28 2 Tutorials 29 Before you start... 31 Creating a Photon project and starting PhAB 31 PhAB’s Interface 32 Tutorial 1 — Hello, world 34 Creating the application 34 Generating code 36 Want more info? 38 Tutorial 2 — editing resources 38 Adding a button widget 39 Changing the bevel width 39 Changing the font 40 Changing the text alignment 42 Setting flags 43 Changing the fill color 44 Editing a pixmap 45 Editing multiline text 46 Editing a list of text items 48 Creating a template 50 Want more info? 53 Tutorial 3 — creating menus and menubars 54 About link callbacks 54 About instance names 55 iv Contents October 6, 2005 2005, QNX Software Systems Creating a menubar 55 Creating the File menu module 56 Adding menu items 57 Creating the Help menu module 59 Attaching link callbacks 59 Setting up the code 62 Want more info? 63 Tutorial 4 — creating dialogs 63 About dialogs 64 More on instance names 64 Attaching a dialog module 65 Adding widgets to the dialog 66 Adding a callback to the Done button 69 Modifying a generated code function 70 Compiling and Running 71 Want more info? 72 Tutorial 5 — creating windows 72 Creating a window 73 Attaching callbacks 73 Adding widgets 74 Generating and modifying the code 77 Compiling and running 81 Want more info? 81 3 PhAB’s Environment 83 Menus 85 File menu 85 Edit menu 86 Project menu 88 Build menu 89 Widget menu 91 View menu 92 Window menu 93 October 6, 2005 Contents v 2005, QNX Software Systems Help menu 94 Toolbars 95 Control panels 98 Widget palette 99 Modes (create vs select) 101 Resources panel 102 Callbacks panel 104 Module Tree panel 106 Module Links panel 108 Browse Files panel 109 Search dialog 111 Customizing your PhAB environment 112 General preferences 113 Color preferences 115 Dragging preferences 115 Grid preferences 116 4 Working with Applications 119 Creating an application 121 Opening an application 123 Saving an application 125 From the IDE 125 From standalone PhAB 126 Closing an application 128 Specifying project properties 128 Startup Windows tab 129 Generate Options tab 133 Run options 137 Build and Debug options 138 Importing files 139 Importing PhAB modules from other applications 140 Importing XBM images 140 Importing graphics images 141 vi Contents October 6, 2005 2005, QNX Software Systems Exporting files 141 5 Working with Modules 143 Module types 145 Anatomy of a module 145 Selecting a module 147 How modules are saved 148 Changing module resources 148 Creating a new module 148 Deleting a module 149 Iconifying modules 149 Displaying modules at run time 150 Positioning a module 150 Finding lost modules and icons 152 Window modules 152 Resizing a window module 153 Dialog modules 153 Resizing a dialog module 154 Predefined dialogs 154 Menu modules 155 Opening the menu editor 156 Specifying instance names 158 Creating hotkeys and shortcuts 158 Resizing a menu module 159 Creating command items 159 Creating submenu items 161 Creating separator items 161 Creating toggle items 162 Creating function items 162 Moving menu items 163 Using a menu module 163 Picture modules 164 Displaying a picture 165 October 6, 2005 Contents vii 2005, QNX Software Systems Using pictures as widget databases 166 Resizing a picture module 166 6 Creating Widgets in PhAB 167 Types of widgets 169 Instance names 170 Default instance name 170 When to assign a unique name 171 Instance names and translations 171 Duplicate names 172 Creating a widget 172 Creating several widgets 173 Canceling create mode 173 Selecting widgets 174 A single widget 174 Multiple widgets 175 Widgets within a group 178 Hidden widgets 178 Aligning widgets 179 To another widget 179 To a parent container 180 Distributing widgets 181 Common User Access (CUA) and handling focus 181 Changing focus with the keyboard 181 Controlling focus 182 Focus callbacks 183 Focus-handling functions 183 Ordering widgets 184 Dragging widgets 186 Setting a widget’s x and y coordinates 187 Transferring widgets between containers 187 Resizing widgets and modules 188 Clipboard 189 viii Contents October 6, 2005 2005, QNX Software Systems Cutting and copying 189 Pasting 191 Duplicating widgets and containers 192 Deleting widgets or modules 193 Matching widget resources and callbacks 193 Importing graphic files 195 Changing a widget’s class 196 Templates 196 Creating templates 197 Adding a widget class 199 Editing templates 201 Deleting templates 201 7 Editing Resources and Callbacks in PhAB 203 Editing widget resources 205 Pixmap editor 206 Setting the pixmap’s size 207 How to draw and erase 208 Choosing colors 208 Drawing freehand 209 Drawing lines, rectangles, and circles 209 Filling an enclosed area 209 Selecting an area 210 Nudging an area 210 Using the Pixmap toolbar 211 Other pixmap controls 211 Color editor 212 Full color editor 212 Quick color editor 214 Flag/choice editor 214 Flag resources 215 Option list resources 216 October 6, 2005 Contents ix 2005, QNX Software Systems Font editor 216 List editor 218 Editing existing list items 220 Deleting list items 220 Number editor 220 Text editors 221 Code editor 224 Layout editors 225 Fill layout info editor 225 Row layout info editor 226 Grid layout info editor: 227 Row layout data editor 228 Grid layout data editor 229 Callbacks 230 Editing callbacks 232 Module callbacks 234 Prerealize setup function 236 Postrealize setup function 236 Setup functions are stored in stub files 237 Code callbacks 237 Callback functions are stored in stub files 238 Hotkey callbacks 238 Hotkeys — the basics 238 Specifying the hotkey label 239 Specifying the callback 240 Processing hotkeys 242 Disabling hotkeys 242 Event handlers — raw and filter callbacks 244 8 Geometry Management 247 Container widgets 249 Geometry negotiation 249 Resize policy 251 x Contents October 6, 2005 2005, QNX Software Systems Absolute positioning 255 Aligning widgets using groups 256 Joining widgets into a group 257 Accessing widgets in a group 257 Aligning widgets horizontally or vertically 257 Aligning widgets in rows and columns 258 Using the Group flags 259 Splitting apart a group 261 Constraint management using anchors 262 Anchor resources 265 Using layouts 267 PtFillLayout 271 PtRowLayout 274 PtGridLayout 279 Using hints 291 Enforcing position or size constraints without anchors or layouts 295 9 Generating, Compiling, and Running Code 297 Using the Build menu 299 Building your application 300 Generating application code 302 What PhAB generates 303 Version control 305 Function prototypes 306 How application files are organized 309 Multiplatform applications 310 Single-platform applications 311 Converting to Eclipse 312 Editing source 312 Choosing an editor or browser 314 Creating a source module 314 October 6, 2005 Contents xi 2005, QNX Software Systems Changing the file display 314 Compiling and linking 315 Specifying additional libraries 315 Running make 316 Customizing the build process 317 Running the application 318 Debugging 319 Managing targets 320 The Build menu 321 Including non-PhAB files in your application 322 Eclipse Project applications 322 Multiplatform applications 322 Single-platform applications 323 Adding libraries 323 Making a DLL out of a PhAB application 324 Compiling and linking 324 Initializing your DLL 324 Unloading your DLL 326 10 Working with Code 327 Variables and manifests 329 Widget variables and manifests 329 Using the global variable and widget manifest 330 Handling multiple instances of a window 331 Internal link manifests 333 Global header file 333 Function names and filenames
Load more

Recommended publications
  • The Early Years of Academic Computing: L a Memoir by Douglas S
    03 G A The Early Years of Academic Computing: L A Memoir by Douglas S. Gale E This is from a collection of reflections/memoirs concerning the early years of academic comput- ing, emphasizing the period when Cornell developed its own decentralized computing environ- ments and networking became a national strategic goal. ©2016 Henrietta Gale Initial Release: April 2016 (Increment 01) Second Release: April 2017 (Increments 02-04) Published by The Internet-First University Press Copy editor and proofreader: Dianne Ferriss The entire incremental book is openly available at http://hdl.handle.net/1813/36810 Books and Articles Collection – http://ecommons.library.cornell.edu/handle/1813/63 The Internet-First University Press – http://ecommons.library.cornell.edu/handle/1813/62 C. Memoir by Douglas S. Gale Preface and Introduction Bill Arms and Ken King have chronicled much of the early history of academic computing. Accordingly, I have tried to focus my contribution to The Early Years of Academic Computing on topics less covered by King and Arms. My contribution is organized into four chronological periods, roughly spanning the last 50 years of the 20th century, and each has an organizational theme: career transitions, the microcomputer revolution, the networking revolution, and the changing role of academic computing and networking. The theme of the first period -- career transitions -- will consider where the early practitioners of academic computing came from. Computer Science was first recognized as an academic discipline in 1962, and the early years of academic computing were led by people who had received their academic training in other disciplines. Many, if not most, came from the community of computer users and early adopters.
    [Show full text]
  • DLP Discovery 4100 Development Kit Software User's Guide (Rev. A)
    DLP® Discovery™ 4100 Development Platform User's Guide Literature Number: DLPU040A October 2016–Revised November 2018 Contents Revision History ........................................................................................................................... 6 Preface ........................................................................................................................................ 7 1 Overview............................................................................................................................. 9 1.1 The DLP Discovery 4100 Development Platform ...................................................................... 11 1.2 DLP Discovery 4100 Development Platform Photo.................................................................... 13 1.3 Key Components ........................................................................................................... 14 1.3.1 Xilinx Virtex 5 APPSFPGA ....................................................................................... 14 1.3.2 DLPC410 - Digital Controller for DLP Discovery 4100 Chipset ............................................. 14 1.3.3 DLPA200 - DMD Micromirror Driver ............................................................................ 14 1.3.4 DLPR410 - Configuration PROM for DLPC410 Controller................................................... 14 1.3.5 APPSFPGA Flash Configuration PROM ....................................................................... 15 1.3.6 DMD Connectors ................................................................................................
    [Show full text]
  • Desktop Icon Era
    Jason Hardware <p = class> </p> 20th Century Did you realize that computer weren’t born with a graphic user interface? It happened after over 30 years. 1962 Parts from four early computer. ORDVAC & BRLESC-I board On the first computers, with no operating system, every program needed the full hardware specification to run correctly and perform standard tasks, and its own drivers for peripheral devices like printers and punched paper card readers. Software <head> id = color, blue; </head> OSes Computer operating systems provide a set of functions needed and used by most application programs on a computer, and the links needed to control and synchronize computer hardware. Programming Language A programming language is a formal language, which comprises a set of instructions used to produce various kinds of output. Programming languages are used to create programs that implement specific algorithms. 80s Along with this revolutionary concept came other brilliant idea of using icons in computing. Sometimes, A picture says more than a thousand words. GUI- Graphic User Interface The history of the graphical user interface, understood as the use of graphic icons and a pointing device to control a computer, covers a five-decade span of incremental refinements, built on some constant core principles XEROX 8010 STAR 1981-1985 Invented by David Smith, Design by Norm Cox, it presented a square grid, simple looks, consistent style. APPLE-LISA 1983 Lisa was the first personal computer with a graphic user interface aimed at a wide audience of business customers. MACINTOSH 1 1984 Probably the most famous “art + Programming marriage” happened in 1982.
    [Show full text]
  • Introduction to Computers
    Introduction to Computers 2 BASIC MOUSE FUNCTIONS To use Windows, you will need to operate the mouse properly. POINT: Move the mouse until the pointer rests on what you want to open or use on the screen. The form of the mouse will change depending on what you are asking it to look at in Windows, so you need to be aware of what it looks like before you click. SINGLE-CLICK: The left mouse button is used to indicate choices from menus and indicate choices of options within a “dialog box” while you are working in an application program. Roll the mouse pointer on top of the choice and press the left mouse button once. RIGHT-CLICK: With a single quick press on the right mouse button, it will bring up a shortcut menu, which will contain specific options depending on where the right-click occurred. CLICK AND DRAG: This is used for a number of functions including choosing text to format, moving items around the screen, and choosing options from menu bars. Roll the mouse pointer over the item, click and hold down the left mouse button, and drag the mouse while still holding the button until you get to the desired position on the screen. Then release the mouse button. DOUBLE-CLICK: This is used to choose an application program. Roll the mouse pointer on top of the icon (picture on the desktop or within a window) of the application program you want to choose and press the left mouse button twice very rapidly. This should bring you to the window with the icons for that software package.
    [Show full text]
  • ICON: a Case Study in Office Automation and Microcomputing
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by International Institute for Applied Systems Analysis (IIASA) ICON: A Case Study in Office Automation and Microcomputing Lee, R.M. IIASA Working Paper WP-80-183 December 1980 Lee, R.M. (1980) ICON: A Case Study in Office Automation and Microcomputing. IIASA Working Paper. WP-80-183 Copyright © 1980 by the author(s). http://pure.iiasa.ac.at/1286/ Working Papers on work of the International Institute for Applied Systems Analysis receive only limited review. Views or opinions expressed herein do not necessarily represent those of the Institute, its National Member Organizations, or other organizations supporting the work. All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage. All copies must bear this notice and the full citation on the first page. For other purposes, to republish, to post on servers or to redistribute to lists, permission must be sought by contacting [email protected] NOT FOR QUOTATION WITHOUT PERMISSION OF THE AUTHOR ICON: A CASE STUDY IN OFFICE AUTOMATION AND MICROCOMPUTING Ronald M. Lee Working Papers are interim reports on work of the International Institute for Applied Systems Analysis and have received only limited review. Views or opinions expressed herein do not necessarily repre- sent those of the Institute or of its National Member Organizations. INTERNATIONAL INSTITUTE FOR APPLIED SYSTEMS ANALYSIS A-2361 Laxenburg, Austria I am especially grateful to Alan Krigman and David Ness, key characters in the case to follow, for their detailed comments and criticism of an earlier draft of this paper.
    [Show full text]
  • SOCIAL INFLUENCE and PREFERENCE of DIRECT-MANIPULATION and KEYBOARD-COMMAND COMPUTER INTERFACES Michael S
    PROCEEDINGS of the HUMAN FACTORSSOCIETY34th ANNUAl MEETING-1990 SOCIAL INFLUENCE AND PREFERENCE OF DIRECT-MANIPULATION AND KEYBOARD-COMMAND COMPUTER INTERFACES Michael S. Wogalter and Richard L. Frei Department of Psychology Rensselaer Polytechnic Institute Troy, New York 12180 ABSTRACf Direct-manipulation and command-based computer interfaces have each found their own following among microcomputer users. This study explores some of the differences between these two groups of computer users. Participants completed a questionnaire that requested their microcomputer usage and ownership, usage and preference of various command methods and pointing devices, the microcomputers most of their friends use, the microcomputer they would be most willing to purchase next, and their preference for several models of microcomputers. The results showed that participants preferred pointing devices (e.g., mouse) compared to other input methods (e.g., arrow keys) regardless of their prior usage. They tended to use an interface similar to that of their friends' and they reported greater willingness to purchase a computer with an interface similar to the one they most often use. In general, the results suggest that social influence and interface familiarity are important factors in determining which interface people choose to use. Being surrounded by others who use a similar computer interface eases the burden (in terms of effort, time, and expense) of obtaining relevant computer information. An implication of this work is that these variables may hinder approval and acceptance of improved computer interface designs offered by human factors specialists. INTRODUCfION Human factors specialists have dedicated considerable and are likely to develop a relationship with these persons. Thus, attention and research to various aspects of computer interface people will tend to affiliate with others, in part, because they have usability.
    [Show full text]
  • A Love/Hate Relaionship: the JVM/OS Dialecic
    A love/hate relaonship: The JVM/OS dialec,c Marcus Lagergren, Oracle A love/hate relaonship: диалектика JVM/OS Marcus Lagergren, Oracle A love/hate relaonship: The JVM/OS dialec,c Marcus Lagergren, Oracle A love/hate relaonship: The JVM/OS dialec,c (and the hardware…) Marcus Lagergren, Oracle A love/hate relaonship: The JVM/OS dialec,c (and the hardware…) Marcus Lagergren, Oracle Fredrik ÖhrströM, Spo,fy The Legal Slide "THE FOLLOWING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION. IT IS INTENDED FOR INFORMATION PURPOSES ONLY, AND MAY NOT BE INCORPORATED INTO ANY CONTRACT. IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION. THE DEVELOPMENT, RELEASE, AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLE'S PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE." Agenda • In the borderlands between hardware, OS and JVM, both good and bad things happen • CoMputer history • How do they affect each other? • Where is it all going? Who am I? @lagergren Who am I? Who am I? [email protected] [email protected] hps://avatar.java.net Who am I? Who am I? Who is Fredrik? Who is Fredrik? Who is Fredrik? Who is Fredrik? The Past The Past (Skipping very quickly over a treMendous amount of hardware) Texas InstruMents TI 99/4a • 1979-1984 • Contains an OS and a GPL interpreter • Device drivers (DSRs) could be wri[en in GPL Texas InstruMents TI 99/4a • 1979-1984 • Contains an OS and a GPL interpreter • Device drivers (DSRs) could be wri[en in GPL
    [Show full text]
  • How to Use This Manual User’S Manual
    LaCie SAFE Mobile Hard Drive with encryption How To Use This Manual User’s Manual How To Use This Manual In the toolbar: Previous Page / Next Page Go to Beginning / Go to End Printing: While optimized for onscreen viewing, the pages of this manual are formatted for printing on 8 1/2" x 11" and A4 sized paper, giving you the option to print the entire manual or just a specific page or section. To Exit: For Windows: From the Menu Bar at the top of your screen, select: File > Quit. For Mac: From the Menu Bar at the top of your screen, select Acrobat > Quit Acrobat. Icons Used In This Manual Italicized paragraphs feature an icon describing the type of information being given. Important Info: This icon refers to an important step that must be followed. Tech Note: This icon refers to tips to help maximize performance. Caution! This icon indicates a potential hazard, and gives tips on how to avoid them. LaCie SAFE Mobile Hard Drive with encryption Table of Contents User’s Manual Foreword 4 Health and Safety Precautions 6 1. Introduction 7 1.1. What Your LaCie SAFE Drive Can Do 7 2. Unpacking Your LaCie SAFE Drive 8 2.1. What’s Included With Your LaCie SAFE Drive 8 2.2. Minimum System Requirements 8 3. Before Installing Your SAFE Drive 9 3.1. How to Use the Fingerprint Sensor 9 3.2. The Configuration Tool 9 3.3. About Authorized Users and Rights 9 3.4. Rules for Registering Users 10 3.5. About Encryption Levels 10 4.
    [Show full text]
  • INTRODUCTION to WINDOWS WHAT IS WINDOWS Windows Is An
    INTRODUCTION TO WINDOWS WHAT IS WINDOWS Windows is an operating system developed and marketed by Microsoft.An operating system performs the following tasks: • Input & Output Management • Resource Management • Data Management • Process Management • User interface WINDOWS AS GUI Windows is a Graphical User Interface (GUI) Operating System. GUI means a platform where items are represented by an icon (picture) on the screen which are easier to remember. You need not to remember lengthy and complex syntax for performing different operations as you do it in DOS. GUI gives you a ready made on screen menu system that helps you finding suitable option for your task. Just select the job you wish to do and all the internal processing will be done by the OS itself without asking you about typical commands. GUI also gives you a multitasking, multithreading environment. It means that if you are working in an OS that supports GUI, you will be able to open more than one task at a time. Besides this, you will be able to transfer one kind of data to a different application e.g. A cartoon can be inserted in a Letter or vice versa. GUI gives you the description of the tasks currently running. In DOS it was not possible to see what processes are running but in Windows 95 it is possible to see all the applications that are currently active either in foreground or in background. GUI gives you most user friendly environment where you can get on-line help for each and every step you are performing. WINDOWS : SALIENT FEATURES • Graphical User Interface (GUI) – Items represented by pictures, which are easier to remember.
    [Show full text]
  • ECE QNX Real-Time Lab
    Department of Electrical & Computer Engineering – Concordia University ECE QNX Real-time Lab User Guide Dan Li 8/29/2020 User Guide of ECE Real-time QNX Lab Contents 1. About Real-time QNX Lab ..................................................................................................................... 2 Contacts .................................................................................................................................................... 2 Packages on Real-time development Machine ......................................................................................... 2 2. Real-time User Accounts ....................................................................................................................... 2 Real-time account ..................................................................................................................................... 2 Login Real-time Domain ............................................................................................................................ 2 Map ENCS Drives ....................................................................................................................................... 2 Drives ........................................................................................................................................................ 3 Change Real-time password ..................................................................................................................... 4 3. Real-time Environment ........................................................................................................................
    [Show full text]
  • Getting Into the Good Routines
    Getting into the good routines Lab or computer classroom regulations: • No food or drink is allowed. • Lower the noise when working on computer tasks. • Don't delete items or move items on the hard disk that don't belong to you. • Do not change the software settings without permission. • Work on a document from the hard disk and save the file to the hard disk. After the document is completed, copy it to the floppy disk. • Make frequent backup when working on a document. • When having problems, work them out individually first or consult with peers. Consult with the instructor as the last resorts. • Try to avoid saving directly onto a disk. Save files to the desktop first and copy files to the floppy disk when done. During your work, keep the floppy disk out of the drive. • Pay attention to the instruction or demonstration. Typing one's e-mail messages during the class demonstration is prohibited. Give your computer a fresh start-up. • If the machine is off, turn on the machine by tapping the reset key on the keyboard once. • If the machine is on, select Finder from the Application menu (Located at the top right-hand corner on the screen) and then select Restart from the Special menu. The fresh start-up will avoid most memory conflict problems. When using computers in a classroom or lab setting for instruction, it is desirable to minimize the conflict problems by getting a fresh start-up. Use virus protection program. To ensure the safety of computer uses in the lab or classroom, the virus protection is installed to check all the inserted disks.
    [Show full text]
  • Decoding Computers: from Mainframes to Microchips Decoding Computers from Mainframes to Microchips
    Decoding Computers: From Mainframes to Microchips Decoding Computers From Mainframes to Microchips TEACHER’S GUIDE 1 Decoding Computers: From Mainframes to Microchips BACKGROUND INFORMATION The Evolution of Computing CDC 6500 Back in the day, computers were enormous, whirring machines. They filled rooms with dedicated cabinets for storage, memory, processing and printing. Teams of technicians were tasked with maintaining them. These gargantuan computers were called mainframes. It’s hard to imagine today, but in the 1960s, computers were prohibitively expensive and reserved only for the most difficult operations, such as recording census data or running complicated scientific experiments. The CDC 6500 was one of the most powerful machines in the world when it was released in 1967. With a price tag of around $6 million, its clients were exclusively high-profile. The United States Air Force owned one, as did many flagship universities, such as Purdue University and Michigan State. Manufactured by Control Data Corp. of Minnesota, the CDC 6500 was, in many ways, a unique machine. It understood a bare minimum of instructions, but that made the computer devilishly fast by 1967 standards. Since speed generates heat, CDC developed a novel approach to remove excess heat from the 6500, a water cooling system. It is hard not to imagine the risk of mixing electronics and H2O, but the mainframe’s elegant design kept it safe. Much of the 6500’s architecture was designed by Seymour Cray, a highly skilled electrical engineer who fit the stereotypical mold of enigmatic genius. But even he relied on colleagues to transform a blueprint into a product ready to ship.
    [Show full text]