Domino Interface

Building a Web application on HCL Domino can be challenging because there are so many ways of creating a Web application. There is just no design pattern to follow or best practices.  This is good for us who like to experiment, but bad for developers who just want to follow an official approach.  You can use XPages, classic Domino Web with Pages, computing fields and computed text with formula language or you can create apps using REST APIs with LotusScript, Java , DAS (please no) , view read entries or even DRAPI as Paul Withers has demonstrated on his blog,  https://paulswithers.github.io/blog/2024/08/15/xpages-web-1/ However, there is little talked about a very old technique that dates back to the beginnings when Domino became web enabled.  As part of my data visualization session demo at Engage 2025, I used this technique to generate the web pages and dashboards.   This technique allows you to separate the form, data and business logic and creates a sta...

Thank you everyone for attending my Engage 2025 session, Visualizing your Domino Data using Open Source Tools. Though I was up against some formidable sessions, I was surprised to have close to 30 attendees in my session. As promised, here is the PowerPoint presentation and sample databases and code. I would like to thank Kris and Tom for an incredible event and for selecting my session for this year's event. They did a wonderful job in continuing the tradition of making Engage a premium event.   After Engage 2025, I spent a day visiting different sites in The Hague.  The walk to the beach was a bit longer than I was told!  https://phoragroup.com/files/Visualize_Your_Domino_Data_with_Open_Source_Tools.pdf https://phoragroup.com/files/engagedemo.zip

When building a web application, optimizing the loading process is important. Previously, we used Uglify-ES and recently Terser to minify individual JavaScript files to help reduce the packages and load time. With the next release of iPhora Automatic coming very soon, we wanted to significantly reduce the loading time needed and the number of HTTP requests handled by the Domino server. Our struggles for the past few weeks have been figuring out the right JavaScript bundler that works with our Dojo Toolkit-based framework. So why are we still using Dojo Toolkit you might first ask? Many have moved away from Dojo Toolkit, the granddaddy of JavaScript frameworks. Dojo provides us the core widget inheritance framework that is not just used for creating widgets like fields and combo boxes, but is used for building the many different app layers of iPhora not just statically but dynamically in real-time. It allows us to have a secure and fast SPA (single page application) architecture. We d...

If you are attending Engage 2025 and would like to learn more about how to visualize your Domino data, come join my session.   Wednesday, May 21 | 14:30 - 15:15 | 1.4 Breakout 2    De09. Visualize Your Domino Data with Open Source Tools As they say, a picture is a worth a thousand words. In the current data driven environment, having the ability to quickly visualize your Domino data is important. It allows you to discover hidden data patterns and trends that may impact important business decisions. There are a number of open-source visualization tools that one can use to create charts, graphs and plots. In this session, Richard will discuss the different tools that are available and their advantages and disadvantages. Richard will show how to utilize these open-source visualization tools to help you effective visualize your Domino data. To learn more and register for Engage 2025 go to https://engage.ug  Hope to see you there.

As I mentioned in the previous blog post, the use of spreadsheets is the largest and number one method used to create situational apps.  In part 2 of this blog series, we will do a comparison between using spreadsheets versus no-code/low-code tools to create situational apps. Click on the link below to continue reading about this comparison. https://iphora.io/iphora.nsf/blogentry?open=VQ34NT01

As the name implies, situational apps are on-demand apps that are created in response to a specific business situation (or need) that may arise infrequently. In general, the productivity gains attributed to a situational app are limited to only a few occasions a year and to few individuals. Therefore, most corporations are unlikely to devote significant resources to the development of such apps, and typical develop cycles may be so long that the situation itself will have expired before a professionally-developed app is ready. To continue reading more about how important situational apps are go to our iPhora blog at: https://iphora.io/iphora.nsf/blogentry?open=0F71X90S