Comment by fsloth

Comment by fsloth 4 days ago

I agree with the OP:s statement

"With version control"

but there are 0 reasons you can't have that in a visual application as well.

It just needs good domain model design.

I mean it's _not_ trivial. To start with you have to first understand the relationships between your model entities, and how versioning strategy affects your model hierarchy (well, graph basically), and that potentially locks you down on a certain path. But it's totally doable as a hobby project (once you know CAD systems are built - so it's not suitable as ones first CAD project ofc).

WillAdams 3 days ago

Example of a CAD program/system which implements this?

Reply View 3 replies

fsloth 3 days ago

Version control?
Quite a few with their domain specific naming conditions, constraints and workflows.
For example Fusion 360 https://www.autodesk.com/products/fusion-360/blog/fusion-360...
Then there's stuff like "Tekla model sharing" https://www.tekla.com/products/tekla-model-sharing
Onshape https://cad.onshape.com/help/Content/versionmanager.htm
Etc
The requirement to a) collaborate b) version the work is quite old and well supported industrially. Depending on the application it may not "look or feel" that nice of course.
I guess the key thing is these are not "code first" offerings.

Reply View | 2 replies
- WillAdams 3 days ago
  
  I was more thinking opensource options now that Ondsel has folded, but appreciate the information.
  
  Reply View | 1 reply
  
  fsloth 3 days ago
  
  Their blog post about this subject is really good https://www.ondsel.com/blog/goodbye/
  They chose maybe one of the toughest imaginable combinations for a business model. Viable open source businesses are hard (since you don’t own your ip in closed form, hard to explain to investors what the actual value is). 3D businesses are hard.
  So it’s hard x hard.
  Clearly their _tech_ worked. I guess there is a lesson here - better mousetrap is almost never enough for a viable business.
  
  Reply View | 0 replies