What do you believe what was happened to me? When I was ready with my application I had to rewrite it while web2 could not produce what I needed. Web 1 could but was deprecated. And, within one or two years, we will not be able to run that projects on actual browsers anymore. So what: that story ended.
Yes, the genius. Just as the old documentation (with links to the same) does not lead to the exact position in the new documentation, but only to the start page. Brilliant. The developer, aka Genius, only thought half of it, if at all.
I would have guessed that if I clicked on the link, I would end up at “var” in the new documentation. Especially since the old documentation was apparently database-driven, so the new links could have been included there. Apparently that was overlooked.
Developers are known to think in an unstructured and cumbersome way, and that’s why it “naturally” doesn’t work to simply replace the sub-domain. With documentation.xojo.com/Var you end up in Nirvana (page not found). Well done.
If you are one of those long time users who has grown accustomed to the inconstancies that API 2.0 addresses, you might be wondering if there’s any value for you in using it. The answer is absolutely yes! While it will take a little time for you to get used to the new APIs, what you will find is that you become increasingly more productive because they are so consistent. You will find (as I did) that you can guess at what the API is and likely be correct. I personally made 95% of the Language Reference updates for API 2.0. The documentation wiki does not auto-complete so I had to double-check all the code I was updating. In no time I found that I rarely made errors because API 2.0 is so consistent. You will absolutely see productivity gains once you have used it for a short time.
“I personally made 95% of the Language Reference updates for API 2.0”