cacb

3 ms·

1.
by cacb 6y ago
Extensions for FEM modelling is something I would like to see with AngelCAD. That would be cool. I don't know Julia but you can build a front end to the AngelCAD boolean engine and by-pass AngelScript if you so prefer. Flexibility is a
2.
by cacb 6y ago
If you observe users of a declarative language things sometimes get very complicated because of the language limitations that do not match the thought process of the user. AngelCAD does not try to impose a specific programming paradigm, it
3.
by cacb 6y ago
Why should it be a 'declarative' language? There is no inherent benefit in that IMHO. I want the full set of capabilities that a general purpose language can offer, and still be scriptable. What is easier or more legible is very s
4.
by cacb 6y ago
AngelCAD is not a "another CAD Exchange format". It is a scripting tool that creates existing standard formats such as STL, OBJ, OFF, DXF, SVG and more. It also reads some of those exchange formats. There is no new exchange format
5.
by cacb 6y ago
It is specifically not a 'declarative' language, it is a general purpose language. OpenSCAD uses a declarative language, AngelCAD does not. If you want a declarative language, use OpenSCAD or implement your favorite language on to
6.
by cacb 6y ago
This is very true and some of the reasons why I designed AngelCAD the way it is. As you say they are diffable and well suited for tracking in source control systems like git for example. Nothing wrong with GUI CAD tools, but there are many
7.
by cacb 6y ago
Because I wanted a strongly typed language that among many good things provides the opportunity for better error messages. Also, the AngelScript compiler is 100% embedded in the application and does not rely on an external environment like
8.
by cacb 6y ago
I am the designer/developer of AngelCAD. It began from a desire of a fast Constructive Solid Geometry engine, based on a strongly typed scripting language. It is not a goal of the core AngelCAD package to develop a traditional CAD GUI,