<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'>Hello everyone,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'>Following on my earlier comments, the idea that computers have “users” with user interfaces or interactive dialogs only really goes mainstream in business data processing circles in the 1970s. A nice snapshot of the emerging conventional wisdom is given in J. Martin, <i>Design of Man-Computer Dialogues</i>. New York: Prentice-Hall, 1973. Martin was a prolific author of books on business computing technology.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'>On menus vs. command lines, a command line system would typically involve typing a command word followed, in many cases, by some parameters. There would very often be a “help” command that would list valid commands.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'>A menu is, in its most primitive form, basically the same thing except that the help is displayed by default and the commands are short (usually one or two characters) so that the system will prompt for any further parameters or options needed. I remember a lot of terminal oriented menu systems involved two letter command codes.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'>Laine is probably too young to remember browsing the web in a text terminal window using the Lynx browser. That turned the web into a menu system, not unlike Gopher. It is still possible to get around Windows with keyboard shortcuts.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif"'>Tom</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> members-bounces@sigcis.org [mailto:members-bounces@sigcis.org] <b>On Behalf Of </b>Laine Nooney<br><b>Sent:</b> Monday, March 17, 2014 11:45 AM<br><b>To:</b> sigcis<br><b>Subject:</b> Re: [SIGCIS-Members] Resources re: history of menus in computing?<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Very helpful, Tom and William, thank you. I'm especially interested in Tom's suggestion re: the general use of a menu as an efficient alternative to a command line--are there any specific resources anyone knows of that could offer a citation on that observation?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>for those interested, the 1996 Federal Standard 1037C (the Glossary of Telecommunication Terms) defines a menu as “a displayed list of options from which a user selects actions to be performed." (ATIS adopted this definition without change). The specificity of "list" is one of the ways games are confounding in this context, as games often replace what could be expressed in a list with lush manipulable simulations.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>best,<o:p></o:p></p></div></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><p class=MsoNormal>Laine Nooney<o:p></o:p></p><div><p class=MsoNormal>Department of Cultural Analysis and Theory<o:p></o:p></p></div><div><div><p class=MsoNormal>Stony Brook University<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Editorial Assistant to the Journal of Visual Culture<o:p></o:p></p></div><div><p class=MsoNormal><a href="http://vcu.sagepub.com/" target="_blank">vcu.sagepub.com</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><a href="http://www.lainenooney.com" target="_blank">www.lainenooney.com</a><o:p></o:p></p></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Sun, Mar 16, 2014 at 5:11 PM, Thomas Haigh <<a href="mailto:thaigh@computer.org" target="_blank">thaigh@computer.org</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Hello everyone,<br><br>Pop up and pull down menus had a specific genesis in the PARC/Xerox/Apple<br>trajectory of GUI work and have been an object of historical curiosity. IIRC<br>PARC had popup menus and Apple added pull down menus.<br><br>In contrast, menus in general are a fairly fundamental concept in<br>interactive computing and I suspect would have appeared very early in the<br>development of commands and applications for timesharing systems. The<br>alternative to a menu was a command line system, but these required commands<br>to be typed with no mistakes in exactly the right syntax. A menu guided<br>users through valid options, which reduced the error rate and effectively<br>let "help" information be integrated with the entry of commands. Menus could<br>be used with teletypes as well as VDUs.<br><br>So my personal guess on the origin of menus would be in a very early<br>interactive system such as MIT's CTSS, RAND's JOSS, or something from SDC.<br>If you are interested in a specific "first" you would also need to develop a<br>clear definition of "menu" to distinguish it from a command prompt.<br><br>Best wishes,<br><br>Tom<o:p></o:p></p><div><div><p class=MsoNormal><br>-----Original Message-----<br>From: <a href="mailto:members-bounces@sigcis.org">members-bounces@sigcis.org</a> [mailto:<a href="mailto:members-bounces@sigcis.org">members-bounces@sigcis.org</a>] On<br>Behalf Of William McMillan<br>Sent: Sunday, March 16, 2014 3:42 PM<br>To: Laine Nooney; sigcis<br>Subject: Re: [SIGCIS-Members] Resources re: history of menus in computing?<br><br>Hello, Laine.<br><br>Menus were central to the UI of UCSD Pascal, Ken Bowles's project in the<br>1970s. Bowles talked with Steve Jobs int he early days (and later, Gates)<br>and some of the students who worked on UCSD Pascal went to Apple and<br>influenced the development of the Lisa etc. Apple Pascal (an OS as well as<br>a programming environment) for the Apple II was UCSD Pascal.<br><br>There are a lot of good web resources on UCSD Pascal, and I had a magazine<br>article on its history in IEEE Spectrum.<br><br>This was certainly an early and influential deployment of a menu-driven UI.<br>Games were developed in UCSD Pascal, but I don't know if they were notable<br>at all.<br><br>- Bill<br>- Hide quoted text -<br><br>On 3/15/14, Laine Nooney <<a href="mailto:laine.nooney@gmail.com">laine.nooney@gmail.com</a>> wrote:<br>> Hi all,<br>><br>> I'm currently pulling together a short essay for a game history<br>> lexicon on the emergence of the menu in games. This topic is running<br>> me a bit in circles--menus seem to be one of those components that are<br>> so "obvious," or taken for granted in the game dev realm, that they<br>> aren't deeply, explicitly talked about.<br>><br>> I'm wondering what the respective literature around "menus" might be<br>> in the history of computing. Are there obvious touchstones or<br>> definitive transitions to be aware of (especially beyond the visible<br>> PARC/Apple/Windows GUI histories)?<br>><br>> And to be clear, I'm trying to keep this distinct from UI issues<br>> (insofar as that's possible!)<br>><br>> Any leads, food for thought, or general chatter would be much appreciated!<br>><br>> Best,<br>><br>> Laine Nooney<br>> Department of Cultural Analysis and Theory Stony Brook University<br>><br>> Editorial Assistant to the Journal of Visual Culture <a href="http://vcu.sagepub.com" target="_blank">vcu.sagepub.com</a><br>><br>> <a href="http://www.lainenooney.com" target="_blank">www.lainenooney.com</a><br>><o:p></o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>This email is relayed from <a href="mailto:members@sigcis.org">members@sigcis.org</a>, the email discussion list of<br>SHOT SIGCIS. The list archives are at <a href="http://sigcis.org/pipermail/members/" target="_blank">http://sigcis.org/pipermail/members/</a><br>and you can change your subscription options at<br><a href="http://sigcis.org/mailman/listinfo/members" target="_blank">http://sigcis.org/mailman/listinfo/members</a><br><br>_______________________________________________<br>This email is relayed from <a href="mailto:members@sigcis.org">members@sigcis.org</a>, the email discussion list of SHOT SIGCIS. The list archives are at <a href="http://sigcis.org/pipermail/members/" target="_blank">http://sigcis.org/pipermail/members/</a> and you can change your subscription options at <a href="http://sigcis.org/mailman/listinfo/members" target="_blank">http://sigcis.org/mailman/listinfo/members</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>