twinBASIC Update: July 18, 2021
On April 23, 2021, I helped Wayne Phillips introduce the world to twinBASIC at the Access DevCon Vienna conference. I boldly predicted that twinBASIC (along with the Monaco editor) would replace VBA and its outdated development environment by 2025. With that goal in mind, this weekly update is my attempt to keep the project fresh in the minds of the VBA development community.
Every Sunday, I will be providing updates on the status of the project, linking to new articles discussing twinBASIC, and generally trying to increase engagement with the project. If you come across items that should be included here, tweet me @NoLongerSet or email me at mike at nolongerset dot com.
Highlights
There were no major updates this week. I assume Wayne is hard at work on the form building interface.
Around the Web
Debug console IntelliSense planned
Yours truly requested that the parameter hints and autocomplete available when editing code also be made available in the Debug Console. Wayne tagged the request with a Planned label, so we've got that to look forward to. Which is nice. Especially since I'm a known IntelliSense junkie.
Web forms support announced
In a follow-up to last week's topic on control inheritance in twinBASIC, Wayne announced that there will also be support for web forms at some point in the future:
Yes, web forms are planned once the web-server extension goes live, and the form-designer I'm creating now will be re-used for it.
Changelog
Here are the updates from the past week. You can also find this information by installing the twinBASIC VS Code extension and clicking on the Changelog tab of the extension page:
[v0.10.3429, 15th July 2021]
- fixed: runtime dereference of nullptr [ https://github.com/WaynePhillipsEA/twinbasic/issues/274 ]
- fixed: editor crash on bad code [ https://github.com/WaynePhillipsEA/twinbasic/issues/276 ]