@monster: thanks for the advice
but referring to the python API…
the python API is (to put it simply) a nightmare and nothing more than a hassle to try to follow. (it should be burned)
(I’ve already puked (multiple times) at the fact the blender API follows it’s structure…)
2.49’s downloadable (<3) API helped me out ALOT better than the current API
(especially the function/class tree browser (<3 <3) )
I am experienced with python2.7 (I can’t call myself an expert though), especially in the PyOpenGL area.
(PyOpenGL runs slower on Python3 (no intent to fix, as nothing needs to be “fixed”), so I stick with 2.7)
perhapse you guys should take some tips from my project’s functions:
http://tcll5850.proboards.com/thread/182/layout (note: highly unfinished)
my project makes model importing more like OpenGL’s automated state engine (no ‘.’ operator), so it’s ALOT easier to follow and script for.
(scripting for blender has become even more of a nightmare since 24x, so I’ve developed this to take it’s place)
^ only applies to model I/O
anyways, my point is the structure-tree…
this is basically my project’s docs which contains references and simple explainations as to how the function works.
(it’s meant mainly to help noobs but to also help pros to keep them from misunderstanding things)
now doesn’t this seem alot better than Blender’s API?
(no “search” needed, just click the function you want and get it with anything it needs on the fly.)
something for me alone, if you guys want to copy:
I’ve made my docs on my forum specifically for user feedback on my functions.
I believe a convenient way of user feedback is an added benefit to aid development.
so why not start with the functions everyone will be using