Skip to main content

The End of an Era

As some know we are celebrating our 23th anniversary as entrepreneurs this year.  It has been full of highs and lows.  One of most fun achievement that we had was in the first couple of years as ReCor.  Now it is most standard corporate training with ReCor and social collaboration and BPM technology with Phora Group and our iPhora solutions.

As one starts out, you try to determine your bearings.  Usually reality hits and you throw out all the business plans and marketing stuff.  So early on we did some stuff for free hoping that something might come out of it in the future.  And that is what happened.  About a year later, the person we helped out came back to us to develop a kiosk for an exhibit.  We did not know much about kiosks at that time, but we knew technology.  You have to remember that we are talking about the early 90s and there is no Internet, Windows, Macs, fancy computers.  The latest and greatest was Intel 486 processor and VGA graphics card with a whole 64 Mbytes of memory and the beginning of touch screen technology which always turned yellow after awhile.

The requirements was that it had to be a real-time interactive touch screen application that would run everyday over and over again.  Windows 3.0 came out and it sucked.  So we had to use DOS which did not have much graphics capabilities

So my two colleagues, Rob Burton and Dan Eitel tacked with me on the development of these kiosks. With no real graphics compilers out there Rob Burton was able to find a machine code based library called Fast Graphics and we built our own language compiler that ran the kiosk in real-time.

We struggle for months to get it working, but we did it!!!

These kiosks were for the Take Flight Exhibit in the Museum of Science and Industry.  Millions and millions of attendees have seen and played with these kiosks and is one of the biggest exhibits in the Museum. If you ever attended the Museum of Science and Industry, you can not miss it.  We were able to attend the opening ceremony with all the big wigs.

These kiosks have been run everyday since. During a twitter conversation with Don McNally who was attending the Museum of Science and Industry, I was told by my colleague that the museum had recently replaced our kiosks with newer one near the end of last year.  I am very saddened and proud.  We never expect the kiosks to last 19 years of continuous use.  The kiosks were turned on by powering it up and turned off by a hard power shut down.  Gateway definitely built some nice hardware those days.

So to this day, these kiosk applications are the longest running applications that we ever built and we are proud of what we done and achieved. It was a fun project that resulted in where we are as entrepreneurs.

Comments

Wonderful story. I never knew you were involved with those, but I have certainly used those kiosks with my kids. Thanks for sharing this.
My oldest son and his cousin were the age of the target audience so they were the test subjects. Now he is getting married this year. How time flies. I see more and more grey hairs popping up.

Popular posts from this blog

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 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

The iPhora Journey - Part 4 - JSON is King - The How

  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 The iPhora Journey - Part 4 - JSON is King - The Why The iPhora Journey - Part 4 - JSON is King - The How As we mentioned yesterday, in reimagining Domino, we wanted Domino to be a modern web application server, one that utilized a JSON-based NoSQL database and be more secure compared to other JSON-based NoSQL platforms. A Domino document existing within a Domino database is the foundational data record used in iPhora, just as it is with traditional Domino applications. But instead of just storing data into individual fields, we wanted to store and process the JSON in a Domino document.  However, text fields (AKA summary fields) in Domino documents are limited to only 64 KBytes, and that is a serious limitation. 64 KBytes of JSON data does not even touch what the real world typically transfers back and fo