Support loading screen while assets download and entities load

[ngokevin]

Issue by cvan
Friday Dec 18, 2015 at 22:45 GMT
Originally opened as https://github.com/aframevr/aframe-core/issues/718

---

Per https://twitter.com/footedesign/status/677967278890221570

[ngokevin]

Comment by ngokevin
Friday Dec 18, 2015 at 23:54 GMT

---

depends on adding asset blocking to <a-assets> before it fires loaded.

then users than listen on loaded and manage loading screens however they want.

[ngokevin]

Comment by cvan
Friday Dec 18, 2015 at 23:59 GMT

---

@ngokevin but in the case of external URLs that get loaded from material component and then from THREE.js's loaders, we can handle those today without changing making <a-assets> inert (which we could do, but then we'd have to enable some like preload boolean).

[ngokevin]

Comment by ngokevin
Saturday Dec 19, 2015 at 00:00 GMT

---

i think we intend if you don't put it in assets there is no preloading/blocking logic.

right now a-assets does nothing. we should enforce through a-assets because that is canonical, anyone can make a material component.

[ngokevin]

Comment by cvan
Saturday Dec 19, 2015 at 00:02 GMT

---

i think we intend if you don't put it in assets there is no preloading/blocking logic.

yeah, I know - basically what this issue is for is to introduce some type of events (perhaps assetsstart, assetsprogress, and assetsend or something) for materials on entities and models to know when the asset(s) have been actually loaded.

[ngokevin]

Comment by ngokevin
Saturday Dec 19, 2015 at 00:04 GMT

---

Yeah we'd add events. But wouldn't have to touch the material component itself

[ngokevin]

Comment by cvan
Saturday Dec 19, 2015 at 00:07 GMT

---

Yeah we'd add events. But wouldn't have to touch the material component itself

correct, just the loadImage, loadVideo, etc. functions in that file

[ngokevin]

Now supported. #925 is a bit more specific