[Bf-taskforce25] Editmesh accessor functions

[Shaul Kedem]

won't conversion back and forth will slow blender?

On Mon, Mar 16, 2009 at 7:38 PM, joe <joeedh at gmail.com> wrote:
> Yeah.  Or well not necassarily *in* 2.5, but whenever bmesh integrated
> into the main development branch.
>
> On Mon, Mar 16, 2009 at 4:01 PM, Shaul Kedem <shaul.kedem at gmail.com> wrote:
>> Joe,
>>  From what you wrote, it sounds like you want both editmesh and bmesh
>> structures to reside in 2.5, is that true?
>>
>> Shaul
>>
>> On Mon, Mar 16, 2009 at 11:51 AM, joe <joeedh at gmail.com> wrote:
>>> For bmesh development (to have an easier migration from editmesh) it'd
>>> be nice if certain tools that use editmesh could still work even after
>>> bmesh replaces editmesh.  Given the nonglobal design of 2.5, this
>>> shouldn't be hard; simply have uses of editmesh go through accessors
>>> functions.  These accessor functions would handle the necessary
>>> conversions for editmesh tools to work with a bmesh.
>>>
>>> It seems to me that the use of such accessor functions should be done
>>> in the 2.5 branch, then merged over to bmesh, instead of the other way
>>> around.  The 2.5 versions would obviously be fairly simple, just give
>>> access to Mesh->edit_mesh; while the ones in bmesh would do the more
>>> complex conversion necassary for editmesh operators to work.
>>>
>>> Anyway, what does everyone else think?
>>>
>>> Joe
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>