API wishlist surveys for Autodesk products

Our annual API wishlist surveys are now live:

AutoCAD®
AutoCAD® Civil 3D®
Revit®
Autodesk Inventor®
Autodesk Navisworks®

Please do take the time to provide us with your input: it's one of the most direct ways to influence the direction of the Autodesk products you customize or for which you develop applications. Our various Engineering teams take this feedback very seriously when prioritising the APIs to expose over the coming releases of our software. And if you (optionally) provide your email address in the survey, I'll send you a copy of the results once they've been compiled.

The surveys will remain open until June 3rd, 2011. Thanks in advance for your feedback!

5 responses to “API wishlist surveys for Autodesk products”

  1. Once again.....

    Better property palette support.....

    If you whine long enough, do you win 🙂

    For a hack programmer like myself, the current implementation is just too difficult to implement for day to day programming. That level of integration (support on the AutoCAD property palette) truly would bring my application to a professional level. Users have expectations; in particular, the ability to edit properties on the property palette is one of them. It's high time this gets properly addressed.

  2. Kean Walmsley Avatar

    Keep whining (if that's what you want to call it), John!

    Sometimes the reason we're not visibly resolving something isn't because it's not important, it's that deeper infrastructure work is needed for us to provide a holistic solution (one example is Overrules, our main answer to the custom objects from .NET question).

    We definitely hear your need (and feel you pain), but please don't stop reminding us until we get there.

    Kean

  3. Danny Polkinhorn Avatar
    Danny Polkinhorn

    In my survey, I totally forgot to request the ability to manage options, basically anything in the Options dialog. I have a routine that resets a user's profile, and the only way to do it (without lisp) is via ActiveX. I would prefer a .NET solution.

  4. It was mentioned in the survey, but I only saw this today

    RE: API documentation, there's a lot of sense in this article

    37signals.com/svn/posts/3018-api-design-for-humans

  5. Thanks, Nick.

    Kean

Leave a Reply to John Holmes Cancel reply

Your email address will not be published. Required fields are marked *