[Bf-taskforce25] 2.5: how to help out right now

Shaul Kedem shaul.kedem at gmail.com
Mon Apr 13 01:22:05 CEST 2009


Hi,
 I went through all of the appearances of "struct wmOperatorType *ot"
and changed the naming according to the convention, hopefully this
will hold into the future,

Regards,
Shaul

On Mon, Mar 23, 2009 at 7:39 AM, Brecht Van Lommel <brecht at blender.org> wrote:
> Hi Shaul,
>
> I made a summary of the discussion here:
> http://wiki.blender.org/index.php/BlenderDev/Blender2.5/Operators#Conventions
>
> Brecht.
>
> On Sun, 2009-03-22 at 17:10 -0400, Shaul Kedem wrote:
>> Hi Brecht,
>>
>>  Regarding the Operator Consistency in naming - can someone give
>> guidelines please?
>>
>> Thanks,
>> Shaul
>>
>> On Sun, Mar 22, 2009 at 1:19 PM, Brecht Van Lommel
>> <brecht at blender.org> wrote:
>
>>         Operator Consistency
>>         --------------------
>>
>>         Operators currently have inconsistent names and properties.
>>         Things like
>>         (de)select all, hide/unhide, select linked, select inverse,
>>         mouse
>>         select, .. are shared by many spaces, so they should also be
>>         consistent.
>>         Further, naming and properties have small differences in
>>         style. It would
>>         be useful for each of those types of operators to compare the
>>         different
>>         versions and make them consistent.
>>
>>         Check this mail and replies to it for decisions on standards,
>>         which
>>         should become used for all operators:
>>         http://lists.blender.org/pipermail/bf-taskforce25/2009-February/000328.html
>
>
>
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>


More information about the Bf-taskforce25 mailing list