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
6c12d81a
Commit
6c12d81a
authored
Jul 05, 2012
by
Taddeüs Kroes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Worked on report.
parent
28c48d54
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
28 additions
and
8 deletions
+28
-8
TODO.txt
TODO.txt
+1
-0
docs/report.bib
docs/report.bib
+7
-1
docs/report.tex
docs/report.tex
+20
-7
No files found.
TODO.txt
View file @
6c12d81a
...
@@ -7,6 +7,7 @@ Code:
...
@@ -7,6 +7,7 @@ Code:
Report:
Report:
- Add 'Results' Section to chapter 4.
- Add 'Results' Section to chapter 4.
- Finish 'Conclusions' chapter.
- Finish 'Conclusions' chapter.
- Move TUIO appendix to chapter 4.
Vragen Belleman:
Vragen Belleman:
- Kan 'Conclusions' wel in H3, voordat experimenten zijn gedaan?
- Kan 'Conclusions' wel in H3, voordat experimenten zijn gedaan?
...
...
docs/report.bib
View file @
6c12d81a
...
@@ -238,7 +238,7 @@
...
@@ -238,7 +238,7 @@
journal = "ACM Comput. Surv.",
journal = "ACM Comput. Surv.",
keywords = "dblp",
keywords = "dblp",
number = 1,
number = 1,
pages = "13-16",
pages = "13-
-
16",
title = "{A Characterization of Ten Hidden-Surface Algorithms.}",
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",
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,
volume = 6,
...
@@ -246,3 +246,9 @@
...
@@ -246,3 +246,9 @@
year = 1974
year = 1974
}
}
@misc{wikihashmap,
author = "Wikipedia",
howpublished = "\url{http://en.wikipedia.org/wiki/Hashmap}",
title = "{Hash map}"
}
docs/report.tex
View file @
6c12d81a
...
@@ -842,19 +842,30 @@ hand tracker assigns a finger to a hand after a \emph{point\_down} event, its
...
@@ -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
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
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
identifying values, known as keys (e.g., a person's name), to their associated
values (e.g., their telephone number). Source:
values (e.g., their telephone number). Source: Wikipedia
\cite
{
wikihashmap
}
.
}
\url
{
http://en.wikipedia.org/wiki/Hashmap
}}
with the
\texttt
{
Hand
}
object. When
with the
\texttt
{
Hand
}
object. When a finger moves (a
\emph
{
point
\_
move
}
event)
a finger moves (a
\emph
{
point
\_
move
}
event) or releases the touch surface
or releases the touch surface (
\emph
{
point
\_
up
}
), The corresponding hand is
(
\emph
{
point
\_
up
}
), The corresponding hand is loaded from the hash map and
loaded from the hash map and triggers a
\emph
{
finger
\_
move
}
or
triggers a
\emph
{
finger
\_
move
}
or
\emph
{
finger
\_
up
}
gesture. If a released
\emph
{
finger
\_
up
}
gesture. If a released finger is the last of a hand, that
finger is the last of a hand, that hand is removed with a
\emph
{
hand
\_
up
}
hand is removed with a
\emph
{
hand
\_
up
}
gesture.
gesture.
\section
{
Results
}
\section
{
Results
}
\label
{
sec:results
}
\label
{
sec:results
}
% TODO: Evalueer of de implementatie en testapplicaties voldoen aan de
% TODO: Evalueer of de implementatie en testapplicaties voldoen aan de
% verwachtingen/eisen die je hebt gesteld in je ontwerp.
% 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
}
\chapter
{
Conclusions
}
\label
{
chapter:conclusions
}
\label
{
chapter:conclusions
}
...
@@ -885,6 +896,8 @@ A gesture trackers implementation is flexible, e.g. complex detection
...
@@ -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
algorithms such as machine learning can be used simultaneously with other
gesture trackers that use explicit detection.
gesture trackers that use explicit detection.
% TODO: Daemon implementatie
% TODO: terugkomen op resultaten uit testimplementatie
% TODO: terugkomen op resultaten uit testimplementatie
\chapter
{
Suggestions for future work
}
\chapter
{
Suggestions for future work
}
...
...
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