WIP: UI: add Space Presets #111068

Draft
Jacques Lucke wants to merge 14 commits from JacquesLucke/blender:space-presets-testing into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
Member

This patch adds the ability to store multiple editor configurations in the same area explicitly. Areas already store multiple spaces/editors so that they are not reset when switching the editor type. However, this has the limitation that one can store at most one configuration per editor type.

The need for a more general solution came up in a recent discussion about baking. The main use case we talked about is to be able to quickly switch between different configured outliner views. For example, there can be one outliner configuration to view all lights, another to view the full scene and one to see all the baked data (once that is implemented). For that use-case it is usually not necessary to have multiple outliners visible at the same time.

space_preset_example.gif

The main challenges here are:

  • What should this be called? The term "space preset" is basically just a left-over from when I started working on this. It's not really a preset anymore.
  • How to make the UI very compact so that it can fulfill its purpose of staying visible to make it fast to switch?
This patch adds the ability to store multiple editor configurations in the same area explicitly. Areas already store multiple spaces/editors so that they are not reset when switching the editor type. However, this has the limitation that one can store at most one configuration per editor type. The need for a more general solution came up in a [recent discussion](https://devtalk.blender.org/t/2023-08-01-nodes-physics-module-meeting/30528) about baking. The main use case we talked about is to be able to quickly switch between different configured outliner views. For example, there can be one outliner configuration to view all lights, another to view the full scene and one to see all the baked data (once that is implemented). For that use-case it is usually not necessary to have multiple outliners visible at the same time. ![space_preset_example.gif](/attachments/8f137e10-11b6-445e-844f-d4ede74a502c) The main challenges here are: * What should this be called? The term "space preset" is basically just a left-over from when I started working on this. It's not really a preset anymore. * How to make the UI very compact so that it can fulfill its purpose of staying visible to make it fast to switch?
Jacques Lucke added 13 commits 2023-08-12 14:16:16 +02:00
Jacques Lucke changed title from WIP: UI: add Space Presets to WIP: UI: add Space Presets 2023-08-12 14:28:05 +02:00
Author
Member

@blender-bot package

@blender-bot package
Member

Package build started. Download here when ready.

Package build started. [Download here](https://builder.blender.org/download/patch/PR111068) when ready.
Jacques Lucke added 1 commit 2023-08-15 14:37:48 +02:00
First-time contributor

Wow, I never even knew how badly I need this! Perhaps my envisioned use case is a bit different.

Any chance to make these so called presets "global" and make them available across different Workspaces?

This could help mitigate another already discussed issue of editors "changing" across workspaces. Like 3D Views having different points of view, different shading settings, or different visibility states when switching between workspaces, which can be disorienting.

If these presets could be made available to all 3D View areas regardless of workspaces, they could help port my tailor-made 3D view setup (including snapping options, overlays, shading settings, gizmo visibility, pivots, toolbars, etc) to other editors, which is currently impossible and quite tedious to replicate across many workspaces.

I'll look into the test build and see if I can come up with any constructive feedback about the UI.

Thanks for working on this.

Wow, I never even knew how badly I need this! Perhaps my envisioned use case is a bit different. Any chance to make these so called presets "global" and make them available across different Workspaces? This could help mitigate another already discussed issue of editors "changing" across workspaces. Like 3D Views having different points of view, different shading settings, or different visibility states when switching between workspaces, which can be disorienting. If these presets could be made available to all 3D View areas regardless of workspaces, they could help port my tailor-made 3D view setup (including snapping options, overlays, shading settings, gizmo visibility, pivots, toolbars, etc) to other editors, which is currently impossible and quite tedious to replicate across many workspaces. I'll look into the test build and see if I can come up with any constructive feedback about the UI. Thanks for working on this.
First-time contributor

Maybe this could fit into a popover similar to the one used for custom transform orientations, with a basic interface for adding, removing, and managing editor "States", the list would provide quick toggling. It place it right next to the editor selector, since they are intimately related.

Blender_EditorPresetsMockup_01.png

I think this would suffice for quick toggling, but in your mockup there this concept of "tabs" that one can use to quickly toggle.
If multiple are selected from within the popover they would show up in the toolbar for quicker toggling.

EditorPresets_Mockup.gif

In this mockup there are custom icons from default icons, but that seems overkill. It would require an interface to assign an icon, and I think that would be disproportionate amount of management for such a niche feature.

Maybe simple dots like in your mockup, or something akin to the old bit layers selector would suffice.

Bit Layers

Maybe this could fit into a popover similar to the one used for custom transform orientations, with a basic interface for adding, removing, and managing editor "States", the list would provide quick toggling. It place it right next to the editor selector, since they are intimately related. ![Blender_EditorPresetsMockup_01.png](/attachments/217914ad-373d-4290-b5d3-afb69e55ed7c) I think this would suffice for quick toggling, but in your mockup there this concept of "tabs" that one can use to quickly toggle. If multiple are selected from within the popover they would show up in the toolbar for quicker toggling. ![EditorPresets_Mockup.gif](/attachments/6077c6e2-7a53-44a1-bb78-4f5bee475c32) In this mockup there are custom icons from default icons, but that seems overkill. It would require an interface to assign an icon, and I think that would be disproportionate amount of management for such a niche feature. Maybe simple dots like in your mockup, or something akin to the old bit layers selector would suffice. ![Bit Layers](https://docs.blender.org/manual/en/latest/_images/animation_armatures_properties_skeleton_panel.png)
This pull request has changes conflicting with the target branch.
  • source/blender/blenkernel/BKE_screen.h
  • source/blender/editors/interface/interface_templates.cc
  • source/blender/editors/screen/screen_ops.cc

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u space-presets-testing:JacquesLucke-space-presets-testing
git checkout JacquesLucke-space-presets-testing
Sign in to join this conversation.
No reviewers
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
3 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#111068
No description provided.