Skip to main content

CollabSphere-Chicago (GRANITE) - Spring 2018 Meeting Agenda, April 25th, 2018

We are happy to announce that we are having a Spring 2018 GRANITE meeting.  We have renamed GRANITE to become CollabSphere-Chicago.  Our Spring 2018 meeting is packed with sessions.  We are fortunate enough to have a number of great speakers from IBM, IBM Customer, and IBM Partners.

If you are interested in attending this meeting either in person or remotely, you will need to register for the meeting. There is no cost to attend.


CollabSphere-Chicago (GRANITE) - Spring 2018 Meeting Agenda

Location
IBM Technical Exploration Center
(Hyatt Center, West Loop)
71 S. Wacker Dr. 6th floor
Chicago, IL 60606

If you are attending in person, you must have your ID and have registered to enter the building and attend the meeting.  Remote attendees will receive a link to the video conference after it is made available.

08:30 - 09:00 AM 
Continental breakfast provided by GRANITE - ONSITE ONLY WE DO NOT DELIVER

09:00 AM -10:30 AM
Presentation: Domino V10 - #domino2025, Notes on iPad
Presented By: Andrew Manby and Luis Guirigary, IBM

 10:30 AM - 10:45 AM
Break

10:45 AM - 11:45 AM
Presentation: Customer Experience - Domino on Docker
Presented By: Slobodan Lohja, Canal Barge

12:00 PM - 12:30 PM
Lunch provided by GRANITE - ONSITE ONLY WE DO NOT DELIVER

12:30 PM - 1:30 PM
Presentation: Watson Workspace Plus,
Presented By: Darren Cacy, IBM

01:30 PM -02:30 PM
Presentation: Introduction to TypeScript for Domino Developers,
Presented By: Richard Moy , Phora Group

02:30 PM -02:45 PM
Collabsphere/MWLUG Update
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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
Post a Comment
Read more

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
Post a Comment
Read more