Using Armory as a library, not as an engine

zicklag · January 24, 2019, 7:32pm

About the WASM API being limited, I think it might be possible to get around that and expose the entire Kha, Iron, and Armory APIs to WASM. I don’t really know WASM, but here is the script that loads the WASM traits:

github.com

armory3d/armory/blob/master/Sources/armory/trait/internal/WasmScript.hx

package armory.trait.internal;

#if js

import iron.data.Data;
import iron.data.Wasm;
import iron.system.Input;
import iron.system.Time;

class WasmScript extends iron.Trait {
	var wasm:Wasm;

	var objectMap:Map<Int, iron.object.Object> = new Map();

	public function new(handle:String) {
		super();

		// Armory API exposed to WebAssembly
		// TODO: static
		/*static*/ var imports = {

This file has been truncated. show original

It manually builds out that limited list of functions in the imports and gives it to the WASM module so that it can call what is exposed. Right now that API is manually provided in this script, but it could be possible to automatically generate the imports for the entire Armory API with Haxe macros.

I’ve done something similar before, where you compile Armory, and use a custom Haxe macro to hook into the parsed Haxe classes at compile time and generate your own bindings to the API. It might be a little difficult to support the entire Armory API through a WASM interface; you might run into some issues that I’m unaware of just because of how Haxe is designed, but it might be worth a shot. I don’t have the time to do this right now, but it could be something to consider if anybody else is interested.