New documentation is hard to love

And now the local documentation is even worst :roll_eyes:

Xojo replaced the individual pages with HUGE single pages with LOTS of content each one at the same time they REMOVED the option to SEARCH in the page as previous documentation. Control + F on windows.

Is this another consequence of not giving support for the NATIVE renderer on windows?

Stop removing features and give propper support for the current native renderer that is already installed on most windows machines.

meanwhile, find a way to enable the in the webkit renderer for the New documentation, it is a real pain to look for something in those absurdly giant pages.

And the option to open in your favourite desktop browser is also gone, I can’t really get my head around removing that then forcing the page to open in the internal htmlviewer which has had reduced functionality for two and a half years only for Geoff to recently suggest the exact same thing in a round about way and for it to almost immediately get scheduled…

I have to say, I really detest some of the form over function decisions xojo makes either by design or by accident.


Yet another problem avoided by not renewing my licence beyond 2019r2 :partying_face:

If he says that you were talking about a different thing… He must know better what you meant and what you want…

And speaking about a bad documentation, there are several mentions of the “windows native renderer” in the DesktopHTMLViewer documentation although xojo decided to ditch the native renderer. Totally ridiculous to add like 200 Mb to an app just to display some basic HTML content when MOST windows PCs already had the New WebView2 runtime installed.

Are you sure there is no option to choose which renderer to use? If this is indeed not the case, it would a massive mistake for sure.

You can open the documentation on the following URL:

You can then find on page, bookmark items etc The old documentation is available on

1 Like

I believe the discussion turned to the local (offline) documentation. I might’ve misunderstood though.

Well, xojo deleted the renderer property section, but all the other properties afected by the renderer still mention it.

Try searching for renderer and the documentation will show you the DesktopHTMLViewer

Yes I know, thats how I noticed the really bad job at removing the renderer from the DesktopHTMLViewer.

But it is a shame that the built in functionality (offline documentation) is not that usable