Confirmed users
770
edits
| Line 82: | Line 82: | ||
===WebImage:=== | ===WebImage:=== | ||
The WebImage is a high level library for image processing and analysis library. Would not address too much in this wiki page right now. I | The WebImage is a high level library for image processing and analysis library. Would not address too much in this wiki page right now. I am focusing on the worker part in current stage.<br> | ||
The underlying implementation of this library can be asm.js or native code which depend | The underlying implementation of this library can be asm.js or native code which depend the performance need. Some features in asm.js might run poorly in B2g. We will do some experiments like the performance comparison between OpenCV-asm.js and native OpenCV in B2G. We might need WebImage for HW accelerator case. For example, we can provide some built-in detection functions like face detection. | ||
In summary, if the performance is not any consideration, we will use asm.js version as much as we can. So the judgement will be the performance need. For example, if we need text recognition in B2G and the performance is critical and the asm.js version of tesseract can't run smoothly, then we go to native built-in way. | |||
<br> | <br> | ||
[[File:Project FoxEyeWebImage1.png]]<br> | [[File:Project FoxEyeWebImage1.png]]<br> | ||
Why do we need WebImage: | |||
* | *For performance critical cases. | ||
*No need of changes in AP for optimization in particular platform: For example, we can use vendor's face detector in camera on B2G. Or native codes version in B2G if there is any memory/performance concern. | *No need of changes in AP for optimization in particular platform: For example, we can use vendor's face detector in camera on B2G. Or native codes version in B2G if there is any memory/performance concern. | ||
* | *Can be cross platforms: Can run asm.js version in all platforms/browser. | ||
===Offline MediaStream:=== | ===Offline MediaStream:=== | ||