From ce13929835e8fd9536f9ff1010e711fcf1a1d00b Mon Sep 17 00:00:00 2001 From: Mart Lubbers Date: Mon, 21 Dec 2015 15:11:08 +0100 Subject: [PATCH] added tools section --- marsrover/document/preamble.tex | 2 +- marsrover/document/robot.tex | 32 +++++++++++++++++++++++--------- marsrover/document/todo.txt | 8 ++++---- 3 files changed, 28 insertions(+), 14 deletions(-) diff --git a/marsrover/document/preamble.tex b/marsrover/document/preamble.tex index 64b86e6..a9af18f 100644 --- a/marsrover/document/preamble.tex +++ b/marsrover/document/preamble.tex @@ -20,5 +20,5 @@ \pagestyle{fancy} \renewcommand{\headrulewidth}{0pt} -\fancyhead[RF]{\small\textsc{DES2015: Mart Natanael (\today). Page: \thepage}} +\fancyhead[RF]{\small\textsc{DES2015: Mart \& Natanael. Page: \thepage}} \fancyhead[CF,RH]{} diff --git a/marsrover/document/robot.tex b/marsrover/document/robot.tex index bf0d685..f6d0323 100644 --- a/marsrover/document/robot.tex +++ b/marsrover/document/robot.tex @@ -1,14 +1,28 @@ \section{Robot architecture} \subsection{Tools} -\emph{LeJOS}~\cite{lejos_team_lejos_2015} - -\emph{XText} - -\emph{eclipse} - -\emph{Antlr} - -\emph{Xtend} +\paragraph{\emph{LeJOS}~\cite{lejos_team_lejos_2015}} is an alternative +operating system for the \textsc{lego}$^{\small\textcopyright}$ \textsc{EV3} +bricks. By default the bricks come preinstalled with their own operating system +in which you can write programs. The programs have to be written in a +\textsc{C} dialect or in a graphical programming tool. \emph{LeJOS} on the +other hand is a constantly developed toolkit to write the programs in Java. +Because of this we can reuse Java standard libraries and program in a familiar +language that allows enough detail for the task. + +\paragraph{\emph{XText}, \emph{XTend} and \emph{Antlr}} are a collection of +tools working together to provide the functionality for writing, parsing, +generating and validating the DSL. \emph{XText} is the format used to write the +concrete syntax in. The \emph{XText} syntax is converted to a so called +\emph{ecore} model which can be read by \emph{XTend} programs. \emph{XTend} +program can do code generation and validation. All the parsing is done by the +parser generator library \emph{Antlr}. + +\paragraph{\emph{eclipse}} is the integrated development environment that ties +all the tools together. The DSL is developed in \emph{eclipse} and when the +language infrastructure is generated you can open a new instance of +\emph{eclipse} to write the actual DSL code in. In this way the user of the +child-instance of \emph{eclipse} has no view on the underlying mechanisms +generating the code and processing the data. \subsection{Design patterns} \subsubsection{Producer-Consumer} diff --git a/marsrover/document/todo.txt b/marsrover/document/todo.txt index e3512ee..b6316c8 100644 --- a/marsrover/document/todo.txt +++ b/marsrover/document/todo.txt @@ -1,14 +1,14 @@ 1. Requirements -done i think +done 2. Robot -mart Tools +done Tools adit DSL description adit Code structure, what do we generate? 3. Development Plan & Evaluation -done Development Plan - + Development Plan +done Evaluation todo Realisation: what features implemented todo What would we do different given more time? -- 2.20.1