redo overview of project, merge news and status

content/en/history/_index.md

@@ -14,6 +14,66 @@ Interlisp evolved from an interactive terminal style programming tool to Interli
 
 Development of the system moved from Xerox PARC to a Xerox AI Systems division, to a spin-out company called Envos, to a smaller company called Venue. The system was called Interlisp, Interlisp-D, and various named releases (Koto, Lyric, Medley) until the name "Medley" was used for the whole thing.
 
+### Another short history
+
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+The 1970s and 80s saw major advances in computing and Human-Computer interaction.  At Xerox PARC there were three IDEs developed with different approaches: Smalltalk, with an object-oriented system; Interlisp, for researchers in AI and exploratory development; Cedar/Mesa, with a strongly typed language. They each had a different model for source code management, development and versioning. In common they shared an infrastructure and vision of computing and distributed systems, with support for Ethernet networking, printing, file servers and network protocols. Each environment had its own Virtual Machine instruction set tuned for the language "all the way down", in a single address space, in a way that opened the systems to customization.
+
+There were several different [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf): Dorado, Dolphin, Dandelion, Daybreak, and others. Each environment had its own microcode to implement its instruction set; once loaded, each would take over the machine -- there was no separate OS. Each had large-screen black and white CRTs for a graphical user interface, mouse and cursor pointer, high quality fonts.
+
+Xerox marketed the Interlisp-D enviornment primarily to the AI community world wide, starting in 1980, from XEOS to Xerox Artificial Intelligence Systems, then a spin-out company called Envos, and then further development and porting to other systems by a company called Venue, until development tapered off. Along the way, the name changed from Interlisp-D to Medley.
+
+We started with sources from Venue for what was intended to be Medley 3.5.
+
+
 ### Detailed History
 
 A more extensive history of Interlisp can be found in the [Interlisp Timeline](timeline). The [Interlisp Bibliography](bibliography) has a wealth of historical material.

content/en/project/_index.md

@@ -1,5 +1,5 @@
 ---
-title: Project
+title: The Medley Interlisp Project: Reviving a Groundbreaking System
 weight: 2
 type: docs
 aliases:
@@ -8,55 +8,37 @@ aliases:
  - /medley/about/
  - /medley/other/
 ---
-## What is the Medley Interlisp Project?
-
-The Medley Interlisp Project was created to revive Medley Interlisp.
-
-Because Interlisp has been around a long time, with multiple iterations, you might find the multitude of names for the Interlisp language and related companies confusing. To assist, we have created a [glossary of terms](glossary) used on this website.
-
-## What are the origins of Interlisp? Why do we care?
-
-The 1970s and 80s saw major advances in computing and Human-Computer interaction.  Interlisp was one of the many experimental systems developed during these heady times.  It represents an early example of a system with a GUI (Graphical User Interface), and IDE (Integrated Development Environment).
-
-Within the Xerox PARC environment, it was an early example of a network enabled machine supporting email, file sharing, printing and more.  In essence it was a forerunner of today's computing systems.
-
-Medley Interlisp represents the last Xerox Interlisp release.  Medley continued Xerox PARC's experimentation with developing systems for [D-machines](http://www.bitsavers.org/pdf/xerox/parc/Exploring_the_Ethernet_with_Mouse_and_Keyboard_May81.pdf). A family of computers (Dorado, Dolphin, Dandelion, Daybreak) resulted. The project was later spun out to a company called Envos, which then turned into Venue.
 
 ## What are we trying to accomplish?
 
-Our aim is to allow *Medley Interlisp* to "live again": usable on modern systems, sufficient to allow someone to develop some code and experience what it was like to use this groundbreaking system. You could think of this as a kind of "*vintage software*" project, to try to capture the sense of fluidity in the development cycle. 
+Our aim is to allow Medley to "live again": to be useable enough on modern systema that someone could develop some code and experience what it was like to use this groundbreaking system. You could think of this as a kind of "*vintage software*" project, to try to capture the sense of fluidity in the development cycle. 
 
-We hope to provide a platform for demonstration of early experiments of hypertext (Notecards), Desktop management (Rooms), Object-oriented programming (LOOPS), as well as Interlisp itself.
+We also hope to provide a platform for revival of systems developed using Interlisp., including 1980's work in hypertext (Notecards), desktop management (Rooms), and object-oriented programming (LOOPS).
 
 ## What are our challenges?
 
-Since we aim to revive Medley Interlisp to support not just a demo or test drive, but actual use as a development and learning tool, we need to overcome a number of compatibility problems with current systems and interfaces.
-
-We also want to restore and present earlier versions of Interlisp, for the student of computer history. For more information go to [Interlisp and Software Preservation Network](https://www.softwarepreservationnetwork.org/Interlisp/).
+Being compatible with modern systems requires compensating for changes input and output channels.  Mouse, cursor, scroll wheels need to function in the expected way. Support for the plethora of different keyboard layouts available today requires rearchitecting some of the lowest levels of stream handling. The replacement of the "XCCS" (Xerox Character Code Standard) with Unicode isn't complete. Today's screens are bigger. CPUs are multi-threading, Big-endian 64-bit character codes. Three-button mouse vs. one button. Subtle bugs because of change of address space.
 
-## What have we done so far?
+We also want to restore and present earlier versions of Interlisp, for the student of computer history. 
 
-We have done a lot of cleanup and adaptation to make Interlisp Medley usable again in the modern world. Among other developments, you can now run Medley Interlisp on many OS and hardware configurations, or in the cloud, using a web browser.
+We have done a lot of cleanup and adaptation, to make Medley usable again in the modern world. Among other developments, you can now run Medley Interlisp on many OS and hardware configurations, or in the cloud, using a web browser. 
 
-We've also been working on integration of the Interlisp style development with git and GitHub, Docker and other modern components.
-
-<div class="mx-auto">
- <a class="btn btn-lg btn-danger mr-3 mb-4" href="">
-  How do I access and use Medley?<i class="fas fa-arrow-alt-circle-right ml-2"></i>
- </a>
-</div>
+We have also developed tools for managing the GitHub workflow, to integrate the Interlisp style development with git and GitHub, Docker and other modern components.
 
 ## Who is involved?
 
-We are some of the original developers and users of the system 30 years ago, joined by newcomers interested in software history and preservation, along with members of the Lisp community. We work with [organizational partners](partners). And with you!
+We are [some of the original developers and users of Interlisp](/project/credits) 30 years ago, joined by newcomers interested in software history and preservation, along with members of the Lisp community. We work with [organizational partners](partners). And with you!
 
 <div class="mx-auto">
  <a class="btn btn-lg btn-danger mr-3 mb-4" href="">
   How do I get involved?<i class="fas fa-arrow-alt-circle-right ml-2"></i>
- </a>
+a </a>
 </div>
 
-## Check out this presentation for more information
+## Why?
+
+People have [different stories](stories) for why they are interested.
+
 
 A presentation from the 2020 Remote Chaos Experience conference highlights some of the interesting aspects of Interlisp.