Outliner Collection Colors #77777

Closed
opened 2020-06-11 20:53:09 +02:00 by Nathan Craddock · 17 comments

Color coded collections are a frequently requested feature in the outliner. They help in visually grouping related collections. While this is a good idea, we still don't have a clear design. There are a few issues:

  • How to display the color? The simple solution is to highlight the row, but we already have 3+ row highlight colors and adding more would be confusing. Many good ideas have been proposed:
    *https:blenderartists.org/t/outliner-layers-colors/1186538 https:*blender.community/c/rightclickselect/54fbbc/
    *https:blender.community/c/rightclickselect/WYdbbc/ https:*blender.community/c/rightclickselect/8Pdbbc/
    ** https://blender.community/c/rightclickselect/VNdbbc/

  • How should the user pick the color? Supporting 8-10 color options would most likely be sufficient. The selection would likely happen from the context menu, but at the moment there are no submenus that allow picking a fixed set of colors.


Implementation

8-12 color options (alongside no color) could be selected from the context menu. These colors can be changed in the user preferences.

Currently the outliner draws hierarchy lines for objects but not collections. We can change this to draw the lines for collections, and color the lines to show the collection color for each item inside the collection. This is useful because it will be visible even when the parent collection item is not.

We will also draw the collection icon colored, or draw a roundrect behind the collection icon.

image.png image.png

Coloring the collection would be preferred because drawing behind interferes with the active indicator. A different (filled) collection icon could make this more readable.


Long term:

  • Viewport overlay based on collection colors. This is a nice idea. One issue is that objects can be linked to multiple collections.
  • Object select by collection color
  • Outliner filter by collection color
Color coded collections are a frequently requested feature in the outliner. They help in visually grouping related collections. While this is a good idea, we still don't have a clear design. There are a few issues: * How to display the color? The simple solution is to highlight the row, but we already have 3+ row highlight colors and adding more would be confusing. Many good ideas have been proposed: **https:*blenderartists.org/t/outliner-layers-colors/1186538** https:*blender.community/c/rightclickselect/54fbbc/ **https:*blender.community/c/rightclickselect/WYdbbc/** https:*blender.community/c/rightclickselect/8Pdbbc/ ** https://blender.community/c/rightclickselect/VNdbbc/ * How should the user pick the color? Supporting 8-10 color options would most likely be sufficient. The selection would likely happen from the context menu, but at the moment there are no submenus that allow picking a fixed set of colors. --- ### Implementation 8-12 color options (alongside no color) could be selected from the context menu. These colors can be changed in the user preferences. Currently the outliner draws hierarchy lines for objects but not collections. We can change this to draw the lines for collections, and color the lines to show the collection color for each item inside the collection. This is useful because it will be visible even when the parent collection item is not. We will also draw the collection icon colored, or draw a roundrect behind the collection icon. | ![image.png](https://archive.blender.org/developer/F8664258/image.png) | ![image.png](https://archive.blender.org/developer/F8664273/image.png) | -- | -- | Coloring the collection would be preferred because drawing behind interferes with the active indicator. A different (filled) collection icon could make this more readable. --- **Long term:** * Viewport overlay based on collection colors. This is a nice idea. One issue is that objects can be linked to multiple collections. * Object select by collection color * Outliner filter by collection color
Nathan Craddock self-assigned this 2020-06-11 20:53:09 +02:00
Author
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Added subscriber: @natecraddock

Added subscriber: @natecraddock
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

My personal favorite is coloring the collection icon. I'm not sure how feasible that is, but IMO it looks very elegant.

It would be great to have that color as a shading option in the viewport too, that could be saved for later though maybe.

My personal favorite is coloring the collection icon. I'm not sure how feasible that is, but IMO it looks very elegant. It would be great to have that color as a shading option in the viewport too, that could be saved for later though maybe.

Added subscriber: @BartekMoniewski

Added subscriber: @BartekMoniewski
Nathan Craddock changed title from Outliner Collection Colors Design to Outliner Collection Colors 2020-07-04 19:46:57 +02:00
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

Personally I'd like to see the icon we use for collections be changed to one that is filled so it can be drawn in various colors better. That way we still have the option of using an outer field to indicate some other status(es).

I'd also not include the relationship lines. Not only is it hard to get many arbitrary line colors looking good on arbitrary backgrounds, but I also just hate the relationship lines anyway. I'd like to see them gone entirely (except maybe the dashed lines we use for some occasions) since we also indicate relationships with indenting. I don't think many people agree with me here, but that is my preference.

Personally I'd like to see the icon we use for collections be *changed* to one that is **filled** so it can be drawn in various colors better. That way we still have the option of using an outer field to indicate some other status(es). I'd also not include the relationship lines. Not only is it hard to get many arbitrary line colors looking good on arbitrary backgrounds, but I also just hate the relationship lines anyway. I'd like to see them gone entirely (except maybe the dashed lines we use for some occasions) since we also indicate relationships with indenting. I don't think many people agree with me here, but that is my preference.
Author
Member

