[Bf-taskforce25] Context/Operator: alternative

[joe]

It may be possible to write a py api, in python and on top of the
C-defined API, that could try to mitigate the limitations of the
current operator spec as much as possible.

For that matter, if we can we do need a wrapper API that'd be as close
to compatible with the old py API as possible.  I suppose if we had
that, it'd be good enough for now, and wouldn't be too limiting (if
perhaps slow).

Joe

2009/3/19 Shaul Kedem <shaul.kedem at gmail.com>:
> guys, let's pace ourselves, it's nice to have new ideas but the current
> operators arch took half a year to accomplish, I agree with ton that the
> goal should be to get a fully working blender out of the door and then work
> on refinements, because frankly, no one knows exactly how good or bad the
> python API will be, and there are other things in the pipeline (render API,
> durian, gsoc projects, siggraph, etc.) that a blender 2.5 will be a very
> good thing to have in place for.
>
> On Thu, Mar 19, 2009 at 7:41 PM, Michael Fox <mfoxdogg at gmail.com> wrote:
>>
>> please keep in mind that my last mail was a rough draft of my thoughts,
>> i may have missed somthing but i hope it will help point in the right
>> direction
>>
>> _______________________________________________
>> Bf-taskforce25 mailing list
>> Bf-taskforce25 at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>
>
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>
>