from vidicue to vanguard, products from datatron (through a pointer from chris). don't think i have heard anything about b220 before or datatron or...

paul pangaro once "programmed computer-graphics on vector displays and one of the earliest color raster-scan machines" nowadays he is senior director at sun microsystems" (The Cybernetics of HCI), developer web services.

some of his papers from the 80s: programming and animating on the same screen at the same time, 1980, creative computing.

Moreover, I want to make pictures with the computer, so why couldn't a system be made where the programs themselves were pictures (or at least two-dimensional things)? Might we not blur the distinction between programming and animating? ...

The fundamental idea of EOM was that all programs are two-dimensional scripts, whose graphical nodes themselves stood for executable programs. Two aspects were both controlled from the screen: the data paths of the program, and the graphics of the intended animation.

henry lieberman's tinker system (watch what i do) carries the idea further.

another project from the early 80s he called: beyond menus: the rats-a-stratz or the bahdeens

First, the interconnections between topics (the "do-ables" and "know-ables" of the domain) are not hierarchical; they are a heterarchy, that is, there are no inherent "higher" or "lower" entities. Hierarchies emerge out of the mesh only during action and interrogation as a result of transactions with a user.

Second, connections or relations between topics cannot not be arbitrary and ubiquitous; they must follow the rule of entailment.

instead of clicking help, "the User can ask the system "what is this function" in the same vocabulary as "do this function", the vocabulary here contained in the underlying knowledge representation."

On October 11, 1963, my suggestion was to pass on a request of our customers to relax the ALGOL 60 rule of compulsory declaration of variable names and adopt some reasonable default convention such as that of FORTRAN. I was astonished by the polite but firm rejection of this seemingly innocent suggestion: It was pointed out that the redundancy of ALGOL 60 was the best protection against programming and coding errors which could be extremely expensive to detect in a running program and even more expensive not to. The story of the Mariner space rocket to Venus, lost because of the lack of compulsory declarations in FORTRAN, was not to be published until later ... (car hoare acm turing award lecture, october 27, 1980)

in his paper the emperor's old clothes hoare talks about failures in software development in the first 20 years, his work at the elliott 503 mark II software system and why it had to be abandoned

...Over lunch our customers were kind to try to comfort me. They had realized long ago that software to the original specification could never have been delivered, and even if it had been, they would not have known how to use its sophisticated features, and anyway many such large projects get cancelled before delivery. In retrospect, I believe our customers were fortunate that hardware limitations had protected them from the arbitrary excesses of our software designs. In the present day, users of microprocessors benefit from a similar protection--but not for much longer. At that time I was reading the early documents describing the concepts and features of the newly announced OS 360, and of a new time-sharing project called Multics. These were far more comprehensive, elaborate, and sophisticated than anything I had imagined, even in the first version of the 503 Mark II software ...