gnh1201/wasm-micro-runtime
1
0
Fork 0
mirror of https://github.com/bytecodealliance/wasm-micro-runtime.git synced 2025-05-12 04:31:14 +00:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity
66d6a3986a
wasm-micro-runtime/core/app-framework/wgl/wgl.md
Wang Xin 66d6a3986a refactor the lvgl wasm api layer
2020-04-12 14:19:23 +08:00

2.1 KiB
Raw Blame History

WASM Graphic Layer (WGL)

The WGL builds the littlevgl v6.0 into the runtime and exports a API layer for WASM appication programming graphic user interfaces. This approach will makes the WASM application small footprint. Another option will be built the whole littlevgl library into WASM, which is how the sample littlevgl is implemented.

Challenges

When the littlevgl library is compiled into the runtime, all the widget data is actually located in the runtime native space. As the WASM sandbox won't allow the WASM application to directly access the native data, it introduced a few problems for the API porting:

  1. Reference to the widget object Almost each littlevgl API will take widget object as the first argument, which leads to either read or write the data associated with the object. We have to prevent the WASM app utilize this to access unauthorized the memmory.

    The solution is to track the objects created by the WASM App in the native layer. Every access to the object must be validated in advance. To simplify each native wrapper function, the wgl_native_func_call() will do the validation for the object presented in the first argument.

    When multiple WASM apps are creating their own UI, the object will be also validated for his owner module instance.

  2. Access the object properties The data structure of widget objects is no longer visible to the applications. The app has to call APIs to get/set the properties of an object.

  3. Pass function arguments in stucture pointers We have to do serialization for the structure passing between the WASM and native.

  4. Callbacks

API compatibility with littlevgl

We wish the application continue to use the littlevgl API and keep existing header files inclusion, however it is also a bit challenging.

Firstly we have to redefine some data types such as lv_obj_t in the APIs exposed to the WASM app. ''' typedef void lv_obj_t; '''

Secondly, as the littlevgl source code is no longer compiled and linked with the WASM app source codes, the compilation won't be successfully while including the original littvgl header files.