| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
addon next).
|
|
|
|
READ THIS TO AVOID A LOT OF WORK!
New way of linking to tracker pages: just use the parameter "aid" (artifact ID),
to avoid a lot of manual updates later in wiki and svn.
Example:
=========
OLD WAY TO LINK TO TRACKER
-----------------------------
Complete url of a script in Upload
http://projects.blender.org/tracker/index.php?func=detail&aid=25349&group_id=153&atid=467
If we move this in contrib this url will become
http://projects.blender.org/tracker/index.php?func=detail&aid=25349&group_id=153&atid=468
467 becomes 468, so we have to update this in wiki page.
Later on, when this moves into Trunk, the url will become
http://projects.blender.org/tracker/index.php?func=detail&aid=25349&group_id=153&atid=469
468 becomes 469, so we have to update the url in wiki page and svn.
Annoying!
NEW WAY TO LINK TO TRACKER
-----------------------------
Best way to link to tracker page is using:
http://projects.blender.org/tracker/index.php?func=detail&aid=25349
Use "func=detail"
Use "aid" (which is the "artifact ID")
DON'T use "group_id" (which is the project ID, bf-extensions is project 153)
DON'T use "atid" (which is the "artifacts tracker ID")
Like this, the url is unique, and we will avoid to update wiki pages and svn after moving pages
[[Split portion of a mixed commit.]]
|
|
can be called from console without error.
|
|
even more cleanup
|
|
|
|
adding with entering into edit mode. no show stopper. but needs to be investigated
|
|
rev: 32411
|
|
supported in the api.
|
|
|
|
scripts tested as working
|
|
- fixed the previously mentioned bug
- somehow setting the Curve.offset screwed things up
- simply removed it, wasn't used anyway
- updated api revision number
|
|
bf-extensions/trunk/py/scripts
by Filiciss Muhgue (filiciss). Thanks a lot!
Part 2: Extensions
|
|
- minor cleanup
- there seems to be a bug with the scale factor, maybe due to all the recent api changes? The output is different than a few weeks ago, although still functional.
- has to be investigated.
|
|
- comforming after my commit in bf-blender:
- removed the categories from addons names
- made 'version' a tuple of integers
- added 'api' field
- formatted wiki and trackers pages and added where needed (empty pages are yet to be written by the authors though)
- more conforming:
- 1 tab = 4 spaces
- please check everything is fine in case I made some gross mistake
|
|
- fixes for api changes
|
|
|
|
|
|
|
|
|
|
- cleanup: removed unnecessary options lists
|
|
|
|
- mesh_surface_sketch.py
- render_renderfarmfi.py
- space_view3d_align_tools.py
- object_cloud_gen.py
also move bl_addon_info to the top for faster parsing.
|
|
These scritps still need changes related to parent classes
- mesh_surface_sketch.py
- render_renderfarmfi.py
- space_view3d_align_tools.py
- object_cloud_gen.py
|
|
Fixed some descriptions and locations
|
|
|
|
- every script is now (2,5,3)
- added warning field in bl_addon_info so every dev knows about this: when "warning" field is not empty, a warning icon appears and text alerts
users about a buggy script (this is used during development, released scripts should must have this empty of course)
- formatted scripts info like this
- GPL
- docstring
- bl_addon_info
- imports
so that the actual script starts after the bl_addon_info dict
- removed old 2.4x cruft like __url__, __bpydoc__, __author__ etc, not needed anymore (when the case integrated info with bl_addon_info and in
case of one email meta just put it in the GPL)
- next commits I plan to do contrib scripts and conform io scripts naming
|
|
|
|
- testing the new button "report a bug",
see commit from dingto here http://lists.blender.org/pipermail/bf-blender-cvs/2010-May/028285.html
|
|
|
|
|
|
|
|
- some better tool tips
- rework of UI
- defaults to options for torus knots only now
- button to show additional parameters
|
|
|
|
not really adding anything
|
|
script introduced to trunk.
the script makes use of mfoxdoggs revision 28923.
the script shows up in the add/curve menu.
|
