X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;ds=sidebyside;f=methods.tex;h=e25809c7034ec18fa86a88fbf8f1918e3d4e0f4c;hb=a0fc5b24e17c83d05fa5cb95e855e784abac8f3e;hp=8b5b1fe6c32bedc66275e8e27272260d238fbddf;hpb=50bd4ce74dd1fe83cadc14e7c0736c1e75605961;p=msc-thesis1617.git

diff --git a/methods.tex b/methods.tex
index 8b5b1fe..e25809c 100644
--- a/methods.tex
+++ b/methods.tex
@@ -1,53 +1,8 @@
-\section{\acrlong{TOP}}
-\gls{TOP} is a recent new programming paradigm implemented as
-\gls{iTasks}~\cite{achten_introduction_2015} in
-the pure lazy functional language \gls{Clean}
-
-\todo{Main terms}
-The lazy functional programming language based on graph rewriting
-\gls{Clean}~\cite{brus_cleanlanguage_1987}
-
-\section{\acrlong{EDSL}s}
-\glspl{mTask} are expressed in a class based shallowly embedded \gls{EDSL}.
-There are two main types of \glspl{EDSL}.
-\todo{Small shallow embedded dsl intro}
-\todo{Small deep embedded dsl}
-\todo{Show that class based has the best of both worlds}
-
-\section{Devices}
-The client code for the devices is compiled from one codebase. For a device to
-be eligible for \glspl{mTask} it must be able to compile the shared codebase
-and implement (part of) the device specific interface. The shared codebase only
-uses standard \gls{C} and no special libraries or tricks are used. Therefore
-the code is compilable for almost any device or system. Note that it is not
-needed to implement a full interface\todo{handshake}. The full interface,
-listed in Appendix~\label{app:device-interface}\todo{update interface listing},
-also includes functions for accessing the peripherals that not every device
-might have. Devices can choose what to implement by setting the correct macros
-in the top of the file.
-
-\subsection{Specification}
-Devices are stored in a record type and all devices in the system are stored in
-a \gls{SDS} containing all devices. From the macro settings in the interface
-file a profile is created for the device that describes the specification. When
-a connection between the server and a client is established the server will
-send a request for specification. The client will serialize his specs and send
-it to the server so that the server knows what the client is capable of. The
-exact specification is listed in Listing~\ref{lst:devicespec}
-
-\begin{lstlisting}[language=Clean,label={lst:devicespec},
-	caption={Device specification for \glspl{mTask}}]
-:: MTaskDeviceSpec =
-	{haveLed :: Bool
-	,haveAio :: Bool
-	,haveDio :: Bool
-	,taskSpace :: Int // Bytes
-	,sdsSpace  :: Int // Bytes
-	}
-\end{lstlisting}
-\todo{Explain specification, combine task and share space}
+\input{methods.top.tex}
 
-\subsection{Communication}
+\input{methods.dsl.tex}
+
+\input{methods.arch.tex}
 
 \section{mTasks}
 \subsection{\gls{EDSL}}
@@ -101,3 +56,18 @@ have a unique numeric identifier and an initial value.
 sdsStore :: Shared [MTaskShare]
 \end{lstlisting}
 \todo{Do something with the sharetype}
+
+\subsection{Communication}
+%\todo{Handshake, device specification sending, spec.c}
+%\todo{mTaskDevice class interface}
+
+\section{mTasks}
+\subsection{\gls{EDSL}}
+\todo{Show the classes}
+
+\subsection{Shares}
+\todo{Show the types and why}
+
+Shares are used to store the values 
+
+Shares all have