The problem that this feature will solve:
While the Cloud is a great idea, for a business such as ours, where everything must go through GIT (our revision tracking system), including models, the use of Shapr3D cloud creates a case where changes can get lost.
It also makes it problematic when we want to load the previous days work: load? Doesn’t exist. Instead, we have to IMPORT our project.
- Models, code, etc. is changed per tasks
- Models are EXPORTED (because there is no save) to get them onto the local drive (remembering that we also need to set the name as well!)
- Models are checked into GIT revision storage system and pushed to our local GIT server (usually done at the end of the day unless there are reasons to do otherwise)
- If older model is checked out with GIT, need to IMPORT (again, there is no load)
In all of this unless you have set up the name of the design using the Cloud, the title of the object will be UNNAMED DESIGN.
Brief description of the outcomes that you expect from this feature:
This should allow me to do traditional load and save to local drive so that we can do proper revision tracking. This would also assign a name to the design instead of UNNAMED DESIGN.
By allowing this, we can assure that the designs are correctly tracked and modifications don’t end up where they shouldn’t.
What can’t you achieve without this feature?
I can’t change the name of the file unless I save it to the cloud. As I indicated, this can be a point of failure (we need everything to go through GIT).
Is this a workflow blocker for you? Is this why you can’t use Shapr3D for work? Is this slowing you down?
No, it just makes it weirdly convoluted and introduces a point of failure (should modifications end up on the cloud instead of the local drive). It is also problematic that unless the cloud is used, you are incapable of naming a design for export.
The lack of a standard save/load mechanism may be ideal for Cloud based system, but falls apart should one need standard functionality.