Lots of things are fixed and improved and the database improvements without needing horrible prepared statements are much improved. Worst part about all of this is R2 is actually a good release. Some of you will not use R2 because of event renaming but I promise you it could have been much worse. Funny, when they realized this, they changed the name of the class which is actually what should have been done in all cases of event, property, and method renaming. If you have any existing code, you would reject using R2 on the premise that is completely and utterly borked. Depending on the constructor you use, all properties silently changed their behavior and there is no way to know this in advance. Likely, you would ask for clarification about why I mentioned the default constructor. What if I had said the reason your code does not work was a subtle change to the default constructor that made the entire object immutable? All I would get back from you is a puzzled look. It is annoying and one questions how or why this is possible, but it makes sense. Opening() broke my code you would understand. If I sold you a plugin and it did not work and I told you that I implemented. Who is driving the technical direction here? The class that we all use every day had been changed in ways that are completely and utterly mind boggling. I am not as upset as I could be as there was an even more asinine change that we luckily got reverted. The fact that the choice is not possible or was never considered is the part that makes event renaming as delivered a rookie platform mistake. The constructs of classes having events is the same regardless of their names so why does the IDE care which version you use? All it needs to know is which library to use for code completion. When you create a project, it should ask you 'API v1 or API v2' and that's it. Open() event I can just stick with Xojo Desktop v1. If I want to stick with my trustworthy but not entirely clear when it fires.

It is ridiculous, but it gives the developer choice. Platform makers often just create entire new frameworks like WPF, UWP or WinForms. It would be ridiculously awkward and painful if new projects started with AppV2 or WindowV2. The crux of the issue is the language and standard library are presented as a single entity in the IDE.

In other languages they would release a new class. Events are part of the core contract of the whole object hierarchy and all code developed in an OOP fashion relies on the stability of those events. In fact, I cannot think of any language that renamed events on their standard library classes. Not because the philosophy behind the changes is wrong but because the IDE was not designed for it. I think renaming the events was a mistake. Lot of chatter in the blogosphere and forums about API 2.0.

Xojo review