|
@@ -56,43 +56,42 @@ The University of Amsterdam (UvA) has provided access to a multi-touch table
|
|
|
from PQlabs. The table uses the TUIO protocol \cite{TUIO} to communicate touch
|
|
from PQlabs. The table uses the TUIO protocol \cite{TUIO} to communicate touch
|
|
|
events.
|
|
events.
|
|
|
|
|
|
|
|
-% Afbakening
|
|
|
|
|
-% TODO: moet dit omlaag naar 'Definition of the problem'?
|
|
|
|
|
-The scope of this thesis includes the design of an multi-touch triggering
|
|
|
|
|
-mechanism, a reference implementation of this design, and its integration into
|
|
|
|
|
-a VTK interactor. To be successful, the design should allow for extensions to
|
|
|
|
|
-be added to any implementation. The reference implementation is a Proof of
|
|
|
|
|
-Concept that translates TUIO events to some simple touch gestures that are used
|
|
|
|
|
-by a VTK interactor.
|
|
|
|
|
|
|
+ \section{Definition of the problem}
|
|
|
|
|
+
|
|
|
|
|
+ % Hoofdvraag
|
|
|
|
|
+ The goal of this thesis is to create a multi-touch event triggering mechanism
|
|
|
|
|
+ for use in a VTK interactor. The design of the mechanism must be universal.
|
|
|
|
|
+
|
|
|
|
|
+ % Deelvragen
|
|
|
|
|
+ To design such a mechanism properly, the following questions are relevant:
|
|
|
|
|
+ \begin{itemize}
|
|
|
|
|
+ \item What is the input of the mechanism? Different touch drivers have
|
|
|
|
|
+ different API's. To be able to support different drivers (which is
|
|
|
|
|
+ highly desirable), there should probably be a translation from the
|
|
|
|
|
+ driver API to a fixed input format.
|
|
|
|
|
+ \item How can extendability be accomplished? The set of supported events
|
|
|
|
|
+ should not be limited to a single implementation, but an application
|
|
|
|
|
+ should be able to define its own custom events.
|
|
|
|
|
+ \item Can events be shared with multiple processes at the same time? For
|
|
|
|
|
+ example, a network implementation could run as a service instead of
|
|
|
|
|
+ within a single application, triggering events in any application that
|
|
|
|
|
+ needs them.
|
|
|
|
|
+ \item Is performance an issue? For example, an event loop with rotation
|
|
|
|
|
+ detection could swallow up more processing resources than desired.
|
|
|
|
|
+ \end{itemize}
|
|
|
|
|
+
|
|
|
|
|
+ % Afbakening
|
|
|
|
|
+ The scope of this thesis includes the design of an multi-touch triggering
|
|
|
|
|
+ mechanism, a reference implementation of this design, and its integration
|
|
|
|
|
+ into a VTK interactor. To be successful, the design should allow for
|
|
|
|
|
+ extensions to be added to any implementation. The reference implementation
|
|
|
|
|
+ is a Proof of Concept that translates TUIO events to some simple touch
|
|
|
|
|
+ gestures that are used by a VTK interactor.
|
|
|
|
|
|
|
|
\section{Structure of this document}
|
|
\section{Structure of this document}
|
|
|
|
|
|
|
|
% TODO
|
|
% TODO
|
|
|
|
|
|
|
|
-\chapter{Definition of the problem}
|
|
|
|
|
-
|
|
|
|
|
-% Hoofdvraag
|
|
|
|
|
-The goal of this thesis is to create a multi-touch event triggering mechanism
|
|
|
|
|
-for use in a VTK interactor. The design of the mechanism must be universal.
|
|
|
|
|
-
|
|
|
|
|
-% Deelvragen
|
|
|
|
|
-To design such a mechanism properly, the following questions are relevant:
|
|
|
|
|
-\begin{itemize}
|
|
|
|
|
- \item What is the input of the mechanism? Different touch drivers have
|
|
|
|
|
- different API's. To be able to support different drivers (which is
|
|
|
|
|
- highly desirable), there should probably be a translation from the
|
|
|
|
|
- driver API to a fixed input format.
|
|
|
|
|
- \item How can extendability be accomplished? The set of supported events
|
|
|
|
|
- should not be limited to a single implementation, but an application
|
|
|
|
|
- should be able to define its own custom events.
|
|
|
|
|
- \item Can events be shared with multiple processes at the same time? For
|
|
|
|
|
- example, a network implementation could run as a service instead of
|
|
|
|
|
- within a single application, triggering events in any application that
|
|
|
|
|
- needs them.
|
|
|
|
|
- \item Is performance an issue? For example, an event loop with rotation
|
|
|
|
|
- detection could swallow up more processing resources than desired.
|
|
|
|
|
-\end{itemize}
|
|
|
|
|
-
|
|
|
|
|
\chapter{Preliminary inquiries}
|
|
\chapter{Preliminary inquiries}
|
|
|
|
|
|
|
|
\section{The TUIO protocol}
|
|
\section{The TUIO protocol}
|