We still need to use 2019R3.2.
Until now we had the old documentation available in Dash (kapeli.com) but they are now removed.
Sure, there’s this crappy inbuild documention in the IDE, but … I keep my thoughts.
There was the old documention under “docs.xojo.com” but it is also removed.
Therefore my question:
Is the 2019R3.2 documentation still available somewhere?
Try getting in touch with Norman. You will need to build your own UI to search the database, but you can adjust the search tools to your liking.
Nice…
@Geoff_Perlman as you said, you still support old versions.
Can you provide a webarchive or something for the old documentation?
2019r3.2 has documentation built-in to it. You just need to turn on that preference.
In the new system, we do have an on-line archive of each version of the documentation (starting with 2022r1) so users will always have access to documentation online going forward in addition to the built-in versions users can use when they don’t have internet access. Unlike the old docs, the new system makes it easier for us to provide on-line and off-line experiences that are closer to the same.
@Lars_Lehmann You’re indeed correct about Dash and 2019r3.2 now missing. This version was created by Kapeli themselves and I’ve asked Bogdan to bring this version of the documentation back.
If you like, you can follow along at…
The built-in documentation lacks on some crucial features. We never used it. Isn‘t it possible to bring that old docs under https://old.docs… or so back?
I remember it and it certainly wasn’t as good as the online docs. Bringing it back takes time and the percentage of users on versions that don’t use the new docs system has been dropping quite steadily. In fact, less than 4% of our users are using a version prior to 2023. What is stopping you from upgrading to a new version?
Looks like the Dash dock set for that version is available.
Thank you for mentioning. This helps. Therefore a vendor documentation is not needed from Xojo anymore.
That you dropped web 1 support in newer IDE versions. And that migrating to web 2 is essentially a rewrite.
If you would have continued Web one, I would pay for 10 pro-licenses here each year. Now, we maintain the old version and changed platform.
Thank you for the fast reply.
) users:()
That’s making a HUGE assumption in how people need to use the documentation. Since we cannot and will not move to API 2 the new documentation is essentially worthless to us.
What assumption am I making?
I guess they’re able to see the statistics over the licenses which are still pulled from their servers (where I am afraid of, when they change the license infrastructure once).
