Age | Commit message (Collapse) | Author |
|
minor other edits
|
|
materials).
|
|
Note: import gimp image also would need it, but it would anyway need a good cleanup (handling of paths is ugly), so did not bothered with it for now.
|
|
|
|
|
|
*Use absolute as default size mode (dpi with BU is not that nice).
*Use default plane primitive instead of creating our own square (this way we can be sure things like verts order will always match those of default plane!), request from Christopher Barrett in tracker.
|
|
Iggy B [rexxxus] for reporting the bug).
|
|
blender code (thanks to meta-androcto for the report on IRC).
|
|
Never use a generator as enum's "items" value!
|
|
make addons blender versions consistent
|
|
(absolute, to directly specify the result height, and dpi or dpbu [dots per Blender Unit], to use image definition). Based on an idea and code from mat ali, thanks!
Also fixed correct use of overriden context (not really a bug, but printed annoying warning messages in the console).
|
|
"import.image_to_plane" to "import_image.to_plane" (import is a keyword in python...). Thanks to P. Staples in tracker!
|
|
|
|
*Mostly, makes much more intensive use of Blender's FileSelector, to only show relevant files, and allow any pict/video files when "all" is selected (previously e.g. importing mkv's was impossible!).
*Style cleaning/refactoring (esp. do not use 'self' for anythin else than a method's object, so made most func member of op class)...
|
|
finished
|
|
|
|
|
|
|
|
Remove module add_utils.py which fully duplicates functions
from trunk's object_utils.py module and switch all dependent
addons to use module from trunk.
|
|
expanding, normalizing first, 2) non-utf8 paths made the script error out, 3) paths were exported with absolute paths by default, had to remember to make them relative which was annoying.
|
|
|
|
|
|
|
|
(reported by Nathan Letwory over IRC)
|
|
|
|
Plus a few styling enhancements.
[[Split portion of a mixed commit.]]
|
|
* You only have to do layout.prop if you want 1 property, no need for row then!
* Use col, row, sub as variable names, not colsub, rowsub, row2 etc please.
* Povray Addon: Still used a lot of splits, you need no split when you only have 1 column!
|
|
|
|
|
|
to FBX.
|
|
|
|
addon next).
|
|
update_tag() tags for depsgraph update only, update() executes normal recalculation and creates edge data.
|
|
|
|
|
|
|
|
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.]]
|
|
- in wiki page urls: "File_I-O/" -> "Import-Export/"
- in categories: "Import/Export" -> "Import-Export"
- 1 tab to 4 spaces
- some tuple formatting, just to be very picky :P
|
|
the rest of the thing is recoded. Since this was like my first script this new version is much more readable and easier to debug. As a bonus there is also a new option to align the planes in a row on import to justify a version bumb. I think i tested everything and it should be bug free. Hopefully :)
|
|
|
|
|
|
supported in the api.
|
|
|
|
bf-extensions/trunk/py/scripts
by Filiciss Muhgue (filiciss). Thanks a lot!
Part 2: Extensions
|
|
should since this can now only be accessed as many bools
|
|
|
|
|
|
- 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
|
|
|
|
|