I’m curious how many of the new issues are Android only. As a new target I would expect a lot of issues reported against it.
In my ideal world I want to know how many new and closed issues were for each target type (desktop, web, mobile) or even by OS (Mac, Win, Linux, iOS, Android, RPi) and how many reported against the IDE. But then there are so many variations on targets these days it wouldn’t tell you much. I could be wrong.
One caveat though
The #'s I see will likely NOT be the same as what you see since it will depend on things like confidential cases I can see vs what you can see
And thats likely to differ
but those #'s will be in the right ballpark give or take a few
But don’t worry, Geoff’s trying to train ChatGPT to write Xojo code and bake it into the IDE, so in the future, it will take even less time to re-write your existing apps into the current version of Xojo.
Sheesh… It’s like he heard what we’ve been complaining about and then decided to do more… Just fix the damn bugs, inefficiencies and work on things like Aliases, Macros, pre-emptive threading etc… You know, things that will actually lead to better quality apps.
Well, Android SUCKS. Compiler error with a simple msgbox it feels like some proof of concept or pre-apha release.
BUT that XAMLContainer is really interesting. For one thing, xojo FINALLY have a way to use the native renderer (WebView2) after ditching it in the WebView control.
This can really improve the windows target.
It is a shame that there is no XAML window and visual designer for it, with all the controls created in the same container. For now, having each control in their own canvas container can have a performance hit, but it looks promissing.
Nothing against Björn and Christian, I used their Addons a lot (Björns’ more than Christians’) but compared with everything in the open source sphere or even enterprise commercial sphere Xojo was/is… how to put it in polite words… uhm… special kind of scam?