[Bf-taskforce25] Layout Files Code-Guidelines

[Campbell Barton]

+1

- In 2.4 we had nothing so strict like this but I'm happy to habe this in 2.5.
- Does this apply to ALL scripts with UI's in blender- eg, render
engine integration (should do I think, but could state in wiki)
- MATERIAL_PT_material - this is more a C standard. the python string
should be "material.material", but for now I think its ok to keep
until the conversion is supported as it is with operators.


On Sat, Aug 1, 2009 at 11:47 AM, Thomas Dinges<dingto at gmx.de> wrote:
> Hi everybody,
> Python Layout files are new in 2.5. I think they have to be consistent
> and easy to understand (code wise).
> These files are also very interesting for the end user, they give them
> the power to tweak their interface to their own needs.
> I wrote some code guidelines for these files:
> http://wiki.blender.org/index.php/Dev:Py/Blender2.5/Layouts/Guidelines
>
> Escpeceally the assignement names are important. We still have lot of
> different ones of them. Try to keep them consistent makes it easier for
> coders and users.
>
> Please read the guidelines and give me feedback on them. It would be
> great to approve them to make them official.
>
> Regards,
>
> Thomas
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>



-- 
- Campbell