Jump to content

Workspaces should be collections of stand-alone craft / (sub)assemblies


Recommended Posts

1. Craft / (sub)assemblies should be saved globally, individually, stand-alone, separate from workspaces.

2. Workspaces should be collections of craft/ (sub)assembly objects. This way you can edit a craft or assembly and when you save it all changes / improvements cascade in workspaces that contain said object. So you don't have to constantly switch workspaces to find the latest iteration of an object.

3. Also craft should be collections of stand-alone, labeled (sub) assemblies, each containing their own action groups and staging sequences. Any craft should be easy to separate into the (sub) assemblies it's made of.

4. And we should be able to launch / test any sub(assembly) or craft from a workspace very easily, with the click of a button.

Edited by Vl3d
Link to comment
Share on other sites

×
×
  • Create New...