A Saved 'Custom' Playground Scene: https://www.babylonjs-playground.com/#QKQHS -
The playground's top menu currently contains 11 buttons:
Run - The Run button is easy to understand. After you paste-in code to the editor, or after you make changes to the code in the editor, you press Run. This commands the playground to try to render your scene.
Save - The Save button will cause your scene to be permanently stored in the playground's database, and it will issue a unique URL, which we will talk more about, below. Don't worry about accidentally overwriting any of the pre-installed demo scenes in the playground. That is not allowed to happen. Often, the Save button is used so that you may share the scene's URL with others, or to allow you to bookmark the saved URL in your browser, and return to continue your 'play' at another time.
Get .zip - The Get .zip button is a handy playground feature. If you wish to take your scene home, publish it on a web server, or hand it out to others, THIS is your button. Get .zip attempts to install your editor code into a single index.html file, and puts that file into a zip called sample.zip. Then it offers the sample.zip file to you, for downloading. Once downloaded and unzipped, you will see the file named index.html. You can browse this file with a webGL-ready browser, and your scene should render nicely in your browser. After you are sure that your index.html file is working properly, you may want to publish it to a web server and share your beautiful playground scene with the entire world. There is no need to install framework files such as babylon.js and hand.js in nearby directories, because the index.html file references the same on-line versions of the framework... as the playground itself uses. The index.html file is ready-to-run and completely portable. (We love it!)
New - The New button is a unique and handy feature. If you look carefully at the editor code in the picture above, or if you have selected one of the pre-installed playground scenes from the drop-down scene selector, you will notice that they are 'wrapped' in a function called 'createScene()'. The createScene() function is a very common function used in many BabylonJS scenes. Copying and pasting createScene() functions is done often with users of the BabylonJS framework. By pressing this button, you will empty the contents of the editor, and a basic un-programmed createScene() function will be placed in the editor. A camera is provided by default, but you may want to add some light and mesh, so the new scene becomes renderable.
Clear - The Clear button is also easy to understand. This button simply empties all the code out of the playground editor. It is often used in preparing for the pasting-in of a createScene() function, or in preparation for some experimenting that you are about to embark-upon. The BabylonJS playground is a fantastic way to create experiments using the BabylonJS framework. It is a wonderful way to learn.
Font size - The Font size button almost needs no explaining. This button and resulting pull-down selector allows you to adjust the font size of the code in the playground editor.
Safe Mode - The Safe Mode checkbox is OFF by default, but auto-activates when any change is made in the editor. In safe mode, the playground issues a "leaving the page?" confirmation warning when you try to unload/reload a freshly-edited, un-saved scene.
-Editor Toggle - This button hides or un-hides the editor portion of the playground.
+Debug Layer Toggle - Yes indeed, this toggles Babylon's handy interactive debug layer. Try it, you'll love it.
Scene Selector - This pull-down selector button (shown as 'Custom' in the picture above)... is used to select any of the pre-installed playground demo scenes. 'Custom' is not the name of any of those demo scenes. The reason that it says 'Custom' is because the scene in the editor at the time that the picture was taken... was a 'custom' scene. It was a modified Basic Scene demo that I created for use in the picture. Often, when you first arrive at the playground site, this button will be labeled 'Basic Scene'. No matter what label is currently on the button, the button is called the Scene Selector button.
Fullscreen - The Fullscreen button also needs very little explaining. This button causes the right-side rendering canvas to go into fullscreen mode. Upon entering fullscreen mode, your browser will provide instructions about how to exit fullscreen mode and return to the playground's default split-screen mode.
The playground's left-side code editor is a 'smart' editor which is based-upon the Monaco Editor. The playground editor has many fantastic features. It uses type-ahead features such as automatically adding matched quotes, parentheses, braces, and brackets... handy things for a programming editor. It tries to spot programming errors, and places little icons along the right side when it sees potential syntax problems. Telling of the many features of our editor... is beyond the scope of this tutorial. You can learn more about the editor by viewing some of its keyboard shortcuts, and by simply spending some time using the playground.
oops - One of the most important features in any programmer's editor... is UNDO and REDO, and our playground editor fully supports both of these features. I am not familiar with the undo and redo keypresses for all OS systems, but for Windows... undo is Control-z and redo is Shift-Control-z. You can do multiple undo and redo, as well. This is very handy, and again, we love it. And don't forget to align your indents with tab and shift-tab.
What can you say about the BabylonJS webGL rendering canvas, other than "IT IS THE COOLEST THING ON THE PLANET!". This right-side area of the playground is where the BabylonJS webGL framework attempts to render the scene that you currently have in the editor. Is the rendering canvas blank? Did you click the Run button? Have you got a camera? Is the camera aimed correctly? Do you have some lighting or an emissiveColor set on your mesh's material?
If your code is wrapped in a createScene() function, does it include var scene = new BABYLON.Scene(engine), near the top of the function? How about a return scene; line as the last line inside the function braces? Do you have some mesh like a box, cylinder, ground, sphere, plane, torus, torusknot, etc?
Are you running in free-flying mode and not wrapping your code in a createScene() function? That is certainly allowed, but you still need a camera, a light, and a mesh shape. These are a few things that can prevent your scene from rendering. Study the playground demo scenes listed under the drop-down Scene Selector button, and soon you will be a BabylonJS playground expert.
This is a picture of the playground's pop-up compilation error detector panel. A compilation error is an error detected by the BabylonJS framework... after you have clicked the Run button. It is not a syntax error detected by the editor, but the editor might ALSO detect it and possibly mark the problem line with a smale green icon along its right side. The compilation error does not always contain pertinent information about the reason for the error, yet it is still handy. It tells you that the BabylonJS framework is not happy with something in your scene code. After making an adjustment to your code, you need not close the compilation error pop-up. It should close automatically at the next RUN, if the error has been corrected.
When you first arrive at the BabylonJS playground web site, the URL in your browser's address field... will look like this:
If you choose one of the demo scenes from the drop-down Scene Selector button, the playground URL will change to this:
(Feel free to edit the code of the demo scenes and click Run and/or Save. You can't damage the pre-installed demos)
When you save a scene to the playground's database in order to share the URL with others or remember the scene for later, the URL will look something like this:
(Be sure to bookmark it, using your browser's bookmark system)
If you save that scene again... (maybe after doing more work on the scene), the URL will increment, and look like this:
If you save that scene again... the URL will increment, and look like this:
(Again, be sure to bookmark this URL so you can easily return to it later)
If you want to load a specific pre-installed demo scene, such as the #12 Particles demo, you can use a URL that looks like this:
Maintaining Your Focus
Sometimes, you will run a scene and use your cursor keys and mouse in the rendering canvas, and then want to 'focus' back to the editor... to make some more code changes. Often, you will need to mouse-click somewhere in the editor area to give the editor focus again. Once the editor has focus, your cursor keys will, once again, move the editor's cursor. This happens most often when a Babylon FreeCamera is the active camera.
Wrong Error Line-Numbers in Console The BJS Playground uses a "mini-fied" (compressed) version of BabylonJS, by default. This causes framework errors seen in the console... to have useless line numbers and click-throughs. If you wish to have GOOD line numbers and click-throughs for Playground console errors, activate the playground in debug mode. Use URLS like these:
And... That's A Wrap
Hey, thanks for reading this tutorial and for discovering the BabylonJS playground. We are very proud of it, and we think you will enjoy using it. This tutorial is still quite new, and will likely be changing often. Be sure to check back for updates and future features.
The BabylonJS Playground is located at... https://www.babylonjs-playground.com
Feel free to discuss the BabylonJS Playground, or any other BabylonJS framework topic... on our forum... located at: http://www.html5gamedevs.com/forum/16-babylonjs/