Figure 3. CGI Studio Process Flow
Active scene is always rendered using a WYSIWYG approach. As a result, it is possible to visually inspect the imported graphics assets early in the development. Moreover, object properties can be dynamically changed in the active scene to get immediate results and timely evaluation.
This CGI module runs the output of the Scene Composer. Candera Engine can run either on the host or on the actual target. It supports both 2D and 3D, thereby allowing one tool for both types of developments
Candera 2D engine supports dynamic scene graph. It supports 2D animations, including smooth rotation, scaling, and translation of bitmaps. In order to enable seamless integration, the 2D engine supports interaction with the 3D engine in a number of ways.
For example, it supports render to texture, can post-process 3D images, and can combine scenes with 3D, etc. In addition to that, it supports hardware layers, multiple displays, alpha blending, 2D widgets, and text rendering.
Candera 3D engine is based on OpenGL-ES 2.0 and is fully compliant with the standard specification. It has been designed to be OS, application, and hardware agnostic.
Its key functions are screen and scene management, handling 3D objects and their processing, animation framework, and asset management in the embedded system’s memory. It also optimizes render order and state management.
One of the key modules is the Player. It runs the generate application on the host as well as on the target. As a result, it is possible to see verify the application on the host even before it is deployed on the target. This is also helps in verifying the widget design.
CGI Studio also has some other modules that bring distinct advantages to the table. Courier is an interaction framework that handles data binding and messaging with the host system, thus allowing smooth integration