Alright, I've got it working without any changes to Emscripten. Thanks for the feedback.
On Sunday, April 24, 2016 at 4:16:38 AM UTC-4, jj wrote: > > I agree here - it seems that the trend is it's most often useful to keep > the Emscripten runtime itself as dumb as possible about HTML/CSS layout, > since that allows the most flexible customization in the html shells by > developers. The --shell-file myshell.html linker flag can be used to pass a > customized shell template file, and src/shell_minimal.html is a good > template to start from. > > For libraries like GLFW however, some amount of CSS mangling is ok, mostly > since those are imperatively called from user code when desired (as opposed > to being controlled for all pages if it was in the runtime), and we can get > better compatibility results if the library maintains some amount of CSS > styling for presentation. If it would be useful to utilize the GLFW_VISIBLE > bit in your code for this, let us know (or submit a PR), that sounds like a > sensible feature. > > 2016-04-21 21:46 GMT+03:00 Alon Zakai <[email protected] <javascript:>>: > >> I'd rather not add more complexity to the JS code. Most users probably >> replace the default html shell anyhow, so people can customize this >> operation there. >> >> On Thu, Apr 21, 2016 at 7:39 AM, Robert Goulet <[email protected] >> <javascript:>> wrote: >> >>> Ok so I looked at this, and its seems quite easy to control with the >>> visible property as you are suggesting. However, right now the current >>> implementation of the default shell.html that ships with Emscripten will >>> hide the status/progress when it receives empty text. Ideally, we would >>> like to send that empty text status ourselves when the engine is ready to >>> render, so that we can also show the canvas at that moment. Do you think we >>> could add some sort of switch to postamble.js so we can control if >>> Emscripten should set the empty status text itself or from the user? >>> >>> On Friday, April 8, 2016 at 1:30:09 PM UTC-4, Alon Zakai wrote: >>>> >>>> I think we could use custom HTML/CSS to do this. Set the visible >>>> property to false on the canvas, and so forth. Perhaps we could hook that >>>> into GLFW_VISIBLE? >>>> >>>> On Fri, Apr 8, 2016 at 8:35 AM, Robert Goulet <[email protected]> >>>> wrote: >>>> >>>>> Is it possible to create the WebGL canvas initially hidden and show it >>>>> later when its appropriate? For example, we would like to keep it hidden >>>>> until all graphic resources are done loading, then show it. If yes, how >>>>> to >>>>> do it? >>>>> >>>>> Also, looks like the current Emscripten GLFW implementation does not >>>>> support the GLFW_VISIBLE window hint. I could try to fix it if I knew how >>>>> to create hidden canvas. >>>>> >>>>> Thanks! >>>>> >>>>> -- >>>>> 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. >>>>> >>>> >>>> -- >>> 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] >>> <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
