Hi Brecht,<br><br> Regarding the Operator Consistency in naming - can someone give guidelines please?<br><br>Thanks,<br>Shaul<br><br><div class="gmail_quote">On Sun, Mar 22, 2009 at 1:19 PM, Brecht Van Lommel <span dir="ltr"><<a href="mailto:brecht@blender.org">brecht@blender.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Hi all,<br>
<br>
While low level work is going for the UI and python API, we can still<br>
use help, and there's still plenty of work to do in 2.5 right now! Just<br>
reply here or come on #blendercoders on <a href="http://irc.freenode.net" target="_blank">irc.freenode.net</a> to get started.<br>
The things listed here should be possible to tackle in pieces.<br>
<br>
Note: operators will still work the same after the changes that are<br>
being made, so no work is wasted.<br>
<br>
<br>
Operator Descriptions<br>
---------------------<br>
<br>
For operators, a "description" field was added. This serves as a tooltip<br>
and short description in the auto-generated API documentation. Almost<br>
none of the current operators have it.<br>
<br>
Choose a folder under source/blender/editors/. Look for _OT_ in the<br>
code, and below ot->(id)name = "..."; add ot->description = "..."; with<br>
a short one line description of what the operator does.<br>
<br>
RNA<br>
---<br>
<br>
RNA is a wrapper around Blender's data structures, used by the UI code<br>
to generate buttons, the python API, and the animation system. All data<br>
that we want to display with the new 2.5 UI code needs to become RNA<br>
wrapped.<br>
<br>
Pick an item from "Help Wanted" on this page, and I can help get you<br>
started:<br>
<a href="http://wiki.blender.org/index.php/BlenderDev/Blender2.5/RNATasks" target="_blank">http://wiki.blender.org/index.php/BlenderDev/Blender2.5/RNATasks</a><br>
<br>
Menus<br>
-----<br>
<br>
There is a new clean API for defining menu items in 2.5, to directly<br>
call operators or add RNA properties in the menus. We may move defining<br>
menus to python, but moving over menus to this system in C already will<br>
make such work trivial, and already test operators and RNA properties to<br>
work well for it.<br>
<br>
In source/blender/editors/, choose a module and look in the *_header.c<br>
file. uiDefIconTextBut is the old system, and uiMenuItem the new one. If<br>
sufficient operators and RNA properties are already defined for the<br>
corresponding tools, porting should be easy. Items not available yet can<br>
be uncommented.<br>
<br>
Operator Consistency<br>
--------------------<br>
<br>
Operators currently have inconsistent names and properties. Things like<br>
(de)select all, hide/unhide, select linked, select inverse, mouse<br>
select, .. are shared by many spaces, so they should also be consistent.<br>
Further, naming and properties have small differences in style. It would<br>
be useful for each of those types of operators to compare the different<br>
versions and make them consistent.<br>
<br>
Check this mail and replies to it for decisions on standards, which<br>
should become used for all operators:<br>
<a href="http://lists.blender.org/pipermail/bf-taskforce25/2009-February/000328.html" target="_blank">http://lists.blender.org/pipermail/bf-taskforce25/2009-February/000328.html</a><br>
<br>
More Operators<br>
--------------<br>
<br>
If you have some proficiency in the code, there are still tools that<br>
need to become operators in 2.5. For example object/object_edit.c still<br>
has plenty of code that is not operatorized yet. This requires quite<br>
good understanding of the code though, we can't guide you through this<br>
step by step.<br>
<br>
<br>
Thanks,<br>
Brecht<br>
<br>
<br>
_______________________________________________<br>
Bf-taskforce25 mailing list<br>
<a href="mailto:Bf-taskforce25@blender.org">Bf-taskforce25@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-taskforce25" target="_blank">http://lists.blender.org/mailman/listinfo/bf-taskforce25</a><br>
</blockquote></div><br>