|
|
|
_How to build source for incore images and fonts, and load them for your MiniGUI apps._
|
|
|
|
|
|
|
|
Table of Contents
|
|
|
|
|
|
|
|
- [Overview](#overview)
|
|
|
|
- [Tools for Generating Incore Data](#tools-for-generating-incore-data)
|
|
|
|
- [APIs for Managing Incore Data](#apis-for-managing-incore-data)
|
|
|
|
- [Restrictions](#restrictions)
|
|
|
|
|
|
|
|
## Overview
|
|
|
|
|
|
|
|
## Key Points
|
|
|
|
We often want to embed the raw data of images and/or fonts into the final executable
|
|
|
|
of a MiniGUI app:
|
|
|
|
|
|
|
|
- The operating system does not provide support for file system.
|
|
|
|
- You want to protect your digital intellectual properties such as icons.
|
|
|
|
|
|
|
|
For this purpose, MiniGUI provides a set of APIs and tools to embed the arbitrary
|
|
|
|
data into the final executable.
|
|
|
|
|
|
|
|
Note that, in MiniGUI term, we often call the embedded data as `incore data`,
|
|
|
|
`incore resource`, or `inner resource`.
|
|
|
|
|
|
|
|
For a complete sample, please refer to:
|
|
|
|
|
|
|
|
<https://github.com/VincentWei/mg-samples/tree/master/incore-data>
|
|
|
|
|
|
|
|
## Tools for Generating Incore Data
|
|
|
|
|
|
|
|
## APIs for Managing Incore Data
|
|
|
|
|
|
|
|
## Restrictions
|
|
|
|
|
|
|
|
TBC... |
|
|
\ No newline at end of file |
