Ogre Forums

Just a quick note that the new API reference for Ogre 1.9 [with a new more matching color theme] is now online:
http://www.ogre3d.org/docs/api/1.9/

Since however there are still some people out there working with Ogre 1.8 or even Ogre 1.7, we also keep those available. That's how nice we are ...

The older versions can be found under the following link:
http://www.ogre3d.org/docs/api/X.Y (replace X.Y with the version number, for example 1.7).

Additionally, we create a generic link that will always point to the current stable version (currently 1.9):
http://www.ogre3d.org/docs/api/latest

If you should face any issues, please let us know.

BTW: Of course we also redirect the old "single point-of-truth" link to the generic one, so all old links should still work:
http://www.ogre3d.org/docs/api/html/index.html

I think the "latest" should be an alias, not a redirect.
It would be great if you can do something similar with the manual

scrawl wrote:I think the "latest" should be an alias, not a redirect.

Had the same thought at first, but decided against it for SEO optimization reasons: With a redirect the actual resolved/redirect destination URL gets the good ranking, not the start URL. My train of thought was that then the actual Ogre class for that specific Ogre version gets the best ranking possible.

But now that you brought it up again, I am actually leaning towards changing it, since if someone is e.g. searching for "viewport ogre" he/she is probably looking for the API reference of the current version and so "latest" would be perfectly fine. If the are trying to look-up the API for a specific legacy version, they have to either adjust their search term or manipulate the URL directly.

So if no other arguments are brought into play, I will change the server config to use aliases.

scrawl wrote:It would be great if you can do something similar with the manual

Agree.
There is no manual in the precompiled SDK 1.9. Why?

scrawl wrote:It would be great if you can do something similar with the manual

It is on the ToDo list.

Pulas wrote:There is no manual in the precompiled SDK 1.9. Why?

Probably because Kojack simply missed it when building the SDKs . But they will have to be re-created anyway since a major bug was found and fixed since their creation.

Ok, good idea, well done. I will continue to host the researchable API anyway.

spacegaier wrote:So if no other arguments are brought into play, I will change the server config to use aliases.

Just FYI. I haven't been able so far to switch to 'alias' usage. Will have to dig deeper into the NGINX documentation sometime in the future.