[Bf-python] vertex groups

[Willian Padovani Germano]

From: <models at paposo.com>
(...)
> My choice is D:
> > - assignVertIndicesToGroup

Ok, we'll update them.

BTW: it just occurred to me that it looks like bpython methods favor 'Vert'
instead of 'Vertex', from what I remember.  If so, we should try to follow
that in other new additions, too.

>     I think it's better to have it in object, because you wouldn't link
the
> mesh data to the object until your finished with the mesh and the mVerts
are
> constructed.  There are also no added calls to find the object because you
> would be calling from the object.

Yes, there's one subtle but strongly rooted aspect of Blender Ton told me
about, when I was trying to convince him to accept a trivial change in a
button, that would make Python know when a user wanted to use vcolors or not
(requested by jms).  Blender's buttons are a direct reading of the current
state of the database.

BPython also doesn't hide totally the internal ways (object + object data,
for example), so it's not really bad to have vgroup functions in the Object.

I haven't tested, but in Blender a same mesh used by more than one object
should be able to have different vertex groups in each object, since that's
where the vgroup info is ... that's a feature, that maybe some users want.

So let's keep the vgroup functions with Object also in bpython.

> P.s. can someone explain what a DispList is to me?

A display list.  It's a "compiled" sequence of OpenGL commands (there are
strict rules at to which commands can be stored in a display list), that you
can store and reuse.  An old speed-up.  For example, in Blender it is used
to store a mesh "ready for displaying": the verts are already transformed
(multiplied by the transform matrices and deformed by the armatures), etc.
If you can simply reuse this list (aka the mesh hasn't changed), you don't
have to recalculate everything, just perform the last steps to put it on the
screen.

--
Willian, wgermano at ig.com.br