Worked on report.

TODO.txt

@@ -7,6 +7,7 @@ Code:
 Report:
 - Add 'Results' Section to chapter 4.
 - Finish 'Conclusions' chapter.
+- Move TUIO appendix to chapter 4.
 
 Vragen Belleman:
 - Kan 'Conclusions' wel in H3, voordat experimenten zijn gedaan?

docs/report.bib

@@ -238,7 +238,7 @@
 	journal = "ACM Comput. Surv.",
 	keywords = "dblp",
 	number = 1,
-	pages = "13-16",
+	pages = "13--16",
 	title = "{A Characterization of Ten Hidden-Surface Algorithms.}",
 	url = "http://dblp.uni-trier.de/db/journals/csur/csur6.html#SutherlandSS74; http://doi.acm.org/10.1145/356625.356626; http://www.bibsonomy.org/bibtex/22bfef4fbc31892de2ab1bf8607514e2b/dblp",
 	volume = 6,
@@ -246,3 +246,9 @@
 	year = 1974
 }
 
+@misc{wikihashmap,
+	author = "Wikipedia",
+	howpublished = "\url{http://en.wikipedia.org/wiki/Hashmap}",
+	title = "{Hash map}"
+}
+

docs/report.tex

@@ -842,19 +842,30 @@ hand tracker assigns a finger to a hand after a \emph{point\_down} event, its
 touch point ID is saved in a hash map\footnote{In computer science, a hash
 table or hash map is a data structure that uses a hash function to map
 identifying values, known as keys (e.g., a person's name), to their associated
-values (e.g., their telephone number). Source:
-\url{http://en.wikipedia.org/wiki/Hashmap}} with the \texttt{Hand} object. When
-a finger moves (a \emph{point\_move} event) or releases the touch surface
-(\emph{point\_up}), The corresponding hand is loaded from the hash map and
-triggers a \emph{finger\_move} or \emph{finger\_up} gesture. If a released
-finger is the last of a hand, that hand is removed with a \emph{hand\_up}
-gesture.
+values (e.g., their telephone number). Source: Wikipedia \cite{wikihashmap}.}
+with the \texttt{Hand} object. When a finger moves (a \emph{point\_move} event)
+or releases the touch surface (\emph{point\_up}), The corresponding hand is
+loaded from the hash map and triggers a \emph{finger\_move} or
+\emph{finger\_up} gesture. If a released finger is the last of a hand, that
+hand is removed with a \emph{hand\_up} gesture.
 
 \section{Results}
 \label{sec:results}
 
 % TODO: Evalueer of de implementatie en testapplicaties voldoen aan de
 % verwachtingen/eisen die je hebt gesteld in je ontwerp.
+% - meerdere frameworks
+% - event area dient zijn doel
+% - Boomstructuur werkt goed, je moet alleen wel creatief zijn in hoe je hem
+%   maakt
+% - Er gaat werk zitten in het schrijven van de synchronisatielaag
+%   tussen architectuur en applicatieframework, maar dit is wel herbruikbaar id
+%   vorm van een vaste set classes
+% - gesture trackers houden code mooi gescheiden, en testapplicatie kan
+%   makkelijk eigen tracker toevoegen
+
+The test applications show that the architecture implementation can be used
+alongside existing application frameworks.
 
 \chapter{Conclusions}
 \label{chapter:conclusions}
@@ -885,6 +896,8 @@ A gesture trackers implementation is flexible, e.g. complex detection
 algorithms such as machine learning can be used simultaneously with other
 gesture trackers that use explicit detection.
 
+% TODO: Daemon implementatie
+
 % TODO: terugkomen op resultaten uit testimplementatie
 
 \chapter{Suggestions for future work}