Jump to content

Contributions:Extensions: Difference between revisions

From BCI2000 Wiki
Gmilsap (talk | contribs)
Created the Contributions:Extensions page
 
Jhill (talk | contribs)
No edit summary
Line 1: Line 1:
A framework ''Extension'' is an optional contributed plugin which can affect multiple modules.  For example, various manufacturer-specific  [[User Reference:Logging Input|input-device loggers]] are provided in the <code>src/contrib/Extensions</code> folder, and these can be optionally added to the BCI2000 framework for SignalSource modules, thereby giving all source modules the ability to log input from the corresponding devices.  Selecting a custom Extension, and re-building your modules to include it, requires the use of CMake and a supported C++ compiler:  see the [[Programming Howto:Quickstart Guide]] for a walkthrough that shows you how to recompile BCI2000 modules.
The following user extensions are available in the [[Contributions:Contents|Contributions]] section of BCI2000:
The following user extensions are available in the [[Contributions:Contents|Contributions]] section of BCI2000:



Revision as of 19:40, 15 June 2011

A framework Extension is an optional contributed plugin which can affect multiple modules. For example, various manufacturer-specific input-device loggers are provided in the src/contrib/Extensions folder, and these can be optionally added to the BCI2000 framework for SignalSource modules, thereby giving all source modules the ability to log input from the corresponding devices. Selecting a custom Extension, and re-building your modules to include it, requires the use of CMake and a supported C++ compiler: see the Programming Howto:Quickstart Guide for a walkthrough that shows you how to recompile BCI2000 modules.

The following user extensions are available in the Contributions section of BCI2000:

See also

Programming Reference:EnvironmentExtension Class

Programming Tutorial:Implementing an Input Logger