wow the autodesk fusion 360 API docs are interesting. it seems like they're trying to see how much documentation they can write without possibly being useful

hypothesis: it is possible to over-document something

I'm looking at a Profile object. I see it has a property called profileLoops. Oh, handy, maybe I need to look at a ProfileLoop.
I click it, and it tells me that Profile.profileLoops is a read-only property that returns a ProfileLoops.

I click, and it tells me ProfileLoops is a collection of ProfileLoop objects.
I click item, it tells me it returns a ProfileLoop object. I click it, and now, and only now, am I looking at a ProfileLoop definition

ProfileLoop has no special property, it just contains ProfileCurves.

that's multiple ProfileCurve objects inside a ProfileCurves object which you get from the read only property ProfileLoop.profileCurves

I don't think there's any code at the bottom of this stack of turtles.

It's just docs, all the way down.

it's weird that the two languages it lets you use are C++ and Python, because this whole API feels like bad java

to import an SVG, you get the ImportManager from Application, then call ImportManager.createSVGImportOptions(filename) and then set parameters on that object, then call ImportManager.importToTarget or ImportManager.importToTarget2

the one giveaway that this is c++ and not java is that they called it a "manager" and not a "factory"

oh god this is going to be a significant tarpit

it's at the point where using the API might be harder than just making a script that clicks on items in the GUI because this is terrible

I think this algorithm is something like... I don't have the proper latin prefix for this. quintic? it's o(n^5). maybe the next one up. sexic?