Intec are proud to be sponsoring Charlie's Promise in 2025. Please read more about their Vision here.
Yesterday Node-RED 1.0 was released. For those of us who have been using Node-RED for some time, this doesn’t mean any change in the stability of the product. But it’s a significant milestone. What’s also impressive is the scale of increase in adoption, as highlighted in this tweet: There have been some significant developments over […]
Node-RED 1.0 Released Read More »
One of the big amendments in Domino V11 is pub sub. It brings a lot of potential, but only with the proper understanding of how to leverage it. It’s a concept many Domino developers may be unfamiliar with, but one that has a lot of parallels in web development. In Vert.x there is the Event
Understanding Pub Sub Read More »
Earlier this week I had a discussion with Graham Acres about an error with ODA. Firstly, there are two scenarios around plugin errors, and it’s important to know the difference: Errors in the “Problems” view in Domino Designer. This is a problem with your Designer client – or the last Designer client the application was
OSGi Plugin Troubleshooting Read More »
Richard Moy added an interesting comment to my last blog post, wishing that HCL would add Web Sockets support to the core. It’s a popular requirement, and one that people have tried to work around. John Jardin added a web sockets server to our React application for our JavaScript session at IBM Think 2018, so
What Domino Makes Trivial Number Three: Web Sockets Read More »
Another topic that becomes key when moving beyond Domino is synchronous and asynchronous processing. But it’s probably something most Domino developers haven’t come across. LotusScript and standard Domino Java are single-threaded. That means your code starts at line 1, runs line 1, then line 2, then line 3. If line 4 is a function /
What Domino Makes Trivial Number Two: Synchronous / Asynchronous Processing Read More »
Don Mottolo makes a good point in his comment on my recent blog post, that there are aspects of other web frameworks that make it a non-trivial task. This is also really why some people talking about Domino are talking about “mid coders” and “pro coders”. And it’s also why the terms don’t really exist
What Domino Makes Trivial Number One: State Management Read More »
A comment from Mark Maden on my recent blog “Thoughts on the Problem of XPages” prompted me about a potential area XPages could add value for the future. One of the strengths of XPages from the start has been flexible reporting. Indeed my very first session at a conference, at BLUG (now Engage) nearly ten
A Possible Role For XPages Read More »
A common request seems to be how do I use XXXX Java or JavaScript project in XPages. One of the strengths of XPages was that it made the approaches more standard. So the answer is often less an XPages question, and more a generic web development question. There are a few caveats, but many of
How Do I Use XXXX Java / JavaScript in XPages? Read More »
Jesse Gallagher posted a thoughtful blog about the challenges for the way forward with XPages. It’s a challenge I’ve had a number of discussions around, many of which are ongoing. The reason there’s not a simple solution – throw whatever resources are required into XPages – is that it simply doesn’t make business sense. There
Thoughts on the Problem of XPages Read More »
I didn’t realise this post was still in draft, so it’s took much longer than expected to publish. But it’s quite timely, because this covers Node-RED, and a blog post has been published this week covering some of the content from the slides of my session with Fredrik Malmborg at Engage. Still, better late than
Modernising Domino Applications: Technical Deep Dive Part Three Read More »