Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
multitouch
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Taddeüs Kroes
multitouch
Commits
bb0fe911
Commit
bb0fe911
authored
12 years ago
by
Taddeüs Kroes
Browse files
Options
Downloads
Patches
Plain Diff
Wrote analysis of related work and removed references to VTK interactor as PoC.
parent
d5319a8c
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/report.bib
+8
-0
8 additions, 0 deletions
docs/report.bib
docs/report.tex
+21
-29
21 additions, 29 deletions
docs/report.tex
with
29 additions
and
29 deletions
docs/report.bib
+
8
−
0
View file @
bb0fe911
...
...
@@ -84,3 +84,11 @@
year
=
{2008}
,
howpublished
=
{\url{http://code.google.com/p/pytuio/}}
}
@misc
{
wiki:DOM
,
author
=
"Wikipedia"
,
title
=
"Document Object Model --- Wikipedia{,} The Free Encyclopedia"
,
year
=
"2012"
,
howpublished
=
{\url{http://en.wikipedia.org/w/index.php?title=Document_Object_Model&oldid=494650979}}
,
note
=
"[Online; accessed 7-June-2012]"
}
This diff is collapsed.
Click to expand it.
docs/report.tex
+
21
−
29
View file @
bb0fe911
...
...
@@ -69,14 +69,10 @@ Python.
\item
How can the architecture be used by different programming
languages? A generic architecture should not be limited to be used
in only one language.
\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.
% FIXME: gaan we nog wat doen met onderstaand?
%\item Is performance an issue? For example, an event loop with rotation
% detection could swallow up more processing resources than desired.
%\item How can the architecture be integrated in a VTK interactor?
\item
Can events be used by 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.
\end{itemize}
% Afbakening
...
...
@@ -86,9 +82,10 @@ Python.
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.
Being a Proof of Concept, the reference implementation itself does not
necessarily need to meet all the requirements of the design.
events to some simple touch gestures that are used by some test
applications.
%Being a Proof of Concept, the reference implementation itself does not
%necessarily need to meet all the requirements of the design.
\section
{
Structure of this document
}
...
...
@@ -150,8 +147,18 @@ Python.
itself is partially re-used in the reference implementation of the
generic gesture detection architecture.
\section
{
Analysis
}
\section
{
Analysis
of related work
}
The simple Processing implementation of multi-touch events provides most of
the functionality that can be found in existing multi-touch applications.
In fact, many applications for mobile phones and tablets only use tap and
scroll events. For this category of applications, using machine learning
seems excessive. Though the representation of a gesture using a feature
vector in a machine learning algorithm is a generic and formal way to
define a gesture, a programmer-friendly architecture should also support
simple, ``hard-coded'' detection code. A way to separate different pieces
of gesture detection code, thus keeping a code library manageable and
extendable, is to user different gesture trackers.
\chapter
{
Requirements
}
...
...
@@ -166,11 +173,6 @@ Python.
% wellicht in een ander programma nodig om maar 1 hand te gebruiken, en
% dus punten dicht bij elkaar te kiezen (oplossing: windows).
% Tekenprogramma dat huidige points + centroid tekent en waarmee
% transformatie kan worden getest Link naar appendix "supported events"
% Proof of Concept: VTK interactor
\section
{
Introduction
}
% TODO
...
...
@@ -462,16 +464,6 @@ Python.
% geen netwerk protocol
% een paar simpele windows en trackers
\chapter
{
Integration in VTK
}
\section
{
The Visualization Toolkit
}
\label
{
sec:vtk
}
% TODO
% VTK heeft eigen pipeline, architectuur moet daarnaast draaien
% VTK interactor
%\chapter{Conclusions}
% TODO
...
...
@@ -483,11 +475,11 @@ Python.
% TODO
% geruik formele definitie van gestures in gesture trackers, bijv. state machine
% Network protocol (ZeroMQ) voor meerdere talen en simultane processen
% Hierij ook: extra laag die gesture windows aanmaakt die corresponderen met window manager
% State machine
% Window in boomstructuur voor efficientie
\bibliographystyle
{
plain
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment