Talking about workspaces

[epicEaston197]

So I decided to look into workspaces today and realized that all that workspaces are is a slot with a workspace component And if you give it a path and put children beneath the slot the entire scene will be saved if you click mark modified and Save workspace And if you make a new path and repeat the same process you can type in the previous path to load that workspace instead and the previous one will deload

This could be extremely useful for world space for example like a hotel style setup so a user can decorate their hotel room save the workspace then when they open the world they can walk into any room and load their decorations and furniture

Also not to mention the actual workflow implications of workspaces being in world space would be You could have a work area and you can work on projects with a custom path then you can save the workspace type in a new path to go to a previous project you were working on

Workspaces could also be a complete replacement for cloud spawning

Workspaces are extremely powerful and they could be used for so many different really cool things but them only being in user space dramatically reduces their functionality and potential

Here is a quote from probable prime on workspaces

Workspaces only work in userspace right now. They're really cool and powerful, I haven't had a chance to speak to Froox about them though so Im not sure what his intended design was to why they are userspace only. For now it makes sense though.

They're responsible for your Dash layout, both the screens on the dash and the top bar. As well as the contents of your facet anchors.

I added extensive logging recently to them so if you search the logs for "workspace" itll make more sense now I've typed that.
I have some local branches that make them work in world space and I use that to Edit Universe's Dash layouts as described awhile back in ⁠🌃updates

[epicEaston197]

Now if workspaces could work in world space i'm assuming the private path would not be able to be accessible
I'm assuming workspace paths will follow a similar pattern to cloud variable paths