XPages for Lotus Notes Client

At Lotusphere 2008, there was discussions about XPages and how it would change how Notes applications are created. Since I was so busy with booth duty and other events I did not attend any of the sessions that involved XPages. However, Rob Burton from my group did attend a session that talked about XPages. Yesterday, he asked if I attended any of the sessions that talked about XPages and I said no. I did briefly hear someone talk about it, but did not pay attention. Surprising he said from what he has learned XPages does a similar thing we having been do for over a year in our Integrated Business Framework system by removing the data from the form. Similar to the concept of XPages, in the Integrated Business Framework design when you open a document you are really opening up a form that can collects data from many databases. The form is automatically populated based on a set of XML configuration data. During the save process the data is stored not as a single document, but the data is store in the corresponding databases. The technique we develop was design for use in the Notes client but could be extended to the Web.

We mentioned this approach in one of the BOF in Lotusphere 2007 and some at the BOF thought it was not a good idea. Interesting that is now the big new thing. XPages will probability do much more than what we have created, but I am glad that IBM is move towards this approach. It will be a good thing when XPages comes to the Notes client.

When I have time, I will create a demo database showing this technique and that it can be done using existing Notes clients. However, I will only be able to give you a demo but not provide the source code since the code is proprietary.

Comments

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

Domino Interface

Search This Blog