Added subscribers: @WilliamReynish, @pablovazquez

Added subscribers: @WilliamReynish, @pablovazquez
Author
Member

In #77777#987846, @Harley wrote:
Personally I'd like to see the icon we use for collections be changed to one that is filled so it can be drawn in various colors better. That way we still have the option of using an outer field to indicate some other status(es).

@Harley I'm also in favor of a filled collection icon. @WilliamReynish and I had some ideas for solving the roundrect collection colors and the active status roundrect, but those failed. I'll be addressing that soon.

I'd also not include the relationship lines. Not only is it hard to get many arbitrary line colors looking good on arbitrary backgrounds, but I also just hate the relationship lines anyway. I'd like to see them gone entirely (except maybe the dashed lines we use for some occasions) since we also indicate relationships with indenting. I don't think many people agree with me here, but that is my preference.

In the screenshot above I've actually rewritten the relationship lines, here is a comparison:

ol_hierarchy_lines_comp.png

I find this simplified relationship lines to be a good balance between what we had before, and no lines at all. However, I'm also in favor of removing the lines, the outliner does use indentation to convey relations. The only downside to removing them is that they can convey the collection color when the collection is not visible. Still not critical though.

image.png

I'm curious to hear what @pablovazquez thinks here.

> In #77777#987846, @Harley wrote: > Personally I'd like to see the icon we use for collections be *changed* to one that is **filled** so it can be drawn in various colors better. That way we still have the option of using an outer field to indicate some other status(es). @Harley I'm also in favor of a filled collection icon. @WilliamReynish and I had some ideas for solving the roundrect collection colors and the active status roundrect, but those failed. I'll be addressing that soon. > I'd also not include the relationship lines. Not only is it hard to get many arbitrary line colors looking good on arbitrary backgrounds, but I also just hate the relationship lines anyway. I'd like to see them gone entirely (except maybe the dashed lines we use for some occasions) since we also indicate relationships with indenting. I don't think many people agree with me here, but that is my preference. In the screenshot above I've actually rewritten the relationship lines, here is a comparison: ![ol_hierarchy_lines_comp.png](https://archive.blender.org/developer/F8731274/ol_hierarchy_lines_comp.png) I find this simplified relationship lines to be a good balance between what we had before, and no lines at all. However, I'm also in favor of removing the lines, the outliner does use indentation to convey relations. The only downside to removing them is that they can convey the collection color when the collection is not visible. Still not critical though. ![image.png](https://archive.blender.org/developer/F8731272/image.png) I'm curious to hear what @pablovazquez thinks here.

Added subscriber: @PierreSchiller

Added subscriber: @PierreSchiller

The relationship lines are the only "map" to something that resembles anything close to a "schematic" view. Just a glance and you can make sure your dynamic 26 hair bone chain is correctly parented early in production.
Relationship lines are a savior when doing drivers on bones as well (mechanical rigging).
No need to remove them.
As for the "filled icon collection", I think it would be a distraction to have a dispair "checkbox - checked" and a similar filled collection icon off right on the side.
It works well -ergonomically- to quickly land a checkmark on the only icon that has to appear "filled" when active (the checkbox).

The relationship lines are the only "map" to something that resembles anything close to a "schematic" view. Just a glance and you can make sure your dynamic 26 hair bone chain is correctly parented early in production. Relationship lines are a savior when doing drivers on bones as well (mechanical rigging). No need to remove them. As for the "filled icon collection", I think it would be a distraction to have a dispair "checkbox - checked" and a similar filled collection icon off right on the side. It works well -ergonomically- to quickly land a checkmark on the only icon that has to appear "filled" when active (the checkbox).

Added subscriber: @Zuorion-4

Added subscriber: @Zuorion-4
Author
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Member

Added subscriber: @kostex

Added subscriber: @kostex
Member

please check your additions against the light theme..
I've tried to get your attention here already:
https://developer.blender.org/rB452a1c7b38383fd3f51532c429912677864e4a33

please check your additions against the light theme.. I've tried to get your attention here already: https://developer.blender.org/rB452a1c7b38383fd3f51532c429912677864e4a33

Added subscriber: @Diogo_Valadares

Added subscriber: @Diogo_Valadares

I don't know if I can comment it here but wouldn't it be better if instead of 8 fixed colors the user could select the color in a color wheel? and I don't know if this is because of my theme but the color 7 is the same as "no color" by default

I don't know if I can comment it here but wouldn't it be better if instead of 8 fixed colors the user could select the color in a color wheel? and I don't know if this is because of my theme but the color 7 is the same as "no color" by default
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#77777
No description provided.