Architecture

The library is split into different modules. Each module is responsible for a specific task such as driving an LCD, reading user inputs or handling files. There are also many modules that are available to the user but that are not necessary to build an application. Such a module is for example the GQUEUE module which provides (a)synchronous queues, buffers and more. Each of these modules has to be enabled in the configuration file before it can be used.

Modules

The following modules are available:

Module	Description
GDISP	Module to interface graphic displays including high-level drawing API. See GDISP.
GINPUT	Module to interface user interaction peripherals such as touchscreen and buttons. See GINPUT.
GWIN	Complete GUI toolkit. See GWIN
GAUDIO	Modules to play and record audio. See GAUDIO.
GFILE	Module to interface many different types of file systems through the same API. See GFILE.
GEVENT	Event handling module. Used internally to couple the GINPUT an the GWIN module together. See GEVENT.
GTIMER	Module providing software timers. Used internally. See GTIMER
GQUEUE	Module which provides (a)synchronous queues, buffers and more. Used internally. See GQUEUE.
GOS	Module which provides the interface to abstract many different underlying systems (OSes). This is used when porting the library to a new system. See GOS.
GADC	Module to provide a common API for analog interface to the library. Used internally. See GADC.
GMISC	Module containing miscellaneous features such as look-up tables for trigonometry functions, array operations and more. Used internally. See GMISC.

Configuration

Each module has to be enabled in the configuration file before it can be used. Most modules do furthermore provide options that can not only manipulate the behaviour of the module but also extend its features and capabilities.