Skip to main content

Engage 2017 and Presentation - Unleash the Power of REST APIs with Dojo

At the beginning of this week, I was fortunate enough to attend Engage 2017. This was the first time that I had not only presented at Engage, but also attended Engage.  Theo does an amazing job in creating this premier event.  The turnout for my session, "Unleash the Power of REST APIs with Dojo"  was more than I expected.

It has been awhile since I was in Europe.  So I took a couple days off before Engage to visit Amsterdam which I have never been to and a couple days after Engage to visit Belgium.  Amsterdam, though it has a lot of history, I found it too much of a tourist trap.  After the first day, I wandered off to the outskirt of the city where there were less tourist and had great time.  I got the Amsterdam Card and got into most of the museums and places at no additional cost.  I was able to ride the metro and trams with this card at no extra charge.  However, it does not work for some buses.  The lockers in Amsterdam station are great for tourist to leave their luggage while you tour the city.  Just make sure your credit card works with the lockers, before you close it.  Also bring coins with you because water closets ( rest rooms ) are not free in the train station.

Antwerp, Belgium is a beautiful European city.  Rather than walking throughout the city, I rented a bike for the two days after Engage and biked about 140 km mostly in the countryside where I found it to be more interesting.  My adventure in Antwerpen was more of getting lost and trying to get back to the Cyclant Bike store where I rented the bike from before they close each day. Jona and Nicolas are great.  I would recommend them if you need a bike for the day.  They are located in the Antwerp Train Station.

I have enclosed a link to my presentation plus the source code for all the demos.

https://www.dropbox.com/s/6tentwxi8vcwtxe/Unleash%20the%20Power%20of%20REST%20APIs%20with%20Dojo-Engage%202017.pdf?dl=0

https://www.dropbox.com/s/5ou0dn8u6xx6pev/Engage%202017%20-%20Demos.zip?dl=0

Comments

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