-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: How does assets.js work? #98
Comments
Hi Maksim, sorry for delay, I was out on holiday. The primary value is that the assets can be modified at runtime by the application that is using 3dstreet. The only use at the moment is the ability to set a path for the assets that can vary depending on environment (ie fetch assets locally when doing local dev, fetch assets from a specific CDN, etc.) Future use will leverage the ability to change asset packs or selectively load only specific assets required for a given scene. As for the logic of assets.js, I would actually ask @zach-capalbo to comment on that if he's available. This was adapted from his work on a similar implementation for Vartiste. Here are docs from that project: https://vartiste.xyz/docs.html#Assets |
Hi Maksim, The reason for the complexity is that street view needs to dynamically inject it's assets into the scene. This becomes tricky because To answer your questions:
|
Thanks @zach-capalbo for the follow-up! I have added some of this info to the main readme and developer documentation. I will mark this issue as closed now and can re-open if any additional info is needed. |
Hi there,
I'd like to understand how the streetmix-assets component in src/assets.js does its job, but struggle to understand why it's so "complicated". Here are my questions:
window.AFRAME
needed?streetmix-assets
definition. Does it mean it modifies thecreatedCallback
andattachedCallback
methods it inherited ? And what's the reason for that?AFRAME.ANode.prototype
?Thanks in advance!
Maksim
The text was updated successfully, but these errors were encountered: