[Bf-python] curve module and surfaces

[Fernando Serboncini]

On Mon, 2004-06-14 at 13:27, Stephen Swaney wrote:

> Perhaps I misunderstand when you say 'the first row of points'.
> Both getNumPoints and getControlPoints have an int argument
> to specify particular curve.

I meant only the U component of a UxV surface. Not multiple curves.

> Our goal with the bpy api was to provide a programmatic interface
> to blender functionality.  Since blender makes a distinction between
> Curves and Surfaces, we should also.

Ok, got your point.

> A future blender3 is a different case and I would be quite
> prepared to argue there that Curves and Surfaces should be
> unified.  But that is Then and not Now.

Agreed.

> Undeniably, there will be reuse and code sharing internally
> between bpy Curves and Surfaces.  I can already see it in the 
> Nurb module I created to add iterators for Curves.  But this 
> does not mean the external interface should be the same.

I would gladly take the latest curve module and create a first version
of a surface module. What do you think?

> This may have passed your test cases but I am looking at
> an example in the debugger of a single Curve with two 
> curves: a bezier and a nurb.
> In one case, pntsv is 1, in the other it is 0.

That's what happened to me: I've created a bezier curve and it worked
fine. Haven't tested with a bezier, so you're probably right.

[]s
Fernando Serboncini
http://fserb.com.br