3D Renderer

[Waidhoferj]

Argo Editor will need to offer a preview to the editing club member of how the updated tour will look for the end user. Take the code from the frontend renderer and add the necessary parts of it to the Editor. Or talk with the web team about mounting a dev server that stays up to date with their work, but can connect to the editor for preview purposes.

[Waidhoferj]

@masonmcelvain Likely we can just take the core of what you've got and leave off some of the frills. Like render only one panorama or path without testing connections. Any suggestions where we should start grabbing code?

[masonmcelvain]

@Waidhoferj The components for the virtual tour in main are pretty much the same as when you built them. We are working on another branch (support-json-data-protocol) that will update the JSON to match the specs we came up with as a group, and thus modify how the components consume the JSON. That will likely get merged today, if you are ok with waiting, or you can just take what's there right now.

Right now all the JSON data is still local under src/assets, because we won't have an API to hit for a while. If I understand correctly, you should just be able to grab the components and JSON and plug it into your editor 👍

[Waidhoferj]

We can wait for the JSON update and then pull in parts the repo. Thanks for nailing down the JSON contract so early!