-In \emph{Task Oriented Programming} (TOP) a program is built out of pieces of
-work called \emph{tasks}~\cite{achten_introduction_2015}. Tasks differ from
-function in the way that they return a result. A task's return value can change
-over time. Task exist in many forms and they can be composed sequentially and
-in parallel. Some possible tasks are asking for user input via a web browser,
-setting up a TCP connection to another server or combining several tasks. At
-the moment there are several types of leaf tasks. A leaf task is a task that
-does not consist of tasks itself. Examples of leaf tasks are the so called
-editors.
+In \emph{Task Oriented Programming} (TOP) a program is constructed out of
+pieces of work called \emph{tasks}~\cite{achten_introduction_2015}. Tasks
+differ from function in the way that they return a result. A task's return
+value can change over time. Task exist in many forms and they can be composed
+sequentially and in parallel. Some possible tasks are asking for user input via
+a web browser, setting up a TCP connection to another server or combining
+several tasks. At the moment there are several types of leaf tasks. A leaf task
+is a task that does not consist of tasks itself. Examples of leaf tasks are
+the so called editors.
This paper describes the effort to add another type of leaf task that
focusses on microcontrollers. Microcontrollers are often not powerful
abstract away from communication techniques and it should be relatively easy to
add techniques. Techniques that are interesting to experiment with is Serial
communication, Bluetooth, \textsc{WiFi}, \textsc{GSM} and \textsc{LoRa}.
+
+\mTask{}s describe a task in an imperative way and allow the functionality of
+the embedded device to be attached to an \iTasks{} system.
repositories / ri1617.git / blobdiff