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.
Another quiet week as Wayne continues working through the first release of GUI support. It sounds like that release could be here soon, based on Wayne's comment yesterday:
I'm putting together some samples over the next few days (e.g. a simple datagrid), and then I'm going to pass things over to the community here to see what happens whilst I switch to working on 64-bit support for a couple of weeks.
Around the Web
Andrew Mansell opened a discussion regarding Data Binding:
The data binding capabilities of VBx are limited, and by extension so are those of WinForms in .Net. The data binding capabilities of WPF are comprehensive, but also very difficult to learn. Is there a middle ground?
I love this idea. I develop primarily in Microsoft Access, but I have done a couple of WPF desktop projects (in both VB.Net and C#). I love the clean separation of concerns that data binding delivers via XAML in WPF applications. The problem is that it is an absolute nightmare to debug.
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:
Nothing to see here this week!