I honestly don’t see why there’s all this hubub to move to API 2.0
By trying to allow existing projects to continue to build without changes, Xojo won’t be removing the classic framework for a very long time. I feel quite secure in not prioritizing API 2.0 with my workflow.
Considering that API 2.0 database interaction is unreliable, I haven’t had the inclination to transition my projects.
New editions will become API2 friendly only. Once you use a new edition because it fixes some old bug you need fixed, and do some clean up and save, eventually all your support for API1 (like the horrible dual API1/2 autocomplete) is gone and things get even worse to maintain. Old bugs are fixed only in such new editions forcing API2 adoption. API2 will be enforced and staying on API1 will not be something easy, it will become unfeasible eventually.
There are just enough threads in the Xojo forums where people have run into issues updating to API 2 and then reverted to API 1 and the problem went away that there is a definite lack of confidence among some
Personally I’m using MBS because of the particular projects I’m using that require things the Xojo db plugins dont do (ie/ accessing MS SQL from any platform is one)
However, the times I have tried to post a reply to a person about their issues I have run into glitches with API 2
Xojo really needs to sort those out so peoples confidence in the new DB API is well founded
I worked with Xojo 2019 r3.1 for a few days and ended up getting quite a few crashes:
and about another 7 crashes. It is to the point where I was politely asked to not submit more feedback cases. The hard part is that I am not able to reproduce the bug, and it crashes frequently. These issues didn’t exist in 2019 r1.1 (API1). More feedback reports are now being asked.
There are some bugs that definitely need to be removed even though theoretically I can use API1 code.
From what I am experiencing, building without changes to API2 is causing issues.
Well… What I said is inoffensive, doesn’t break any known rule, and is even a good PR.
There’s a post THERE about the current cycle that made me think they would call the attention of the author and they didn’t, what I said can’t be listed in any bad behavior rule.