Dev talk:Ref/Proposals/UI/Tools Workflow
Hi PLyczkowski, thanks for adding your input. My understanding of the two proposals is that they are almost exactly the same, but with different wording. We've identified the same issues and both our solutions are pretty much the same too. That's nice, we are definitely on the same page :) I noticed these small differences though:
- You separate tools from operations. This is pretty much the same as what's already in Blender referred to as non-modal and modal operators. Blender doesn't really otherwise distinguish between one-off operations and more proper tools that stay active. Though it may make sense to either change the terminology or to make the distinction clearer.
- It's nice that you explain that hotkeys can stay the same. I though the same thing, but didn't write it down as clearly.
- In your proposal, you right-click to end a tool. This is akin to the spacebar in modo that you use to drop the tool when you are satisfied. I'm not sure we need this - can't the user simply switch to another tool without having to 'apply' the first tool?
- One thing I didn't read in your proposal was what to do with manipulators. I think the current situation where they are removed from the tools (and only available for Move, Rotate, Scale) is really odd. It adds UI duplication, and are usually in the way when you don't need them.
One thing that this proposal raises but doesn't address is the case where you need multiple manipulation points for a single operation. Consider the suggested "Spin" and "Bisect" manipulators - To use them properly, you would have to "touch and adjust" several of the manipulation points before the operation is applied. This means you need to add some "Apply" button, or UX equivalent thereof.
I'm not saying that's a bad thing, mind you. It could actually be very good to do things this way. Consideration should also be put into CAD-standard tools like 2-point move and 3-point scale and rotate. These allow setting up reference points, and choosing the right origin, so that the operation can be done with better accuracy. Using separate manipulators for the "origin", "reference" and "target" in such tools, along with an "apply" button, would give blender the CAD capabilities it is currently lacking.
Another thing to consider is snapping. In case where manipulators are on-screen objects which can be moved to influence (rather than perform) an action, it should be possible to snap them, either to the grid, or to other objects. They should have similar snapping options as are currently available for the 3D cursor.
-- Slugfiller 14:08, 2 January 2014 (CET)
