[Bf-python] IPO modules changes (on wiki and patch tracker)

Ken Hughes khughes at pacific.edu
Sun Jun 5 22:27:18 CEST 2005


Ken Hughes wrote:
> Stephen Swaney wrote:
> 
>> Ken Hughes wrote:
>>
>>> OK, now that 2.37 is finally released, and everyone's looking for
>>> something else to do, I'd like some comments and feedback on the
>>> new IPO proposals I've been working on.  I've posted a lot of ideas
>>> on the wiki (look under "Design and Discussion..." -> "IPO Module").
>>
>> Finally was able to get into the wiki.  Added a couple brief comments.
>> In general, I like the way this is going!
>>
> 
> Thanks for the feedback; added some responses to the wiki.  I'm going
> to makes some patches for api2_2/MTex.c for accessing tex channels
> through there and then post a patch for people to try.  I'll also add
> some more of my thoughts/observations on Curves and Ipos.

I've put more comments on the wiki (should have waited until I thought
more about this), but just a patch to api2_2/MTex.c will suffice; the
only way I can think of doing implementing "myMaterial.texture[0].ipo"
is with a new IPO type (or fake IPO wrapper) "MTex" and would involve
many more changes than the four new Ipo and Ipocurve methods I'd suggested.
Of course, since the issue is ease-of-use and intuitive representation
to the Python users, if an "MTex" IPO type is the way to go I can code
up a demo.

Ken



More information about the Bf-python mailing list