I am still in the initial steps of preparing for my upcoming presentations on connecting the desktop and the cloud and exploring more Forge sample starting points.
At the same time, we are in the midst of the Forge and AppStore online hackathon webinars that I mentioned last week, with one down and nine more to come:
More Roomedit3dv3 Starting Points
I mentioned Augusto's two nice up-to-date samples as potential starting points for my planned roomedit3dv3 renovation of the ancient 2D roomedit and the initial Forge-based roomedit3d samples last week, discussing:
- The forge-3leg.nodejs-template demonstrating 3-legged OAuth for logging into and retrieving models from A360.
- The model.derivative-nodejs-box.viewer using the Model Derivative API to translate Box files and display them in the Viewer.
Philippe also pointed out his more complete series of up-to-date Forge boilerplate templates.
In Philippe's own words:
I'm polishing a new set of forge samples, which I also designed to be used as boilers that range from low to medium complexity.
Multiple projects can be deployed independently to Heroku:
- viewer-offline
- viewer-barebone
- viewer+server
- viewer+server+oss
- viewer+server+oss+derivatives
- viewer+server+data-mng+derivatives
You can also run the samples locally, just take care about matching the callback url that you specify for your forge app in the portal.
For example, I created an App called "Forge DEV" intended to test my local set up.
Callback URL: http://localhost:3000/api/forge/callback/oauth.
This should work as-is when you run the sample locally.
For Heroku deployment I created another forge App with callback URL https://adsk-forge.herokuapp.com/api/forge/callback/oauth.
When deploying to Heroku, I use HOST_URL = https://adsk-forge.herokuapp.com.
You can test the app at adsk-forge.herokuapp.com.
Forge Webinar Series
Jim Quanci himself already presented the first webinar session two days ago, with full documentation and recording already up and published live for your future reference and enjoyment:
- September 20 – Introduction to Autodesk Forge and the Autodesk App Store
Here are the rest of the series, starting later today and continuing during the remainder of the Autodesk App Store Forge and Fusion 360 Hackathon running until the end of October:
- September 22 – OAuth and Data Management API – token-based authentication, authorization and a unified and consistent way to access data across A360, Fusion 360, and the Object Storage Service.
- September 27 – Model Derivative API – enable users to represent and share their designs in different formats and extract metadata.
- September 29 – Viewer API – formerly part of the 'View and Data API', a WebGL-based, JavaScript library for 3D and 2D model rendering a CAD data from seed models, e.g., AutoCAD, Fusion 360, Revit, and many other formats.
- October 4 – Design Automation API – formerly known as 'AutoCAD I/O', run scripts on design files.
- October 6 – BIM360 – develop apps that integrate with BIM 360 to extend its capabilities in the construction ecosystem.
- October 11 – Fusion 360 Client API – an integrated CAD, CAM, and CAE tool for product development, built for the new ways products are designed and made.
- October 13 – Q&A on all APIs.
- October 20 – Q&A on all APIs.
- October 27 – Submitting a web service app to Autodesk App store.
