@ThorstenBux @EdwardLu2018 i'm testing a new class that i created inside WebARKitLib see here in my testing branch feature-webarkittrackers . You can see the WebARKitOrbTracker.cpp that implement the necessary functions for initializing and to track.
WebARKitOrbTracker is a class, but i think we should implement a base class that may serve as base class for all future trackers. I also created a WebARKitUtils.h file to store functions that can be shared by trackers. For example we could store the im_gray(uchar data[], size_t cols, size_t rows) and maybe other functions.
There is also an example, but it only provide a test to verify the setup. It is just a beginning, a lot of work must be done! 😄
At least i can say the project may be built without errors, from emscripten....

I will share with you some thoughts:

• Bundler
  Actually i'm using webpack as a bundler, but we are free to use another bundler, for example Rollup or Parcel. We should understand what better fits our needs.

• Entry point of the library:
  At the moment we export as a module the two WebARKit and WebARController in the index.js file

  webarkit-testing/src/index.js

  Lines 1 to 6 in 7034e6d

  	import WebARKit from './WebARKit'
  	import WebARKitController from './WebARKitController'
  	export default {
  	WebARKit, WebARKitController
  	}

  
  Does it is what we want/needs?
  in CommonJS code to initalize the module you need

  webarkit-testing/examples/example.html

  Lines 11 to 14 in 7034e6d

  	WebARKit.WebARKitController.init().then(wark => {
  	wark.webarkit.test();
  	wark.initTracking()
  	})

  
  maybe better would be write:
  WebARKitController.init().then(wark => {
  but this is not allowed because the lib is exported in that way.

This list is not complete, i will update while issues will emerge in the development.

While testing on Mobile(Android) i get:

RuntimeError: Aborted(RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance)
    at mA (WebARKit.js:2:22558)
    at WebARKit.js:2:25463
onError @ worker.js:42
Promise.catch (async)
initTracker @ worker.js:47
self.onmessage @ worker.js:11

this is caused because the Memory option

As said in #10 i get sometimes this error:

__resumeException WebARKit.js:2

  $emscripten::internal::MethodInvoker<void (WebARKit::*)(emscripten::val, ColorSpace), void, WebARKit*, emscripten::val, ColorSpace>::invoke(void (WebARKit::* const&)(emscripten::val, ColorSpace), WebARKit*, emscripten::_EM_VAL*, ColorSpace) 00d78de6:0x12cf0
  WebARKit$processFrame VM21:10
  value WebARKit.js:2
  value WebARKit.js:2
  processFrame  worker.js:53
  self.onmessage

Note that this happens only on Mobile device.