Skip to main content

And it is Still Alive and Kicking

About a year ago, it was reported to me that all the kiosks that we help develop for the Take Flight exhibit at the Museum of Science and Industry (MSI) in 1995 were removed and replaced with newer kiosks. I was very sadden to hear this.  We developed three different types of kiosks, two outside the 727 and one inside the plane and installed into the back of each seat in the plane.


My colleague, Robert Burton developed a compiler using C and assembly that was originally used for developing our Lotus cc:Mail training courses for version 1.0 all the way up to version 2.  The compiler and development kit allowed us to create very dynamic graphics for the DOS platform.  At least it was very dynamic in 1995.  Each of the 20 so kiosks ran on a Gateway 486 with 64M of memory.  Wow!!  Startup and shutdown of these kiosks was done by turning the power on and off.  I wonder what would happen to Windows if that happened.

Since we are members of MSI, I decide to make a visit to MSI yesterday to see what they replaced our stuff with. The newer kiosks were bigger and had more graphics, but I still liked better the graphics found in our application. They are more vibrant and fun.

However, we were pleasantly surprised to discover that there was still one kiosk that was not replaced. So our work that we did 20 years ago lives on!!! Being turned on and off every single day, entertaining visitors (millions of them) and will be continuing to do so for many, many years or until the Gateway 486 craps out.  Just like Lotus Notes, our app was built to last and yes Gateway built good computers those days.

Of course we bumped into fellow ICS community member, Andrew Barickman and his family at the MSI.


 
 
 

 

Comments

Unknown said…
Sweetness. Nice to know your work can hold up well over that length of time.
It was the most fun project we ever did over the past 23 yrs since we started on our own.

Popular posts from this blog

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era).  But in the last decade, there a

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select

The iPhora Journey - Part 3 - Creating an Integrated UI Framework

The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework There are many ways to create the user interface (UI) for a web application. The HTML page could be created on the server and then pushed out. It could be static with the data generated on the page by the server with JavaScript, providing a more dynamic experience, or the server could generate new HTML content to update portions of the web page. XPages or PHP are good examples of this. Another method is to have the web page partially generated by the server and have JavaScript build the rest of the HTML by pulling data from the server via an API. This is the approach used in the Single Page Application (SPA) model. In all cases, it is still dependent on the web server technology being using.  As mentioned previously in this blog, XPages is dependent on complete integration between form and document, which e