Architecture - Revision history

Tectu: /* Modules */

2016-03-04T13:50:34Z

‎Modules

2014-07-05T11:22:17Z

‎Configuration

2014-07-03T21:42:19Z

‎Initialization

2014-07-03T21:41:03Z

2014-07-03T01:20:42Z

2014-07-02T21:04:52Z

‎Modules

2014-07-02T21:04:38Z

‎Modules

2014-07-02T21:03:42Z

‎Modules

2014-07-02T11:11:56Z

2014-07-02T11:10:21Z

‎Modules

@@ Line 7: / Line 7: @@
 == Modules ==
 Although there are many modules available, most of those are used internally and are not relevant for common application building. The main modules with which a user will usually interact are:
 * GWIN
 * GEVENT
 * GAUDIO
 However, the user has full access to the other modules as well as they can simplify development of an application. One of these examples is the [[GQUEUE]] module. It provides (a)syncronous queues and buffers which can be a great help for some users.

@@ Line 54: / Line 54: @@
 == 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.
+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 behavior of the module but also extend its features and capabilities.
 == Initialization ==

@@ Line 57: / Line 57: @@
 == Initialization ==
-The entire library is initialized by calling <code>gfxInit()</code. All modules will automatically be initialized if they have been enabled in the configuration file.
+The entire library is initialized by calling <code>gfxInit()</code>. All modules will automatically be initialized if they have been enabled in the [[Configuration|configuration file]].
 [[Category:General]]

← Older revision		Revision as of 21:41, 3 July 2014
Line 55:		Line 55:
	== Configuration ==		== 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.		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.
		+
		+	== Initialization ==
		+	The entire library is initialized by calling <code>gfxInit()</code. All modules will automatically be initialized if they have been enabled in the configuration file.
		+
		+
		+
		+	[[Category:General]]

@@ Line 2: / Line 2: @@
 The library is split into different [[#modules|modules]]. Each module is responsible for a specific task such as [[GDISP|driving an LCD]], [[GINPUT|reading user inputs]] or [[GFILE|handling files]].
 The image to the right shows the architecture of a typical user application. Note that there are many more modules that are used internally and therefore not shown in the graphic.
 == Modules ==

@@ Line 10: / Line 10: @@
 * GEVENT
 * GAUDIO
-However, the user has full access to the other modules as well as they can simplify development of an application. One of these examples is the [[GQUEUE]] modules. It provides (a)syncronous queues which can be a great help for some users.
+However, the user has full access to the other modules as well as they can simplify development of an application. One of these examples is the [[GQUEUE]] module. It provides (a)syncronous queues which can be a great help for some users.
 The following modules are available:

@@ Line 1: / Line 1: @@
 [[File:architecture2.png|500px|right|Overall µGFX architecture. Not showing all modules.]]
-The library is split into different modules. Each module is responsible for a specific task such as [[GDISP|driving an LCD]], [[GINPUT|reading user inputs]] or [[GFILE|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.
+The library is split into different [[#modules|modules]]. Each module is responsible for a specific task such as [[GDISP|driving an LCD]], [[GINPUT|reading user inputs]] or [[GFILE|handling files]].
-Each of these modules has to be enabled in the [[Configuration|configuration]] file before it can be used.
+The image to the right shows the architecture of a typical user application. Note that there are many more modules that are used internally and therefore not shown in the graphic.
 == Modules ==