Rename: Std_ClippingPlane to Std_ToggleClipPlane

[vocx]

is everyone just going to not notice the "toggle" word in the command strings being utterly wrong ? The command opens a task where you can toggle some clipping planes, but in itself does not toggle anything...

Of course, however, that would mean changing the name of the C++ classes and command name. This could be done at another time. Right now we want to match the code to the wiki. This renaming is done so that the Std_WhatsThis system works correctly when launching the documentation system of FreeCAD.

My personal belief is that a command name should be an "object" (noun) as opposed to an "action" (verb).

So, it should be name Std_ClippingPlane, and not Std_ToggleClippingPlane; it should be Std_Primitives and not Std_CreatePrimitives, etc. This is better when talking about the result of those commands and when writing documentation.

[DeepSOIC]

My personal belief is that a command name should be an "object" (noun) as opposed to an "action" (verb).

My opinion is exact opposite: a command IS an action, i.e. it sorta IS a verb, and should be named accordingly: with a verb in it. I don't mind the current situation too much, though, where many commands are named after the objects they create, and thus the objects and the commands share their wiki pages.

[vocx]

...many commands are named after the objects they create, and thus the objects and the commands share their wiki pages.

But then how would you document it? "The Std_CreatePlane command creates a Plane. See the documentation of Plane."

The action would have barely any documentation; it would just point to the object. So, I think it makes more sense to document objects.