I understand that the future of Xojo is API 2.0. I have used API 2.0 and while I disagree with some of the naming conventions I can live with it. I do have a problem with many of my older projects, however. My older projects, especially the big ones, will most likely never use API 2.0 because it’s simply too big of a task to convert.
To upgrade to API 2.0 for a desktop project I have to change my error handling to go from checking for error codes to handling exceptions. Any string manipulation cannot simply be upgraded because the older API is 1-based and the newer one is 0-based. And the sheer number of property name changes is disastrous in some projects. Converting from Date to DateTime is not a simple replacement either.
That’s not to say that these things are not doable but they are not desirable right now. And I’d really like to not accidentally invoke an API 2.0 method or property because AutoComplete shows me both. AutoComplete conveniently shows me the old, classic property/method in red which is great but I have no way of knowing what is new for API 2.0. Therefor I’d love to have the option to choose what is shown in AutoComplete.
Feedback 57885 Feedback #57885 is just that. This case is currently ranked fairly high so I’m not the only one that thinks this is a great idea. The basic gist of it is this: there is a preference setting that allows me to select what I see in AutoComplete, API 2.0, API 2.0 and Classic, or just Classic API.
In the ideal world (as stated in the Feedback case) this would change the deprecation warnings for API 2.0 if you’ve selected Classic API and it would also switch the local documentation to the proper usage to avoid confusion.
Obviously, Xojo does NOT want to implement this because API 2.0 is the future of the platform. My argument is that without this mechanism many of us with older, big projects, won’t update our licenses because we can’t/won’t use Xojo with API 2.0.
This is not a good situation to be in because I feel we’re one macOS upgrade away from disaster. If you’ll recall before Catalina was released FolderItems were broken in for a while. This turned out to be an Apple bug that was fixed. Another example is the ColorPicker and if you’re using an older version of Xojo you have issues with it that you have to workaround. What happens with Son of Catalina comes out and something else is deprecated and we *have to* upgrade to newer Xojo.
You might feel like I’m complaining for the sake of complaining. I assure you I am just looking out for my clients assets and my own hard work. I can’t justify the cost and expense to upgrade to API 2.0 and I really don’t want to mix and match API’s. I could use a newer version of Xojo but I just can’t take the chance of using something (API 2.0) that’s not fully proven (to me) yet. All it takes is one mistake and I have a mad client.
Currently 57885 is ranked 9th. If you’d like to see it get implement throw your points at it. What do you think? Am I agonizing over AutoComplete too much or do you think I’m justified in my concern and request?