Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
M
multitouch
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Taddeüs Kroes
multitouch
Commits
eff87d8d
Commit
eff87d8d
authored
Jun 02, 2012
by
Taddeüs Kroes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Moved 'Definition of the problem' to 'Introduction'.
parent
c5b29a5a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
31 additions
and
32 deletions
+31
-32
docs/report.tex
docs/report.tex
+31
-32
No files found.
docs/report.tex
View file @
eff87d8d
...
...
@@ -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
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
}
% 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
}
\section
{
The TUIO protocol
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment