[Bf-python] tp_getset update

[Stephen Swaney]

On Mon, Aug 15, 2005 at 10:08:16AM -0700, Ken Hughes wrote:
> 
> * I've noted two modules where it would make sense to implement sequence 
> or index operators; Metaball.c and Lattice.c.  For example: 
> Lattice.getPoint(index), Lattice.setPoint(index,position) and 
> Lattice.latSize.  These could be replaced with built-in operators and 
> attributes: Lattice.point[i] and len(Lattice.points)

In general,  access to sequence data in types via a FORTRAN-like
interface can be replaced with the pythonic sequence protocol.
I will make a note on the wiki.

Implementing iterators is probably not a bad idea either.
Back in the olden days, we were not quite as clever as we are now!

> * Any reason for Effect.c and Particle.c to be separate anymore?  I 
> think I missed some discussion, but Wave.c is gone and don't recall 
> seeing a Build.c ever, so there seems to be just one effect now. 
> Doesn't seem to make sense to have a separate BPy Particle object, 
> especially the way it's implemented -- as a pseudo derived class.

Sounds like time for a little design document!

-- 
Stephen Swaney			
sswaney at centurytel.net