Through the Interface

There’s still time to fill out the 2010 API wishlist surveys

, , ,

As mentioned in this previous post, the following API wishlist surveys are currently live:

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

We've had around 500 responses across the various surveys, but to give a few more people the chance to respond, we've extended the deadline until June 11th, 2010.

To give you an idea of how the voting is looking so far, here's a summary of the responses against the survey's "money" question (5. From the following list of possible AutoCAD API enhancements, please choose three areas that you recommend we make our top priority for the next release or two of AutoCAD.):

AutoCAD API wishlist survey - interim results for question 5

7 responses to “There’s still time to fill out the 2010 API wishlist surveys”

  1. csharpbird Avatar
    csharpbird

    Hi,Kean
    By editing acad.exe.config, .NET 4.0 can support AutoCAD 2007 and 2011 . But not for AutoCAD2008~2010
    Any suggestion?Thanks.

    Reply
  2. Kean Walmsley Avatar
    Kean Walmsley

    Hi csharpbird,

    Obviously - given the timing of their respective releases - no version of AutoCAD prior to 2011 was tested with version 4.0 of the .NET Framework. Depending on the specific version's usage of .NET, it might work (as you appear to have found with 2007), but it doesn't really surprise me you'd have trouble using .NET 4.0 features with prior versions.

    As Albert said in his AU presentation, AutoCAD 2010 may have had fixes in Update 2 to enable .NET 4, but as the only reference in the ReadMe is regarding a fix for an issue with ribbons "when .NET 4 is on the system" it's not clear that that really enables the use of .NET 4 with AutoCAD 2010.

    You should get a more comprehenesive answer via ADN, if you're a member.

    Regards,

    Kean

    Reply
  3. WhyLISP Avatar
    WhyLISP

    I see that enhanced Visual LISP IDE is second on the list. Why is LISP still being used so widely? It should be abandoned or encouraged for users to abandon it. As I read somewhere someone described coding in LISP is for people that like solving logic puzzles with code (not the problem you are solving, the code itself). If you are new to development try read a LISP program, then try read a .NET program and tell me which is easier to understand and work with. If you want an enhanced IDE, use Visual Studio. This will allow development effort to go towards improving the API and adding additional ones instead of duplicating effort on writing IDE's (which is done already by Microsoft, is AutoCAD a drawing package or a programming IDE software? Why would you want it to be both? Why duplicate so much effort?) I am new to writing code for AutoCAD and have been working with both LISP and .NET and .NET is hands down the way to go (As it may be apparent my experience as a new developer learning both API's has provided me with a slight bias). I am sure I know the answer to this question since all the dinosaurs out there are holding up a horrible API, but is there any plans to take the focus off of LISP and useless duplication of effort?

    Reply
  4. Kean Walmsley Avatar
    Kean Walmsley

    The "VLIDE Enhancements" item has jumped somewhat in this year's survey, which is possibly just due to increased attention from a different community (Steve Johnson has specifically asked for LISPers to respond to the AutoCAD survey, for instance).

    As you've stated, we are not in the development tool business, these days - and would prefer to rely on companies such as Microsoft or even on open source technologies, instead - but we also need to service the requirements of the existing community of people dependent on "legacy" development environments, or to provide migration tools to - or education on how to develop equivalent programming skills on - technologies that are continuing to evolve with our products.

    It's a fine balance in terms of resource allocation, of course. I can certainly understand there are many LISPers who would like to see more development resources focused on enhancing the VLIDE. All of the input provided in these surveys is valuable to our various Product Management teams when deciding the right mix of focus for the coming releases.

    Kean

    Reply
  5. James Maeding Avatar
    James Maeding

    People that think VS is a replacement to the abilities LISP provides, do not understand the advantages of LISP. Since it can be tested at the command line, its way easier to develop small macros and things with. Also, the libraries of subroutines the LISP people have are tried and true, while .net code is still accumulating. LISP and .net are not the same, and fit different skill levels and time availablities. I can see the day when .net will be as convenient as LISP, but we are a ways out. We do not even have VSTA in acad yet, and must shut down acad and run a new session almost every time you make changes and debug. The practical implications of that and the .net learning curve divide LISP and .net by a large distance. Autodesk is wise to maintain both to meet as much market segment as possible.

    Reply
  6. Greg Bates Avatar
    Greg Bates

    Hi Kean,

    Did final numbers for this survey come in? It's interesting to see each year the differences (and similarities) in what customers are looking for. Thanks for keeping us up to date!

    Greg Bates
    Managed Design

    Reply
  7. Kean Walmsley Avatar
    Kean Walmsley

    Hi Greg,

    I've now closed the surveys and will compile the results to send out to the participants in the coming days.

    Regards,

    Kean

    Reply

Leave a Reply

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