interesting concepts. some examples look like graphs.
Antimony – A fresh look at CAD software
121–124 of 124 posts
Re: Antimony – A fresh look at CAD software
#122Earlier quoted context omitted.
Thanks, I didn't realise that. Unfortunately, I wasn't looking to charge for my app, so a commercial license isn't feasible for me. As far as I know, GPL3+ is incompatible with the iOS App Store, so that's out too.
Doesn't that depend on how much they charge for a commercial license? After all you're already paying for OS X and other tools?
Certainly, but they're charging €1000+, so it isn't really an option for me. I'll just re-write the parts I need. I'll just almost certainly do it worse, and it'll take more time, that's all!
Re: Antimony – A fresh look at CAD software
#123Earlier quoted context omitted.
This is a really great question. I don’t know the answer yet. I struggle with this problem every day when I design things in OpenSCAD, because OpenSCAD doesn't give your parametric model access to the results of the modeling operations in any way (!!) I think that Antimony kind of suffers from the same problem, but because it's using distance fields rather than plain CSG, it does have a “blend” operation ( https://gi…
in mold making for example, being able to chamfer some edges and keeping other edges very crisp (along the seam) is important.
That makes a lot of sense. I wonder if you can hack this in with a little more CSG stuff: maybe union the blended version with some giant solid blob that covers the crisp seam edges, and then intersect the result with the fully-crisp version. That's a pretty indirect way to solve the problem, but I wonder if it might work?
Re: Antimony – A fresh look at CAD software
#124Earlier quoted context omitted.
Looks like a Qt version skew problem; http://doc.qt.io/qt-5/qjsonarray.html suggests that in the current Qt, the QJsonArray constructors take either zero or one arguments, and the code is trying to invoke this one introduced in Qt 5.4 http://doc.qt.io/qt-5/qjsonarray.html#QJsonArray-2 , while your installation of Qt5 seems to only declare a two-argument constructor and the copy-constructor. You probably already knew…
After updating qt5base-dev using debian experimental, and adding -fPIC to the CXXFLAGS, it compiled nicely :) edit: there seems to be a slight problem with text rendering tho(only lowercase 'a' and bullet points are drawn), see http://imgur.com/MiX1hvL More of a qt5 issue I think
Fixed it invoking as "antimony -style gtk"
According to https://wiki.archlinux.org/index.php/Uniform_Look_for_Qt_and... qt5 attempts to be smart with guessing the desktop environment under wich it is running.