Dev talk:2.5/Py/API/Intro
Need stable URLs to per-release documentation
I just fixed up a URL that points to documentation, but because the blender version is embedded in the PyAPI doc urls, it's going to either break or be out of date every release. It's not clear what the best way to fix this problem is.
One crafty solution would be to write a script to serve the docs that allows the release to be a parameter in the URL instead of a a url part. The script could redirect a newer version if the docs for a specific old version number were removed. Alternatively, a user could manually remove the version parameter so the script would just show the current version of that doc. This would change a URL like:
http://www.blender.org/documentation/blender_python_api_2_57_release/bpy.types.Operator.html
into:
http://www.blender.org/documentation/blender_python_api/bpy.types.Operator.html?release=2_57
-- User:Jeske
Page linked from blender
today I've linked this page from blender code, see here: today's counter is 34,257, let's see how much this will increase :)
--mindrones 18:48, 28 November 2010 (UTC)
Meanwhile Python 3.2 is used, isn't it?
Problems in the scripts
hope it's OK to post this here ... if not, please feel free to delete... several of us copy and pasted the OpHelloWorld, the GUI drawing guide, and one of the 2.3 scrips (just to see) exactly as suggested. All of these scripts had more than one indentation error. These are *impossible* for a NOOB to fix - especially as these are clearly intended precisely *for* a NOOB. Certainly these scripts are QA'ed - or at least tested by more than one person before they get published? Thanks!
--User:GiggleFishArts 4:04, 7 August 2011 (UTC)
