Great approach, thanks for the reply!

-Raúl

On Monday, September 8, 2014 3:06:36 AM UTC-5, Floh wrote:
>
> I'm still building with the original shell.html file for testing, but when 
> building the web page replace the original HTML with my own and only copy 
> the .js and .mem file over. This was easier to do in the end since the web 
> page is also generated from a python script.
>
> The web page files are here (the emscripten sample shell page is 
> emsc.html): https://github.com/floooh/oryol/tree/master/web, the .html 
> files are actually templates with ${...} variables, which will then be 
> replaced by a python script with variable content (and a json file which 
> per-sample attributes generated during the cmake run), the python script is 
> here: https://github.com/floooh/oryol/blob/master/tools/webpage.py
>
> Cheers,
> -Floh.
>
> Am Montag, 8. September 2014 00:48:06 UTC+2 schrieb Raúl G. Roa Gómez:
>>
>> Hi Floh, 
>>
>> Your demo page is looking good.
>>
>> I'd like to know if you know how to make emscripten build to a different 
>> HTML template or if you just imported the JavaScript files manually to your 
>> new example pages.
>>
>> On Sunday, September 7, 2014 1:44:48 PM UTC-5, Floh wrote:
>>>
>>> Hi,
>>>
>>> I spent the weekend to make the Oryol sample web page a bit more 
>>> presentable: http://floooh.github.io/oryol/index.html
>>>
>>> There is no way to get any sort of download progress events from a 
>>> <script async ....> element is there? I would have peferred a real progress 
>>> bar for the emscripten demos, but had to settle for a simple spinner 
>>> rendered into a temporary 2D canvas.
>>>
>>> Slightly off-topic: some of the pnacl demos currently crash in Chrome, 
>>> and require a recent Chrome Canary (I think because of my use of 
>>> vertex-array-object extension) 
>>>
>>> Cheers,
>>> -Floh.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to