How to improve

[CEXT-Dan]

I’ll post questions I get, maybe will help guide the project to be more user-friendly

[gswifort]

It is probably possible to predict the URL of individual classes and methods with great success. It would be good if the pyi file generator added these addresses (e.g. https://help.autodesk.com/view/OARX/2025/ENU/?guid=OARX-RefGuide-__MEMBERTYPE_Methods_AcDbDatabase) to the docstrings.

[CEXT-Dan]

the docstrings in DocString.db and docstrings.json are scraped from the .chm version, it’s actually the same.

I’d like to see these personalized to Python, those docs a littered with lines like “It’s the caller’s responsibility to call delete” which is not applicable as it’s the wrapper’s job.

Maybe if docstring id is -1, try to scrape one. Here’s an html version of the scrape

DocStrings.zip

[CEXT-Dan]

BTW I’m done with Ax. I plan spending time on these, and unit tests, and samples
Also, I recommend everyone grab a copy of the ARX SDK, and put a shortcut to arxref.chm on their desktop

[CEXT-Dan]

PS M:\Dev\Projects\PyRxGit> Get-ChildItem -Filter "*.h" -Recurse | Get-Content | Measure-Object -line
33920

PS M:\Dev\Projects\PyRxGit> Get-ChildItem -Filter "*.pyi" -Recurse | Get-Content | Measure-Object -line`
47510

.h is probably closer to the number of methods lol, big project

[gswifort]

HTML is more readable than a docstring with all formatting removed.

[gswifort]

please pin this discussion