Oh, sorry, that was my fault. I could have been more precise.
The SpineCanvas class is just a simple utility to quickly use spine-webgl. It uses the default AssetManager of spine-webgl.
You can create your own custom SpineCanvas by copying its code, or you can also extract the logic you need from it without creating a dedicated class.
[spine-ts] loading png assets as needed for web
got it working 
️
joo Ah ok, no worries. Thanks for your patience and bearing with me while I'm still onboarding onto Spine and asking lots of questions
We're more than happy to assist riggers, animators and developers in using the editor and the runtimes! Feel free anytime to ask anything that is unclear to you 
joo got it working
I'm glad to hear that!
You are right, the spine-pixi atlasLoader loads all atlas pages transparently.
This implies you cannot use it to achieve your goal. However, as you can see from the code it just does what our spine-webgl loadTextureAtlas does.
I didn't try it, but I guess that if you load the atlas as a txt file, instance the TextureAtlas with the atlas txt data, add the TextureAtlas to the asset cache, and eventually initialize your Spine game object, then you can defer the texture pages loading when you want.
Let me know if you need any help with the code
3 महीने बाद में
Hi Davide!
It has been a while now and I'm revisiting this again, where I only want to load the textures I need depending on what skins are set, and not the full list of textures.
I ended up using spine-player instead of spine-webgl because spine-player already has a lot of features I need that is built in. However, I'm not sure how to apply a custom asset manager and custom asset loader with spine-player without forking spine-player and adding my custom asset manager/loader. Would love some advice on how to move forward on this.
Thanks!
It's just that the player has a lot of features already implemented that I need, whereas with spine-webgl, I would need to implement a lot of it from scratch. That's why I was hoping I could just use the player and build on top of it. As for the widget, I'm waiting for it to be officially released before using it in production!
Thanks
We were busy with the pixi-v8 runtime release, but now that we've lanuched it, I'll resume on working on the widget.
Regarding the Player customization, if you don't want to fork it, you'll need to monkey patch/extend the AssetManager or the Player overriding the method that loads the texture.
I'll give it a try tomorrow morning and if it works, I'll share with you a piece of code that you can use as a base.