API Overhaul
I am pleased to say that we are finally making some progress on the API front and our development team has agreed to look at our current API and kick off an overhaul of sort.
Needless to say that this is long overdue and I am very excited that this is finally taking shape. Well, "good things take time"!
This change will be reflected in next years release and will not affect Autodesk Design Review 2009. The numerous new features and improvements did not leave any room for the much needed API work in the 2009 release time frame.
It is planned that the makeover will include not only the addition of missing functionality and correction of problems, but also the removal of API that are not being used or are no longer relevant, due to being linked only to legacy products.
This is were YOU come in!
Enclosed is a list of API that are currently slated for the "grinder" and it is crucial that you let us know if you are using any of the stated API. The selection was made based on earlier customer feedback and an internal evaluation.
- IRasterToDWF
- IMarkupEvents
- IAdTempFileHolder
- IAdSectionTypePrivate
- IAdPrintDialog
- IAdPageNavigatorCtrl
- IAdContent
- IAdContent2
- ISheetListCtrl2
- ISheetListCtrl3
- IMarkupPropertiesCtrl2
- IMarkupCtrl
- IMarkupCtrls
- IPropertiesCtrl
- ISectionPropertiesCtrl
- IThumbnailCtrl
- IThumbnailCtrl2
- IThumbnailCtrl3
- IAdECompositeViewerPrivate2
- IEModelEditorToolPrivate
- IText3DToolGather
- IAdPagePaper
- IAdEPlotBookmark
- IAdEPlotDocument
- IAdEPlotPage
- IAdEPlotPagePrivate
- IAdDocument
- IEPlotDrawList
- ISelectionInserter
- IAdEPlotViewer
- IAdEPlotViewer2
Please reply to this post or send your feedback directly to volker.joseph@autodesk.com. Feedback can consist of anything API - even API you would like to see or is not working for you at this point. Please ensure to include an explanation or supporting documentation with your feedback, thank you.
Now is the time to speak up!
--Volker
Subscribe
Perhaps people could register their feedback as comments to this blog article, so we can all see what API methods should not be depricated.
Posted by: Scott Sheppard | March 05, 2008 at 06:56 AM