Workspaces: Sharing of workspaces #54628

Closed
opened 2018-04-16 11:12:29 +02:00 by Brecht Van Lommel · 8 comments

We need a good mechanism and UI to save / load / share workspaces.

We need a good mechanism and UI to save / load / share workspaces.
Author
Owner

Added subscriber: @brecht

Added subscriber: @brecht
Brecht Van Lommel changed title from Workspaces: sharing of workspaces to Workspaces: Sharing of workspaces 2018-04-16 11:15:04 +02:00
Member

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez
Member

Currently Workspaces are Datablocks, so I guess the save/load part is done already?
Screenshot from 2018-04-17 15-16-29.png

In this context, is Workspace considered an asset? If so then this could be part of the Asset Manager design.

Currently Workspaces are Datablocks, so I guess the save/load part is done already? ![Screenshot from 2018-04-17 15-16-29.png](https://archive.blender.org/developer/F2768358/Screenshot_from_2018-04-17_15-16-29.png) In this context, is Workspace considered an asset? If so then this could be part of the Asset Manager design.
Author
Owner

In 2.8 we have workspaces in the startup.blend and other regular .blend files, and in a new workspaces.blend. When clicking the (+) icon next to the workspaces in the new topbar, you get a list of workspaces in workspaces.blend, and you can then add one of them to the current .blend. There is currently no way to save a workspaces to the workspaces.blend from the same menu. It's a .blend file so users could open it and add some workspaces in there, but it's in a hidden config folder so users won't find it easily.

In a way this is like a mini asset management for workspaces, and if you can save workspaces to/from a general asset database it seems redundant. So I guess that's the first question to resolve, do we improve the current workspaces.blend mechanism or do we fold it into the asset management system?

In 2.8 we have workspaces in the `startup.blend` and other regular .blend files, and in a new `workspaces.blend`. When clicking the (+) icon next to the workspaces in the new topbar, you get a list of workspaces in `workspaces.blend`, and you can then add one of them to the current .blend. There is currently no way to save a workspaces to the `workspaces.blend` from the same menu. It's a .blend file so users could open it and add some workspaces in there, but it's in a hidden config folder so users won't find it easily. In a way this is like a mini asset management for workspaces, and if you can save workspaces to/from a general asset database it seems redundant. So I guess that's the first question to resolve, do we improve the current `workspaces.blend` mechanism or do we fold it into the asset management system?
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Managing the workspaces of the workspaces.blend is actually something I hoped to allow through the new Blender settings design, see #54115.

Managing the workspaces of the `workspaces.blend` is actually something I hoped to allow through the new Blender settings design, see #54115.
Author
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Brecht Van Lommel self-assigned this 2018-09-20 15:30:55 +02:00
Author
Owner

This is handled now in Blender 2.8, without a separate workspaces.blend. Instead users can directly append workspaces from the builtin and user defined startup.blend, as well as any application templates.

This is handled now in Blender 2.8, without a separate workspaces.blend. Instead users can directly append workspaces from the builtin and user defined startup.blend, as well as any application templates.
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
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#54628
No description provided.