The TX-2 computer, an experimental machine at the M.I.T. Lincoln Laboratory, has been in operation for almost 10 years as an on-line, graphically oriented facility. In 1964, a time-sharing system for the TX-2 was started. This system, APEX, was to service a small number of consoles with graphic display capability. To achieve hardware economy, displays were to be refreshed from main core memory through a time-shared vector generator providing analog signals distributed to the individual console scopes. The displays were to be refreshed directly from a structured display file as experience with the Sketchpad developments of the early 1960's had indicated was highly desirable for interactive graphic applications. Although the APEX graphic system has evolved through several generations of display hardware and corresponding software changes, the initial design principles of displays refreshed from structured information in main core by a time-shared generator have remained. This paper is an attempt to collect and evaluate some lessons learned from our experience in developing and using this system.
{"title":"Graphics in time-sharing: a summary of the TX-2 experience","authors":"W. R. Sutherland, J. Forgie, Marie V. Morello","doi":"10.1145/1476793.1476900","DOIUrl":"https://doi.org/10.1145/1476793.1476900","url":null,"abstract":"The TX-2 computer, an experimental machine at the M.I.T. Lincoln Laboratory, has been in operation for almost 10 years as an on-line, graphically oriented facility. In 1964, a time-sharing system for the TX-2 was started. This system, APEX, was to service a small number of consoles with graphic display capability. To achieve hardware economy, displays were to be refreshed from main core memory through a time-shared vector generator providing analog signals distributed to the individual console scopes. The displays were to be refreshed directly from a structured display file as experience with the Sketchpad developments of the early 1960's had indicated was highly desirable for interactive graphic applications. Although the APEX graphic system has evolved through several generations of display hardware and corresponding software changes, the initial design principles of displays refreshed from structured information in main core by a time-shared generator have remained. This paper is an attempt to collect and evaluate some lessons learned from our experience in developing and using this system.","PeriodicalId":326625,"journal":{"name":"AFIPS '69 (Spring)","volume":"353 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1969-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115923023","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The introduction of computer techniques into the hospital environment offers an exceptional opportunity to reassess traditions and procedures developed over the years of a non-automated era. However, there is an apparent danger that computer applications evolving in many hospitals tend to perpetuate the stereo-typed roles of departments and personnel confined within traditional organizational boundaries. Their primary emphasis on conventional business or other specialized areas serves to sustain long standing and often outmoded rituals and procedures, imbuing them with the aura of modern automation. Such stereotype can be avoided by centering design of the computer system on the patient and his care as the crucial basic unit, thereby optimally meeting the needs of both patient and staff.
{"title":"Hospital automation: something more than a computer","authors":"W. Bennett, C. Stroebel, B. Glueck","doi":"10.1145/1476793.1476911","DOIUrl":"https://doi.org/10.1145/1476793.1476911","url":null,"abstract":"The introduction of computer techniques into the hospital environment offers an exceptional opportunity to reassess traditions and procedures developed over the years of a non-automated era. However, there is an apparent danger that computer applications evolving in many hospitals tend to perpetuate the stereo-typed roles of departments and personnel confined within traditional organizational boundaries. Their primary emphasis on conventional business or other specialized areas serves to sustain long standing and often outmoded rituals and procedures, imbuing them with the aura of modern automation. Such stereotype can be avoided by centering design of the computer system on the patient and his care as the crucial basic unit, thereby optimally meeting the needs of both patient and staff.","PeriodicalId":326625,"journal":{"name":"AFIPS '69 (Spring)","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1969-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115470173","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The language BCPL (Basic CPL) was originally developed as a compiler writing tool and as its name suggests it is closely related to CPL (Combined Programming Language) which was jointly developed at Cambridge and London Universities. BCPL adopted much of the syntactic richness of CPL and strived for the same high standard of linguistic elegance; however, in order to achieve the efficiency necessary for system programming its scale and complexity is far less than that of CPL. The most significant simplification is that BCPL has only one data type---the binary bit pattern---and this feature alone gives BCPL a characteristic flavour which is very different of that of CPL and most other current programming languages.
{"title":"BCPL: a tool for compiler writing and system programming","authors":"M. Richards","doi":"10.1145/1476793.1476880","DOIUrl":"https://doi.org/10.1145/1476793.1476880","url":null,"abstract":"The language BCPL (Basic CPL) was originally developed as a compiler writing tool and as its name suggests it is closely related to CPL (Combined Programming Language) which was jointly developed at Cambridge and London Universities. BCPL adopted much of the syntactic richness of CPL and strived for the same high standard of linguistic elegance; however, in order to achieve the efficiency necessary for system programming its scale and complexity is far less than that of CPL. The most significant simplification is that BCPL has only one data type---the binary bit pattern---and this feature alone gives BCPL a characteristic flavour which is very different of that of CPL and most other current programming languages.","PeriodicalId":326625,"journal":{"name":"AFIPS '69 (Spring)","volume":"73 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1969-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125912075","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The federal government is destined to play a key role in the future development of on-line business systems and the structure of the new industry growing up around them. Six points of contact already are evident: 1. Anti-trust action (real and implied) as in the current cases against IBM and AT&T.