Morsenger Processing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
[[Morsenger]] was developed from the ground up as an extensible application. | [[Morsenger]] was developed from the ground up as an extensible application. | ||
Internally, [[Morsenger]] maintains 2 | Internally, [[Morsenger]] maintains 2 separate data pipelines that automatically process incoming and outgoing transmissions. Data in the pipelines travels through a series of filters that transform selected data between different formats. | ||
* Input filters can take luminous changes from the Camera and IR sensor and sound from the microphone and pump [[ | * Input filters can take luminous changes from the Camera and IR sensor and sound from the microphone and pump [[Raw Data]] into the [[Input Pipeline]]. | ||
* Filters on the [[Input Pipeline]] transform the data between [[Ascii Text]], [[Morse Code]], [[Abbreviation]]s and [[Bit Stream]]s. | * Filters on the [[Input Pipeline]] transform the data between [[Ascii Text]], [[Morse Code]], [[Abbreviation]]s and [[Bit Stream]]s. | ||
* Any [[Ascii Text]] received from the [[Input Pipeline]] is displayed as an incoming message. | * Any [[Ascii Text]] received from the [[Input Pipeline]] is displayed as an incoming message. | ||
* Text from the [[Send Button]] is pumped | * Text from the [[Send Button]] is pumped to the [[Output Pipeline]]. | ||
* Filters on the [[Output Pipeline]] transform the data between [[Ascii Text]], [[Morse Code]], [[Abbreviation]]s and [[Bit Stream]]s. | * Filters on the [[Output Pipeline]] transform the data between [[Ascii Text]], [[Morse Code]], [[Abbreviation]]s and [[Bit Stream]]s. | ||
* Other filters take [[Bit Stream]] data from the [[Output Pipeline]] and produce audio, camera flashes etc. | * Other filters take [[Bit Stream]] data from the [[Output Pipeline]] and produce audio, camera flashes etc. | ||
* Additional filters tap into data flowing through the [[Input Pipeline]] to visualise incoming transmissions. | |||
All input, output, data processing and transformation is handled as background tasks. | All input, output, data processing and transformation is handled as background tasks. |
Revision as of 11:38, 30 May 2017
Morsenger was developed from the ground up as an extensible application.
Internally, Morsenger maintains 2 separate data pipelines that automatically process incoming and outgoing transmissions. Data in the pipelines travels through a series of filters that transform selected data between different formats.
- Input filters can take luminous changes from the Camera and IR sensor and sound from the microphone and pump Raw Data into the Input Pipeline.
- Filters on the Input Pipeline transform the data between Ascii Text, Morse Code, Abbreviations and Bit Streams.
- Any Ascii Text received from the Input Pipeline is displayed as an incoming message.
- Text from the Send Button is pumped to the Output Pipeline.
- Filters on the Output Pipeline transform the data between Ascii Text, Morse Code, Abbreviations and Bit Streams.
- Other filters take Bit Stream data from the Output Pipeline and produce audio, camera flashes etc.
- Additional filters tap into data flowing through the Input Pipeline to visualise incoming transmissions.
All input, output, data processing and transformation is handled as background tasks.