Already we have created more enhancements than were made when LotusScript was added into Lotus Notes from the rest of the Lotus SmartSuite family of products. But this is just the start - both for language enhancements and developer tooling. The intention to bring an additional backend language to Volt MX that will be famliar not only to Domino developers but also VB6 and VB.Net developers, modernised and enhanced for the current development landscape. We already have a wish-list of enhancements - Big Hairy Audatious Goals probably beyond what many can conceive. And of course, we have also looked at what is already on Aha. Will we achieve them all? Who knows? But we will dare to try, and perhaps even catch.
Very few software engineers in our limited but highly colourful history have had the opportunity to create a new programming language. And yet, we have that chance along with an incredible legacy of LotusScript and its millions-upon-millions of running lines of code to do something that will truly inspire our customers and partners. And just as this is a once-in-a-lifetime opportunity for the research team tasked with the project, it’s also a once-in-a-lifetime opportunity for the community. This is a call-to-arms to tell us what you think we should add.
Bear in mind that the target runtime for VoltScript is not HCL Notes or Domino and the deployment target is not an NSF; VoltScript is designed to run anywhere it needs to in the HCL portfolio. From personal experience, we know this is a challenging change of mindset. For example, lsxbe (the LSX containing the Notes backend classes) will obviously not be available.
We know many of you have already asked whether everything will be ported back to LotusScript. Once the non-Domino mindset is achieved, it becomes apparent that not all the new changes we need to make will be appropriate for Domino. Some work will be necessitated because the code is being deployed to and triggered from Volt MX Go’s Foundry. That also means different tooling options, which opens up opportunities that may not be appropriate when the development IDE and target build artefact is an NSF. And some opportunities, like mocking Notes classes, are not possible when the actual Notes classes are already automatically added by the runtime. Some changes may be candidates for porting to LotusScript, but we are a research team for Volt MX Go, not a product maintenance or core engineering team. So, we are not the correct engineers to make such decisions and now is probably not the right time for such decisions.
This is not an existing product, so Aha is not the appropriate route to share your feedback. We don’t intend to choose how VoltScript evolves based on the most popular requests as there are different priorities based on minimum viable product and skills required to implement.
In the coming weeks we will share here and elsewhere our current list of features we wish to implement. Contact Paul Withers through various social media or OpenNTF’s Discord or Slack if you want to be a part of what will prove to be yet another adventure.