Consolidate Theme Options #45352

Open
opened 8 years ago by JonathanWilliamson · 23 comments

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 and Theme Panel Color primarily.

The best place for these to go is probably the User Interface category.

As @JulianEisel indicated on [Twitter](https://twitter.com/Severin_b3d/status/616371933333073921), 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` and `Theme Panel Color` primarily. The best place for these to go is probably the `User Interface` category.

Changed status to: 'Open'

Changed status to: 'Open'
JulianEisel was assigned by JonathanWilliamson 8 years ago

Added subscribers: @JonathanWilliamson, @JulianEisel

Added subscribers: @JonathanWilliamson, @JulianEisel
Januz commented 8 years ago

Added subscriber: @Januz

Added subscriber: @Januz
Collaborator

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 and Theme 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.

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` and `Theme 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**.
Collaborator

Setting priority to normal although I think it's actually pretty high priority.

Setting priority to normal although I think it's actually pretty high priority.

Added subscriber: @TARDISMaker-2

Added subscriber: @TARDISMaker-2

Added subscriber: @WarrenBahler

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.

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.
Collaborator

Added subscriber: @Blendify

Added subscriber: @Blendify

Added subscriber: @michaelknubben

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.

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

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.

Blender_proposal_UI_Splash_PierreSchiller.jpg

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.

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. ![Blender_proposal_UI_Splash_PierreSchiller.jpg](https://archive.blender.org/developer/F1074091/Blender_proposal_UI_Splash_PierreSchiller.jpg) 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

@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: @DuarteRamos

Added subscriber: @nokipaike

Added subscriber: @nokipaike

756 color options and 119 other options for themes.

holy shit !
:)
has the situation remained the same?

> 756 color options and 119 other options for themes. holy shit ***!*** :) has the situation remained the same?

Added subscriber: @FDesimpel

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...

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...
Uendel commented 3 years ago

Added subscriber: @Uendel

Added subscriber: @Uendel

Added subscriber: @PaulCoops

Added subscriber: @PaulCoops

Added subscriber: @Aeraglyx

Added subscriber: @Aeraglyx

Added subscriber: @dominikfill

Added subscriber: @dominikfill
lichtwerk removed the
legacy module/User Interface
label 7 hours ago
lichtwerk removed the
Interest/User Interface
label 7 hours ago
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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…
There is no content yet.