gnh1201/wasm-micro-runtime
1
0
Fork 0
mirror of https://github.com/bytecodealliance/wasm-micro-runtime.git synced 2024-11-26 15:32:05 +00:00
Code Issues Actions 14 Packages Projects Releases Wiki Activity
13875f43c6
wasm-micro-runtime/core/app-framework/wgl
History
Wenyong Huang 32242988ed
Apply clang-format for more source files (#795) 
Apply clang-format for C source files in folder core/app-mgr,
core/app-framework, and test-tools.
And rename folder component_test to component-test, update
zephyr build document.

Signed-off-by: Wenyong Huang <wenyong.huang@intel.com>
2021-10-21 13:58:34 +08:00
..
app Apply clang-format for more source files (#795) 2021-10-21 13:58:34 +08:00
native Apply clang-format for more source files (#795) 2021-10-21 13:58:34 +08:00
readme.MD Merge branch 'master' into master 2020-04-13 11:05:54 +08:00

readme.MD

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 make the WASM application small footprint. Another option is to build 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 littlevgl API exporting:

  1. Reference to the widget object

    Almost each littlevgl API takes the widget object as the first argument, which leads to either reading or writing the data associated with the object in native space. We have to prevent the WASM app utilize this method to access unauthorized memmory address.

    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 implementing 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 should also validated for its owner module instance.

  2. Access the object properties

    As 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 since 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; '''

Prepare the lvgl header files for WASM applicaitons

Run the below script to setup the lvgl header files for the wasm appliation.

core/app-framework/wgl/app/prepare_headers.sh

The script is also automatically executed after downloading the lvgl repo in the wamr-sdk building process.

How to extend a little vgl wideget

Currently the wgl has exported the API for a few common used widgets such as button, label etc.

Refer to the implementation of these widgets for extending more widgets.