Finding this project, I've been trying to dig into this some more...
- The name of the Fusion executable appears to have, at some point, been changed (i.e. no more "360") and it does not appear that this plug-in has been updated to be compatible with that (not to mention other things I'll enumerate). To elaborate:
- The executable location's directory pattern has changed...
- From: `~/Library/Application Support/Autodesk/webdeploy/production/Autodesk Fusion 360.app/Contents/MacOS/Autodesk Fusion 360` ->
- To: `~/Library/Application Support/Autodesk/webdeploy/production/<Some UUID that changes with every update>/Autodesk Fusion.app/Contents/MacOS/Autodesk Fusion`
- The structure of the accompanying `Application Support` subfolder appears to have changed as well...
- From: `<Location of Executable>/../../Api/Python/packages/adsk/defs` (path discovered in the source code of the plug-in) ->
- To: `~/Library/Application Support/Autodesk/Autodesk Fusion 360/API/Python/defs/adsk` (notice that `defs` and `adsk` folders have switched 'levels' with one another in the path, and that the `Application Support` path still says "Autodesk Fusion 360" and not "Autodesk Fusion", like the actual app itself)
- Note: The fact that the API support files are no longer packaged in the main app bundle is mildly worrisome; There definitely are ways that this could work properly, and I have no reason to believe they can't as things are now, but the fact that the API support used to be packaged with the app bundle, but now aren't? It makes me wonder how long it will take for those two delivery vehicles/deployment locations get out of sync. I mean... it's already broken at least one thing (this!)... But I digress...
I've been trying for a couple hours to set up enough 'proxy' directories and symlinks to get it to work, with no luck. I may keep trying, but ultimately, the PyCharm plugin, written in Java (because JetBrains, so naturally it is), probably needs to be rebuilt or otherwise made more resilient to changes in these paths (or at least to update for compatibility with the latest structure). Maybe it should ask you to find the `API` directory, a configuration file, or something else entirely. I assume that, in the past, the executable was a reliable starting point from which to find the API specs, but it's clearly not that anymore. Since the path patterns used by the PyCharm/IDEA plugin aren't specified in any configuration file, but rather are specified as literals in the code, even if it were made configurable, it'll nevertheless require a rebuild.
I was a SWE in earlier life, so I can probably figure it out, but I welcome all input or any offers of collaboration.
- Ian
