Skip to content

Index

Reaping the Benefits of Standard

More than three years ago we began work on VoltScript. A little over a year ago we released our first Early Access code drop. There were certain core principles to which we developed. Two of these were a modern developer experience and adoption of standard development practices.

Over recent weeks I received ample evidence of the benefits as I improved and extended Archipelago, the build management engine of VoltScript.

XPages App to Web App: Part Ten - Ship Form Actions

In the last two parts we created our first web component and converted the login function into services we could use for all data interactions, the first use being to load data for any select controls in the application. Now it's time to create the ship form.

XPages App to Web App: Part Nine - Services

We've got a login and a landing page, we're ready to start building the bulk of the application now. But we need the data. In part six we handled the login, both for a mock session and the actual authentication to Domino REST API. But that format is going to quickly get messy as we build out the rest of the application. We can do better.

LotusScript Classes and Delete

A couple of years ago I wrote a number of blog posts about LotusScript / VoltScript classes. The topic is relevant to both languages, we've not made any changes to how classes are managed in VoltScript, even though we discussed adding some things added to Visual Basic since LotusScript was created, things like additional modifiers. Even though classes are still the same, we've used some quite sophisticated aspects of class, as will be apparent to anyone who has looked at VoltScript Testing, its LotusScript port bali-unit, VoltScript JSON Converter, or VoltScript Collections.

Framework App to Web App: Part Six - Mocking, DRAPI and CORS

In the last part, we created for login form and added an eventHandler to call formLogin() function. However, we didn't go into the code behind that function. That function is pretty basic, offloading the bulk of the processing:

const formLogin = () => {
  let username = document.getElementById("username-input").value;
  let password = document.getElementById("password-input").value;
  login(username, password);
};

Framework App to Web App: Part Five - Home Page

So it's time to start with the application. Any development - team or individual - should use source control. My usual approach is to create the repository in GitHub (or your preferred repository), then clone it locally. A README is best practice of course. And I'll be creating two subfolders, "webapp" and "bruno" - because bruno allows me to store the REST service collection and environment in the github repo.

Framework App to Web App: Part Four - DRAPI

Domino REST API is (in my admittedly somewhat biased opinion) the best easy method for creating a secure REST API into Domino. If you have very strong Java skills, an OSGi plugin using JAX-RS is the standard supported way. If you have good Java skills, Jesse Gallagher's JakartaEE project is the community approach. But even if you have those skills, Domino REST API may provide what you need. It certainly provides what I need for this project.

Framework App to Web App: Part Three - Frameworks and the Internet

A Brief History of Web Development

Until now, the series has focused on XPages. That's understandable considering my previous series that this is inspired by. However, recently it's become apparent that much of this series is relevant to a much wider audience than just XPages developers. Most web developers are used to developing with a specific framework. That's understandable considering the history of the last 20+ years. But that means this series is relevant to a much wider audience than HCL Domino developers using the JSF-based XPages framework.