When Koru exports a scene, it wraps it up in some HTML called “template”. Template decides whether the scene will be fullscreen or not, template customizes snapshot buttons and can do some other scene control. Finally, template may simply add your logotype to the caption of the page. Any time you need a custom HTML output in Koru, you make a template.
You can read more about templates here, but best of all you don’t really need to start from scratch. Koru comes with a couple of pre-defined templates that you can use to kick-start your own. Let’s clone one of the existing ones now.
Start Koru and click its File menu. In the drop-down list select Open Templates Library item. You will see a folder on your disk where Koru stores its templates. Find a folder called mini-widget and make a clone of it. On Mac you need to right-click it and select Duplicate, on Windows you can simply copy and paste it. Rename the new folder to image-uploader and enter that folder.
You will see three files inside:
Open _readme.txt with your text editor and modify its first line, so it contains just two words “Image Uploader”, then replace the rest of the file with a brief description of what this template is for. The end result should look like this:
Image Uploader This template lets your users configure material named "Image". They can upload their own images there and change its color.
Save the file, then switch back to Koru and make a simple scene. Then try to export it to disk. You should see your new preset in the list:
Note that the first line of the text file you edited became the name of the preset in the list, and the rest of the text file is now displayed at the right as a description. We didn’t change the preview image, so it is the same as for “Minimalistic DIV” template that we initially cloned, but you can later replace it with any square image you want.
Once again, you can read more about the contents of this file here, we will not focus on that in this tutorial. What we need is to add two controls that let your users upload images and change color. Locate the line:
And add the following lines right below that line:
<p> <label>Select Image:</label> <input type="file" accept="image/*" id="file-picker"/> </p> <p> <label>Select Color:</label> <input type="color" value="#fff" id="color-picker"/> </p>
If you export a scene with this template now, you will see file and color pickers above the 3D model:
You can style them up with CSS, but this runs out of scope of this tutorial. The next step is to add handlers to these buttons, so clicking them changes the scene.
Locate these two lines at the end of the template:
Add some empty lines between these two and put the following code there:
The code defines two functions: koruInit() and onLoadEnd(). The first gets called when the Koru engine has loaded, but the scene itself is not loaded yet. It is too early to look for our material yet, so we ask Koru to let us know when the scene is loaded. To do that we add a listener for “loadend” event that Koru sends after loading the scene.
When the scene is loaded Koru calls our onLoadEnd() function that gets the Koru engine from the event parameter. Then it looks for material named “Image” and fails if it doesn’t find it or if it has no layers. Finally, it gets the layey variable that we’ll be changing later.
After that it gets file and color pickers and assign handlers for their “onchange” events. The handlers will be called when user changes color or selects a file. In both handlers we assign image and color to layer’s properties, update the layer and ask Koru to redraw the scene.
Important: in order for the code above to work you need a material named “Image” in the scene, this material needs to have at least one layer, its first layer needs to be enabled, its diffuse block needs to be enabled and it needs to have a default diffuse texture. The first part is obvious, as the code looks for the material by name and accesses its very first layer. The default texture may not be that obvious, but as Koru tries to optimizes exported scenes, it exports slightly different code if there is no default texture to speed up the rendering. Because of that, Koru expects that if there was no texture at export time, there will be no texture in run time. To avoid this, you need to export scene with default textures for the properties you are going to change.
Here is a zip-file with the template described above. Unpack it to your templates folder to get the same result without typing a word.
It wasn’t that difficult, right? Combine this with a screenshot button from another tutorial below and get a simple online 3D mockup tool!