A reasonable way to handle files loading about silenceengine HOT 6 CLOSED

This is what I have thought of, and in a way this is solved by using the ResourceLoader. Consider a game which has a large sized resources, and it needs one large file in one level. Now in case we are going to keep a preloader, then we have to keep all these files in the memory, which is not the developer of the game wants. This is the reason I went with the callback approach like JavaScript.

And I said that ResourceLoader can solve this issue, it is like a pre-loader that you are talking, you tell it which files to preload, and once the loading is done, you can get the files content directly because they are already loaded into the memory.

My question is, why to use the ResourceLoader directly in the engine when it is designed to be used by the users?

from silenceengine.

When loading asset files, the developer would almost always want to keep them in memory. While larger files would be the rare exception. It would make much more sense to preload things by default, and have defined ways of dealing with the exceptions.

As for your question, I don't really understand what you're asking. Specifically the used by the users part.

from silenceengine.

What other engines actually do is they use BrowserFS. I should have searched for it in the beginning, it is awesome and it do really have support for synchronous IO like preloaders do, but once loaded it also caches the data in either LocalStorage, or HTML5 FileSystem or IndexedDB or whatever the browser supports, making it the best choice that we had to have.

I think this can bring us a new synchronous API, even large files means that they need to be loaded only once. This also removes the synchronization issues we have in Android, because we no longer need threads and hence the apps can properly quit without some hacks in AndroidWindow.

I'll start by writing GWT bindings to this API.

from silenceengine.

It is time for about a release. This is post-poned for now, but in future version, we will have a synchronous API along with the current asynchronous API.

from silenceengine.

The solution for this is to have the renderers pre created and let the user use the ResourceLoader for the purpose of loading the files. This is even more simpler if you use the ResourceLoadingState.

To make your files loaded in before the game starts, use the on-init callbacks.

from silenceengine.

Now that the renderers and programs are precreated once in the engine and are cached, I think this is resolved. Regarding access to synchronous IO, that is not possible without increasing memory consumption, and may pose as an issue on HTML5 backend for larger games. So closing this stating that it is now solved.

from silenceengine.