Antimony – A fresh look at CAD software
mattkeeter.com
Antimony – A fresh look at CAD software
1–10 of 124 posts
Re: Antimony – A fresh look at CAD software
#2Re: Antimony – A fresh look at CAD software
#3Re: Antimony – A fresh look at CAD software
#4This is neat, but from a usability standpoint most mechanical engineers prefer to work with draft style sketches rather than a node-based interface. Thus it is neat and impressive, but I am not sure it is what the consumers in the CAD market desire.
I'm a physicist and I only used one CAD software occasionally. In the CAD software I used I had to clone primitive objects to use them in multiple operations. If I wanted to change one dimension I had to update all the clones. Simply the acyclic graph model works better for this than the tree model. (Also some operations were irreversible, that was absolutely inexcusable.)
Re: Antimony – A fresh look at CAD software
#5This is neat, but from a usability standpoint most mechanical engineers prefer to work with draft style sketches rather than a node-based interface. Thus it is neat and impressive, but I am not sure it is what the consumers in the CAD market desire.
Re: Antimony – A fresh look at CAD software
#6Re: Antimony – A fresh look at CAD software
#7The tree rep is very cool. It could probably render implicitly using distance fields without even needing triangulation. http://iquilezles.org/www/articles/distfunctions/distfunctio...
Re: Antimony – A fresh look at CAD software
#8Re: Antimony – A fresh look at CAD software
#9Only problem, to me, is that it seems like a lot of work to get a UI like this off the ground. It'd be lovely to see support of a node-based UI built into some common UI frameworks.
[1] http://worrydream.com/DrawingDynamicVisualizationsTalkAddend...
Re: Antimony – A fresh look at CAD software
#10.. with fairly similar goals - only not for architecture, but rather 3d-printig ..