4 ms·
Looking at the source, it seems like their viewer is based on OpenSeadragon: https://openseadragon.github.io/ https://openseadragon.github.io/
by yorwba 7y ago
Looking at the source, it seems like their viewer is based on OpenSeadragon: https://openseadragon.github.io/ https://openseadragon.github.io/
- dTal 7y agoThen they've added an astonishing amount of value. OpenSeadragon appears to be nothing more than a zooming 2D image viewer that consumes image pyramids? I'm not sure why you would even start with that, when your goal is to render hi-res 3D meshes in real time. Is there even an overlap in functionality?
- sunsetMurk 7y agoOh my. I'm in love. This is going to divert some of my attention for a side project... Hopefully for the better! This is so packed full of useful features, and at first glance a very thoughtful implementation and healthy ecosystem.
- framefactory 7y agoVoyager, the 3D viewer uses Three.js for WebGL rendering and a custom entity/component architecture for both the scene tree and the general architecture of the application. The UI is built using custom Web Components with the help of LitElement and LitHtml. The viewer itself is a web component and super easy to embed. The tool suite also provides an authoring environment for annotating and editing scenes. Documentation: https://smithsonian.github.io/dpo-voyager https://smithsonian.github.io/dpo-voyager. Contributions are very welcome! Full disclosure: I'm the developer of the Voyager 3D suite.