More updates on Revit 2017, Revit 2018, and above all our treasured Revit API Docs.
Plus, the clock is running now on two Forge enhancements.
If your existing app uses the obsolete View and Data API or unscoped tokens, it will stop working soon!
Finally, notes on DevCon, AU, female coders and the Twitter Women Who Code conference:
Revit API Docs provides online access to the full contents of the Revit API help file RevitAPI.chm for all versions of the Revit API from Revit 2015 onwards.
Now it is up and running with support added for Revit 2018 as well:
Many thanks to Gui Talarico for maintaining this invaluable resource!
Awesome, awesomely effective and awesomely simple web site, btw :-)
2018 has received its first little update, the Revit 2018.0.1 Hot Fix.
The reported issues resolved in Revit 2018 build 20170421_2315 include:
Here are direct links:
A new update for Revit 2017 has been published as well, with too many enhancements to list here.
Please refer to the release notes for full details.
Here is the direct link to download and the readme doc.
As part of the continual Forge platform security improvements, enforcement of the scopes requirement for all access tokens will begin on May 22, 2017.
If you have apps created before June 15, 2016, you need to update your code so that any access tokens generated by your app request scopes.
Calls without scopes will be rejected after May 22.
For full details, please refer to the Forge OAuth scopes docs.
As said, the clock is running now.
Convert your existing app from the obsolete View and Data API to the Forge Viewer API.
It’s been almost a year since the release of the Forge Data Management API, Model Derivative API, and Viewer JavaScript library replacing the original View and Data API.
Consequently, on July 17, 2017 the View and Data API will close down.
Please migrate your code from the obsolete platform version v1 to the new platform v2 before July 17, 2017, or your application will stop working.
For more information, please refer to the detailed description
on migrating apps from Forge v1 to v2.
The Forge DevCon call for speakers is open.
Are you interested in sharing your experience working with the Forge platform?
Have you creatively used Forge to enhance a project or solve a challenge?
If so, then come join other experts in a leadership role at Forge DevCon.
Please submit your proposal by May 17!
As already mentioned, the Forge DevCon has been aligned with Autodesk University in Las Vegas.
Autodesk University obvoisly remains the most important event of the year for all Autodesk technology not directly related to Forge programming, including Revit, its API and add-in development.
If you have anything you would like to share on any such subject, please submit your AU proposal by May 17.
Five female Autodeskers will take the stage at the Women Who Code conference at Twitter HQ on Saturday April 29.
Check out the interview with them on female professionals, developing and collaborating.