excalibur-playground/templates/ at main · excaliburjs.com/excalibur-playground · Tangled

excaliburjs.com / excalibur-playground

0

[READ-ONLY] Mirror of https://github.com/excaliburjs/excalibur-playground. Excalibur Playground Source Code excaliburjs.com/excalibur-playground/

0

excalibur-playground / templates /

at main 4 files

Chris K feat: add autoplay option. fix timing issue (#9) 9mo ago

fix: fix pathing of assets when deployed (#5) Fixes pathing issue created in https://github.com/excaliburjs/excalibur-playground/pull/4 I've folded in a few other changes as part of this PR: - added the running man spritesheet asset, I figured that would be useful for the docs. - I'm not sure where the running man came from, so no licence info. - vertically stack the canvas and editor when embedded - this is to support the change in the docs to be more like this https://svelte-pixi.com/api/components/animated-sprite/ On that second point (the svelte-pixi example), I am wondering if we should completely hide the toolbar and instead autoplay when embedded?

9 months ago

add preloaded asset templates (#4)

10 months ago

feat: add autoplay option. fix timing issue (#9) Closes #7 ## Changes: - Adds an autoplay param so embedded playgrounds show something to the user instead of a black screen - Updates the non-audio templates to skip the play button. I'm envisioning for the embedded playgrounds in the docs to follow a similar pattern? Especially if its not audio or not too intense. I have also tried to address a timing issue. I believe its already happening in production, but seems more obvious with autoplay enabled. Occasionally throwing the following "Typescript is not registered". We're not the only team to hit this: - https://forum.babylonjs.com/t/ts-playground-red-banner-could-not-find-source-file-inmemory-model-1/55126/4?utm_source=chatgpt.com - https://github.com/BabylonJS/Babylon.js/pull/11554 If I understand the Babylon playground code, they are retrying? At least the comment suggests that. There is an open issue for Monaco Editor, but unfortunately its almost 10 years old. With "waiting skeleton" memes included. https://github.com/microsoft/monaco-editor/issues/115 Regardless, I've added a little exponential backoff that retries the client/worker. Since adding that retry code, it consistently loads. Often between 0 and 2 attempts

9 months ago

feat: add autoplay option. fix timing issue (#9) Closes #7 ## Changes: - Adds an autoplay param so embedded playgrounds show something to the user instead of a black screen - Updates the non-audio templates to skip the play button. I'm envisioning for the embedded playgrounds in the docs to follow a similar pattern? Especially if its not audio or not too intense. I have also tried to address a timing issue. I believe its already happening in production, but seems more obvious with autoplay enabled. Occasionally throwing the following "Typescript is not registered". We're not the only team to hit this: - https://forum.babylonjs.com/t/ts-playground-red-banner-could-not-find-source-file-inmemory-model-1/55126/4?utm_source=chatgpt.com - https://github.com/BabylonJS/Babylon.js/pull/11554 If I understand the Babylon playground code, they are retrying? At least the comment suggests that. There is an open issue for Monaco Editor, but unfortunately its almost 10 years old. With "waiting skeleton" memes included. https://github.com/microsoft/monaco-editor/issues/115 Regardless, I've added a little exponential backoff that retries the client/worker. Since adding that retry code, it consistently loads. Often between 0 and 2 attempts

9 months ago