This situation could have been avoided quite easily by running a separate technology preview programme for Web 2.0 and only merged it into the main product when it was close to being ready.
3 Likes
At this point I’d agree
They have no choice but to continue on with the path they have set themselves on
Its unfortunate that they have put themselves in such a position
1 Like
exactly what I said several times recently, total no brainer, or get some help in to work on parts of the project that can easily be worked on by others, there are a lot of clever people in the Xojo world who I have no doubt would be pleased to do some work for a free licence or two if it gets the job done more quickly with less bugs and just plain released.
I renewed December last year and basically got screwed completely with a totally pointless release cycle and headless chicken approach from the company about what should/should not be done.
1 Like
I see them having 3 options:
• Rip Web 2.0 out & put Web 1.0 back in and release that as 2020r1.
• Merge the bug fixes from 2020r1 into 2019r3.2 and release that as 2020r1.
• Stick with it until it is good enough to ship.
Unfortunately, none of the choices are good, add unnecessary additional pressure onto the staff and result in Xojo Inc. having egg on their face.
We caused the same problem for ourselves several times until we finally decided to change our ways. I just hope that Xojo Inc. have learned a valuable lesson here.
2019r3.2 was released today.
Only addition is Big Sur / Apple Silicon.
Apparently not worth the download if you do not run one of the above.
2019r3.2 is not exactly what I call an interim release, it’s more like an emergency patched release. In essence it is just the same r3.1, but running on the updated beta OS.
A interim should include some of those fixes in R1 too.
That would be the best, smart move. And it should have been done in June.
Kind of useless for practical uses. It’s only interesting for those focused on “preview technologies” and just for MacOS. It’s more a marketing thing (“we are on the edge, we are ready”) than anything else.
And if it stays that way, you will still be able to run API 1 code, but you won’t have the local language reference from 2019R1 available, which is a problem for using API 1.
-Karen
Hi Karen,
yes that is an issue for sure, but for a few years I have been using Dash as my LR and that allows you to download the docset for each version and only search in one version if you wish, for me an invaluable tool to completely ignore API2.
A quick look inside the Xojo application package on a Mac seems to indicate that the local language reference files are self contained in a subfolder. I wonder if it would be possible to copy the 2019r1.1 version of those files into a later version of Xojo.
Well, this only shows that the QA at xojo is not great 
They didnt expect that Web 2.0 had too many problems.
You are right, they said that web 2.0 and android had their own chanel, so, for a complete new technology there should not be problem to keep releasing current bugs to other parts of the framework with Web 1.0 alognside a beta versión with the web2.0 progress.
And since they are killing Web 1.0 with no further maintenaince, to show some respect to clientes, at least they should had a release las Web 1.0 release focused on Web 1.0 bug fixes.
I would think you can copy the help files over no issue, good idea! if its not working you could always just open the IDE, open the LR and minimize the IDE?
I think this release should be praised. AFAIK this is the first time Xojo have essentially back-patched a previous year’s release to support a new operating system.
I have hammered and hammered about not having access to documentation history. At this point, it’s clear that Geoff simply does not care. I don’t think we’ll ever see it come back.
1 Like
breaks the signature
but yeah I cant think of any reason that would not work
it took a long time to get him to understand why people just didnt update every one of their projects to the very latest version
The docs may be similar
True
It’s also the first time they have been in a position they needed to because there was no “current year” release out yet
1 Like
I don’t think releasing a version with all the bug fixes after SIX MONTHS could be described as “rushing it”.
Sorry, but this isn’t a case of “Xojo can’t win”, this is a case of “Xojo being bloody stupid”. It is embarrassing to watch, and if I had bought a license after 20199R3 came out I would feel cheated.
But maybe I’m looking at this all wrong. Maybe Xojo wants a release that EVERYONE has to buy. Make it seriously big, full of new features, lots of important bug fixes, and incompatible with the past. Result would be lots of money unless people leave Xojo for good. Maybe more of a desperate late gamble because Xojo was trapped in a downward spiral?
I doubt its anything quite this nefarious
Its more likely its just “uh we thought we’d have shipped by now” and that they seriously underestimated how close to done they were early in the year
So they stated that 2020r1 would be Web 2.0 and thats the stake in the ground - and they have more work to get there than they thought
So now they just have to plow on because they dont have any way out of this jam they stuck themselves in
It looks like it works.
I replaced the 2019r3.2 XojoLangRefDB with the one from 2019r1.1 and Xojo launches. I also performed a search in the Language Reference for Middle and did not find the new string extensions.
1 Like