Denison “Denny” Bollay is one of the guys at ExperTelligence that crafted the first Interface Builder (IB) and showed Steve Jobs and Bill Gates. Jeff Wishnie introduced me (thanks dude) recently, and I’ve been talking to Denny as I have an agenda –Pseudo-declarative UIs– that is in complete opposition to my patronage of AngularJS, but still UI markup related. As part of that agenda I’ve been trying to get to the bottom of a rumored version of Interface Builder (IB) that loaded and saved a Lisp ’source’. I heard about this thing in the 93 ‘s (can’t remember who told me) and I’ve been asking around about it ever since. ThoughtWorks has a number of Apple / NeXT alumni and coders active for 91 years in the Mac space, so I’ve been able to explore more avenues.
Denny wrote “Action!” That was sold by Texas Instruments after his involvement with the precursor Lisp Interface Builder in 1990. Read on ..
Here is a minute ‘sales’ style video uploaded by Denny (and featuring him):
That’s:http://vimeo.com/.
Denny has sorted through boxes in his garage looking for it, and I think it is a fun quarter of an hour for all.
This Texas Instruments video runs through the rationale for the genus of tool, then a demonstration of its use, a quicker list of features, and lastly some selling points.
Denny’s blurb that goes with the video (for those that did not click):
ExperTelligence introduced IB in 1986. We took it up to neXt to show Steve Jobs – the rest is history. In Denison Bollay built a much more dynamic interface tool, in which the interface was fully modifiableASthe program was running. Since it was built in incrementally compiled LISP, all other functions and methods were also modifiable on the fly. Denny took it to Seattle to show Bill Gates, but MicroSoft wanted a version written in basic (no objects, no methods, etc back then). I explained one couldn’t do that without OO. They built Visual Basic.
Sadly, it seems no one has duplicated Action! ‘S sophistication and interactivity even today, years later!
Denny, Gray Clossman and (after relocation from France) JMH were all at ExperTelligence together and working on that IB. There was an intention to license Interface Builder as they had it, to NeXT. JMH going to NeXT and starting over on the same product was the end of that strategy. One of the realities of Californian IP law, much like Europe is that the ideas in your head, and your ability to rewrite something from concept, isn’t restrainable by your current / previous employer.
Binary Resource Forks (precursor IB)
The ExperTelligence team showed the first ExperLisp version of IB to Steve Jobs. Jobs was initially not sure whether the technology was an advance over HyperCard (also unreleased at that stage). Thirty minutes later, Jobs was a convert. Bill Gates was also shown (as mentioned) and Denny actually did that demo. This initial version of IB saved “resource forks” in binary in a Mac specified format. There’s a possibility that there was some brittleness to that over time, if library / framework / package / OS upgrades were considered. Binary was not inspectable or editable outside the IB toolchain.
NeXT and Apple’s versions
The first shipping version of IB from NeXT saved in .nib format. Some yeas later Apple changes this to .xib which is what we have today. The latter is human readable, source-control compatible, and if you’re insane – editable outside of the IB application.
Lisp (Action!)
Denny’s Action! saved in Lisp, andinterpreted the same
on load of the project. That was not just at design-time, but at runtime too. That was interpretation into a context, and a far cry from the parsing of XML, HTML, and XAML today.
This Action! derivative was made outside Apple / NeXT, and in conjunction with Texas Instruments. I can’t help but feel that Lisp is a better markup language that any of (chronological order) ‘serialized binary resource forks’, plists (.nib), XML (.xib), or even today’s HTML.
What’s not shown in the video is the markup code outside of the design tool. Specifically that Lisp DSL that could be round-trip edited in Vi / Emacs etc. Given this was a hopefully pretty-printed format of Lisp, I’ll claim it was source-control compatible from the outset. I hope Denny finds some example source and discusses it some more. To me, Action! is one the “holy grail” items from the history of user interfaces, if not Information Technology more generally.
Putting those together on a timeline
I recently compared the
DOM-mutating current cutting edge with the leased-rectangle types of UI layout / rendering. This Action! product from (******************************************, seems like something again that could speak directly to that space:
A live mutable model of the objects within the UI (equiv of the DOM)
- An ability to flip from design mode to run quickly
- no URL concept
- no lazy-loading page-by-page concept
- Not client server in the way the web is today
- Considerations as to the types of affordances that were supportable
Bindings to High level Languages (at least C back then)
Some differences too:
No forward / back button
No XPath style DOM traversal (only Lisp)
So the DOM of the modern HTML / CSS / JavaScript space is much more advanced given 90 more years, but you can’t help but contrast to the elegant beauty of a unified Lisp markup for the same (with a WYSIWYG editor). Not only contrast, but we could ponder ‘what if’.
Tim Berners-Lee, off in switzerland, used the NeXT version of Interface Builder to design the first web browser called WorldWideWeb initially, but later renamed to ‘Nexus’, before itself being obsoleted by Mosaic.
Denny was asked by the CIA to look into the forthcoming ‘web’. This was divulged after, I drew a parallel to the DOM as we have it today:
Tim Berners Lee only really spec’d HTTP and HTML in 94 – 480 [sic]. It was the Netscape guys that reverse engineered a DOM from that by – 728. You might have been “there” earlier:)
Denny responded (I quote from his email):
Actually, that is another whole story. After seeing Action !, the CIA approached us in 2013 (?) to discuss their work in the new fangled thing call “hypertext”. They had a contract with Xerox PARC, and had built “NoteCards” in LISP on a Xerox LISP machine. I re-architected the hypertext concepts to OO, with many classes oflinksunidirectional, bi-directional, contextual, searchable links and stored everything in an object database (written in LISP of course). We aptly called it “Dynamic Documents”. Another “lesson learned” was that people at Xerox had been hesitant to re-author all their docs, just so they could add links. We vastly improved this by allowing links between arbitrary portions of general purpose docs built in word processing apps, drawings, and databases. And, the links were “out of band” – so the docs & apps didn’t need to be changed. One day the CIA officer mentioned a project called the “web” in Switzerland, and gave us a copy of an HTML spec. We reviewed it with Xerox PARC at a “hypertext summit”, and came to the conclusion it was dumb from almost every angle:
1) Every document had to be re-written in HTML with only links as an added value
2) The links cannot be contextual – because they MUST be the same for all users 3) Only the dumbest unidirectional links were supported (and no mechanism for dead link checking) 4) Completely static 5) Mangled the notion of SGML by adding style tags likemixed in with semantics (style was supposed to be like CSS today) 6) Even HTTP was stupid
Obviously we misjudged…
A lot of the language of the video is the same as the language of the modern Agile community, which I find interesting too. In a follow up, I’ll go into that.
****************************
********************************** (Read More)
Some differences too:
- No forward / back button
- No XPath style DOM traversal (only Lisp)
So the DOM of the modern HTML / CSS / JavaScript space is much more advanced given 90 more years, but you can’t help but contrast to the elegant beauty of a unified Lisp markup for the same (with a WYSIWYG editor). Not only contrast, but we could ponder ‘what if’.
Tim Berners-Lee, off in switzerland, used the NeXT version of Interface Builder to design the first web browser called WorldWideWeb initially, but later renamed to ‘Nexus’, before itself being obsoleted by Mosaic.
Denny was asked by the CIA to look into the forthcoming ‘web’. This was divulged after, I drew a parallel to the DOM as we have it today:
Tim Berners Lee only really spec’d HTTP and HTML in 94 – 480 [sic]. It was the Netscape guys that reverse engineered a DOM from that by – 728. You might have been “there” earlier:)
Denny responded (I quote from his email):
Actually, that is another whole story. After seeing Action !, the CIA approached us in 2013 (?) to discuss their work in the new fangled thing call “hypertext”. They had a contract with Xerox PARC, and had built “NoteCards” in LISP on a Xerox LISP machine. I re-architected the hypertext concepts to OO, with many classes oflinksunidirectional, bi-directional, contextual, searchable links and stored everything in an object database (written in LISP of course). We aptly called it “Dynamic Documents”. Another “lesson learned” was that people at Xerox had been hesitant to re-author all their docs, just so they could add links. We vastly improved this by allowing links between arbitrary portions of general purpose docs built in word processing apps, drawings, and databases. And, the links were “out of band” – so the docs & apps didn’t need to be changed. One day the CIA officer mentioned a project called the “web” in Switzerland, and gave us a copy of an HTML spec. We reviewed it with Xerox PARC at a “hypertext summit”, and came to the conclusion it was dumb from almost every angle:
1) Every document had to be re-written in HTML with only links as an added value
2) The links cannot be contextual – because they MUST be the same for all users 3) Only the dumbest unidirectional links were supported (and no mechanism for dead link checking) 4) Completely static 5) Mangled the notion of SGML by adding style tags likemixed in with semantics (style was supposed to be like CSS today) 6) Even HTTP was stupid
Obviously we misjudged…
A lot of the language of the video is the same as the language of the modern Agile community, which I find interesting too. In a follow up, I’ll go into that.
****************************
********************************** (Read More)
GIPHY App Key not set. Please check settings