-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add introduction to Plugins documentation
- Loading branch information
1 parent
35d3033
commit 8447542
Showing
1 changed file
with
18 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
<!doctype html> | ||
<HTML> | ||
<HEAD> | ||
<meta charset="UTF-8"> | ||
|
||
<Title>Plugins</Title> | ||
</HEAD> | ||
<BODY> | ||
<h1>Plugins</h1> | ||
<p>In the following sections, all the plugins available in the AsTeRICS framework will be presented. The plugins can be divided in 3 groups: sensor modules, processing modules and actuator modules.</p> | ||
<ul> | ||
<li><EM>Sensors</EM> include all software modules which make physical or simulated data available to other AsTeRICS plugins. Examples include a digital switch interface, an analogue sip/puff sensor, a webcam or a signal generator.</li> | ||
<li><EM>Processors</EM> include mathematical transformations, feature detectors, threshold level monitors etc. which are necessary to scale or combine signals or detect interesting events in the data streams acquired from the sensors.</li> | ||
<li><EM>Actuators</EM> enable assistive functionalities like mouse- or keyboard replacement, visual or acoustic feedback or direct interaction with the environment, e.g. infrared remote control, home automation or physical manipulation.</li> | ||
</ul> | ||
<p>The plugins represent the functional blocks of AsTeRICS. They can be combined to tailored Assistive Technology setups via the graphical AsTeRICS Configuration Suite software application (ACS), where plugins can be selected, connected via channels, and parameterized. Thus, the ACS can be considered as a user friendly environment to arrange the plugins. The result of this configuration process is an .xml file containing the deployment model for the AsTeRICS Runtime Environment (ARE).</p> | ||
</BODY> | ||
</HTML> |