I made my choice on the starting point for the new roomedit3d incarnation, and the second Forge webinar was successfully held:
The Birth of Roomedit3dv3
So far, I evaluated two of Augusto's apps and Philippe's series of boilerplate sample apps as potential starting points for a new incarnation of roomedit3d:
- data.management-nodejs-integration.box, demonstrating 3-legged OAuth access to models on A360 and transferring them back and forth between A360 and the Box content management platform.
- model.derivative-nodejs-box.viewer, demonstrating access to models on Box and displaying them in the Forge Viewer.
- forge-boilers.nodejs demonstrating the suite of Forge APIs and components:
- Authenticate and authorise the user – Authentication (OAuth)
- Access and download a RVT project file from A360 – Data Management API
- Translate and access its geometry and metadata – Model Derivative API
- Display to the user – Viewer
Each of these is fully documented in its own GitHub repository, and the first two are briefly highlighted in Augusto's discussion on Box & Forge.
I also made some notes on them in my first search for a suitable roomedit3dv3 starting point, followed by more roomedit3dv3 starting points.
I finally decided to go for the latter, for the sake of completeness. Besides including all the Forge APIs that I might possibly need, it also makes use of a full web development and deployment stack including the Webpack module bundler and NPM packages to build and generate the frontend code. On one hand, this requires an extra build step. On the other, it directly supports ES6 code, since all the JavaScript is passed through Babel via the webpack build and bundling step.
I forked Philippe's repository and renamed it to roomedit3dv3, tagging this initial forked state as release 0.0.0 in order to track all further changes right from the start.
So far, all I have done is rewrite the documentation, remove the simpler boilerplate code samples #1-#5, and test that the one I am using, #6, still is in a working state. I now reached release 0.0.4 just doing that.
I actually hope and expect that work to be the largest chunk, and that adapting the existing viewer extension to do its job in the new environment will be less work the documentation work already completed :-)
It is looking good, though, and you can check out the further details by looking at the readme.
Forge Webinar Series
Augusto Goncalves presented the second session in the ongoing Forge webinar series.
Again, support documentation and a recording have already been published for your future reference and enjoyment:
- September 20 Introduction to Autodesk Forge and the Autodesk App Store
- September 22 Introduction to OAuth and Data Management API – on OAuth and Data Management API, providing token-based authentication, authorization and a unified and consistent way to access data across A360, Fusion 360, and the Object Storage Service.
Here are the rest of the series coming up and continuing during the remainder of the Autodesk App Store Forge and Fusion 360 Hackathon until the end of October:
- 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.
