= 2.8: Optimizing Workflows =
== Motivation ==
The main goal of the Blender 2.8 project is improving workflow support, this invokes optimizing workflows.
A common way to optimize workflows is using task oriented environments. Such a task oriented environment helps increasing efficiency by facilitating access to relevant tools and options, optionally while hiding irrelevant ones.
Let's consider these 3 approaches:
* **Context Sensitivity**Context sensitivity can be one solution to optimized workflows, however software history tells us that context sensitivity almost never works in a user satisfying way. More reliable are modes, which can be easily changed on user's desire. We simply put it into the user's hands to select the right state for the task he's trying to accomplish, he's smarter than Blender anyway ;)
So task oriented modes - "Workflow Modes" - appear to be the way to go.
A third alternative would be task oriented presets,
== How to integrate Workflow modes? ==
Good question! This is the part that's still totally fuzzy.
* Will they be more like current object modes, screen layouts or like presets? (The last two are not really modes, )
== Eliminating Mode Errors ==
Modes are of course not entirely error-free, in fact they can easily become dangerous if not designed/implemented thoughtfully. Mode errors appear when the user tries to invoke a function by an action (pressing shortcut, clicking button, ...), but a different function is invoked, or even nothing at all, because of the different behavior of the current mode.