On Sep 8, 10:16 am, "Edward K. Ream" <[email protected]> wrote:
> - The "Creating the Blender Add On" chapter is written as if the > script writer did not have access to proper API documentation. We are getting someplace. About 99% of Jaworski is cruft. Here is the gist, with the cruft removed. >From page 43: A discussion of bpy.data, bpy.context, bpy.ops and bpy.types. The main thing is that each Blender operator is a (subclass of) bpy.ops. For example, Jaworski is creating a new mesh operator, so we need a subclass of bpy.ops.mesh. How hard is that?? bpy.types could be called the true "front page" of the docs: http://www.blender.org/documentation/blender_python_api_2_59_2/bpy.types.html This is where the real info resides. >From page 46: A discussion of the bpy.app, bpy.path, bpy.props, mathutils, bgl and blf modules. The bgl (Blender openGL) module allows drawing directly on the Blender screen. The blf (Blender Font?) module allows drawing text. Pages 48-58 In essence, this whole discussion is a graphical way of discovering that MeshEdge objects have a bevel_weight field. http://www.blender.org/documentation/blender_python_api_2_59_2/bpy.types.MeshEdge.html But this is easily discovered from the doc: Meshes http://www.blender.org/documentation/blender_python_api_2_59_2/bpy.types.Mesh.html have an edges field whose contents are MeshEdges. Of course, having a working script is "A Good Thing" (tm), and so is the ability to convert the script to an add-on. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
