gnh1201/wasm-micro-runtime
1
0
Fork 0
mirror of https://github.com/bytecodealliance/wasm-micro-runtime.git synced 2024-10-16 13:02:32 +00:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity

update wgl readme

Browse Source
This commit is contained in:
Wang Xin 2020-04-12 22:53:10 +08:00 committed by GitHub
parent bf8fbee92e
commit 42d982e431
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
core/app-framework/wgl/readme.MD
View File

@ -1,31 +1,32 @@
WASM Graphic Layer (WGL) 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. 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 # 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: 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 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. 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.
When multiple WASM apps are creating their own UI, the object will be also validated for his owner module instance. 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 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.
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 3. Pass function arguments in stucture pointers
We have to do serialization for the structure passing between the WASM and native. We have to do serialization for the structure passing between the WASM and native.
4. Callbacks 4. Callbacks
# API compatibility with littlevgl # 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. 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.
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; typedef void lv_obj_t;
''' '''
@ -47,7 +48,7 @@ The script is also automatically executed after downloading the lvgl repo in the
# How to extend a little vgl wideget # 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. 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 other widgets. Refer to the implementation of these widgets for extending more widgets.