You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 23, 2023. It is now read-only.
Currently in CRASH! whenever a user uses the Release command everyone's model is brought in sync with those changes. In the server if we were to group all specks between release calls we would have an easy way to track states that the model has gone through to get from the original to the current.
Proposed Nomenclature
State 👉 A group of all the specks between two consecutive release calls Speck 👉 Every change sent to the server (Add/Remove/Update) Release 👉 A group of states agreed upon as a release by the modeller(s)
States
The server could, on each release, fetch every speck between the current call and the last call. Compress this set by removing any selection calls or add/removes that contain duplicate geometry items etc. and then point to these specks should users want to browse through states or revert back to previous ones.
Release
Admittedly this is an idea Quite far down the pipeline. But being able to choose a 'release' and group a set of states together would be quite useful as a transmission/submission tool.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently in CRASH! whenever a user uses the Release command everyone's model is brought in sync with those changes. In the server if we were to group all specks between release calls we would have an easy way to track states that the model has gone through to get from the original to the current.
Proposed Nomenclature
State👉 A group of all the specks between two consecutive release callsSpeck👉 Every change sent to the server (Add/Remove/Update)Release👉 A group of states agreed upon as a release by the modeller(s)States
The server could, on each release, fetch every speck between the current call and the last call. Compress this set by removing any selection calls or add/removes that contain duplicate geometry items etc. and then point to these specks should users want to browse through states or revert back to previous ones.
Release
Admittedly this is an idea Quite far down the pipeline. But being able to choose a 'release' and group a set of states together would be quite useful as a transmission/submission tool.
Beta Was this translation helpful? Give feedback.
All reactions