[Bf-python] shared properties?

[Willian Padovani Germano]

Hi,

> But can we implement the common ones as shared? It seems the blender
> structs (quite intentionally) start with an ID struct.
Yes, ID is a fundamental Blender struct.

> The difference is
> we'd have a header file declaring these methods ([sg]etName to begin
> with) and a macro to put in the method table adding the references.
I'm not against restructuring, but I guess this is really not the moment.
We have a lot to check, document, finish and test, all modules involved.
Maybe you read on #blendercoders (Sunday meeting) that we'll try to have a
working pre-release next Sunday or so, if not, two weeks from now.  The
changes also involve moving parts of code around, use module headers for
static declarations, renaming of functions and struct members, etc, so
another change right now wouldn't help.  After we get out of this, that's
another story.

On the other hand, the current way is very simple and uniform, though
repetitive.  As I told you, one of the objectives was to have a brain-dead
implementation very easy to pick up and learn from, maybe even a good
teaching aid for Python/C use.  So I'd like to have Michel's opinion about
it, too (are you reading, Michel ?).  get/setName is such a simple, basic
part of the code that it may not be worthwhile to do them differently just
because of the Blender internal way.

--
Willian, wgermano at ig.com.br