In the application i am looking at, you can create objects of different types by a corresponding context menu. Which entry (or which of these keywords) will be used is depending on the context of the action. There is always a maximum of one keyword possible at a time, so the user will never be in a situation whether he should use "new" or "insert" as there will be only the corresponding action displayed. Currently possible actions any user can perform are:
- New foo
- Add bar
- Insert foobar
What they do:
- "New" creates an object new from scratch, like a new text file.
- "Add" creates an object from a template that can be configured after; it can often be used without further actions right after the add.
- "Insert" creates an object that is quite primitive, such as a clean canvas, that can be configured after. The object created usually behaves like a dummy or a template right after creation, it has no use unless it gets "filled with life" by the user.
Is it problematic to give similar actions like these different names like I do? Does any of the naming conflict with general conventions?