Consolidate Theme Options #45352
Labels
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
15 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#45352
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As @JulianEisel indicated on Twitter, there are 756 color options and 119 other options for themes.
The main issue is that each editor has their own set of theme options, which are all shared, in that these options apply to each editor but are set independent. Of the 17 editors, each has the same 17 standard color settings, a total of 289 - it could be 17. For example,
Unique theme needs per editor should be the exception, not the rule.
Proposal
Consolidate all common editor options into a single, generic set. This includes:
Theme Space Settings
andTheme Panel Color
primarily.The best place for these to go is probably the
User Interface
category.Changed status to: 'Open'
Added subscribers: @JonathanWilliamson, @JulianEisel
Added subscriber: @Januz
Although this proposal gets a BIG +1 from me, I think it's nice to keep the possibility to set the mentioned theme options per editor (e.g. because I heard people color each editor different for teaching).
So I'd extend this proposal by adding a per editor option "Use Global Options" (or similar named) for
Theme Space Settings
andTheme Panel Color
. It would allow one to use separate colors for this editor when unchecked. When checked we could simply hide these settings.This way we would allow setting these options per editor, while keeping it being the exception.
Setting priority to normal although I think it's actually pretty high priority.
Added subscriber: @TARDISMaker-2
Added subscriber: @WarrenBahler
I fully support this, the pain of copying colors to each and every editor while fine tuning a theme is approaching the ridiculous.I think this is a great example of where too much of a good thing (flexibility) , becomes flawed in practice.
Added subscriber: @Blendify
Added subscriber: @michaelknubben
When 'Global Options' is set to false, do we revert to the current situation where everything has to be adjusted separately? Because if so, a more elegant solution may be for the user to manually enable sections.
So you can have one section to control global colours, and the user can add an 'Properties panel' override, which enables/unhides that section.
This way the user can adjust only one part separately,while leaving the rest of the UI under global control.
Added subscriber: @PierreSchiller
Hi, I don´t know exacly where this post should go, I apologyze in advance. I read somewhere there´s a need to show (invite) the user to start using blender by placing a button so the user will know the splash screen will go away and he/she will start working on blender.
Consecutively there´s a need to invite the novice user to "try" any of the simplified blender workspaces. So I figured the features should be right up front inviting the user along with a short description of what the workspace does in text.
The huge large image to the left should be a featured artwork but there´s an option to left click on it and it will launch a URL with official Blender galleries. Since many of the nouvelle artists DON´T KNOW what Blender is capable of creating, the gallery should be a strong point to emphasize inspiration for the new commers of Blender. (Think of Artstation for inspiration). The url should point to blender.org/gallery or something similar.
Interaction and Keymapping presets are resolved immediately after identifying blender´s version. This is unmistakable to touch since each user with previous experience on another 3d package could feel right at home.
So, yeah. This is my splash screen proposal. I wish I could find the correct category to keep on posting things about the interface UI, Icons and themes. Thanks.
@PierreSchiller sorry but this is not the right place for these proposals. You can create a WIKI page if you with the proposal. Design Tasks here should only be created by the UI Team or a developer after it's been discussed and approved.
The WIKI is here: https://wiki.blender.org/index.php/Dev:Ref/Proposals/UI
Added subscriber: @DuarteRamos
Added subscriber: @nokipaike
holy shit !
:)
has the situation remained the same?
Added subscriber: @FDesimpel
I was tweaking the light theme a bit a while back, and indeed, i was also thinking, why not have a global setting, and then you can override it per editor or even per setting in an overridden section.
So there could be a 'theme space' etc section in user interface as default.
Also, since per editor settings for theme space and such are in their own dropdown category, could the 'object colors' per editor also be in a dropdown please, less scrolling when just editing the space colors.
There seem to be a lot of inconsistencies in button type used in headers etc too.
More settings, more control over theme would be nice, also in sizes...
Added subscriber: @Uendel
Added subscriber: @PaulCoops
Added subscriber: @Aeraglyx
Added subscriber: @dominikfill
Is this still something to be considered?