Gab_CV

6 ms·

1.
by Gab_CV 8y ago
I am preparing a Readme file with more explanations. Yes I think I think I'll extract everything on the server, and implement some form of lazy loading thanks to some emscripten mechanism
2.
by Gab_CV 8y ago
It is because IndexedDB maximum row size is not that big, and depends on the browsers
3.
by Gab_CV 8y ago
First commits on the repos (D3 and Regal) are from 17/12. I started to work on this a week or so before the first commits, so it took roughly 4 weeks, with daily progress and commits. In the end the amount of changes in the code is rel
4.
by Gab_CV 8y ago
Actually, indexedDB is used to cache/store the whole .pk4, but using small chunks of data (50MB or so). This works well in practice. The best would be that all browsers support the Chrome Filesystem API, but that's not for now
5.
by Gab_CV 8y ago
I think it would be better to stream only needed data, using some lazy load mechanism. Still need to figure out what is the best approach
6.
by Gab_CV 8y ago
One of the difficult thing was not knowing during the whole porting process if in the end it would really work, or not... I almost gave up several time :)
7.
by Gab_CV 8y ago
I double checked on the License specific to the demo (License.txt in the install), and it is indeed less restrictive. However this might be gray area
8.
by Gab_CV 8y ago
Well, the end idea is to have sandboxed native speed applications, immediately available without any installation. The issue of "loading" needs to be tackled on. In that very specific case, it is just that the program was not desi
9.
by Gab_CV 8y ago
Yes, it is dead just now. I guess I have to take another hosting option :)
10.
by Gab_CV 8y ago
Hi! I am the guy who did this port. I am very sorry for long download times, but the HN/Twitter buzz was unexpected and the host server - a cheap shared hosting I barely use just for testing purposes - is currently crying very hard. Oo