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
4b796592
Commit
4b796592
authored
Jun 15, 2012
by
Taddeüs Kroes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Wrote 'future work' chapter and cleaned up some diagram code.
parent
ff8c7c40
Changes
3
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
158 additions
and
44 deletions
+158
-44
docs/data/diagrams.tex
docs/data/diagrams.tex
+16
-7
docs/report.bib
docs/report.bib
+7
-0
docs/report.tex
docs/report.tex
+135
-37
No files found.
docs/data/diagrams.tex
View file @
4b796592
...
...
@@ -48,7 +48,7 @@
\end{tikzpicture}
}
\
newcommand
{
\basicdiagram
}
[1]
{
\
def\basicdiagram
{
\begin{figure}
[h]
\center
\architecture
{
...
...
@@ -57,7 +57,11 @@
\node
[block, below of=arch]
{
Application
}
edge[linefrom] node[right]
{
gestures
}
(arch);
}
\caption
{
#1
}
\caption
{
A diagram showing the position of the architecture relative to
the device driver and a multi-touch application. The input of the
architecture is given by a touch device driver. The output is
translated to complex interaction gestures and passed to the
application that is using the architecture.
}
\label
{
fig:basicdiagram
}
\end{figure}
}
...
...
@@ -111,7 +115,7 @@
\end{figure}
}
\
newcommand
{
\areadiagram
}
[1]
{
\
def\areadiagram
{
\begin{figure}
[h]
\center
\architecture
{
...
...
@@ -127,12 +131,16 @@
\group
{
eventdriver
}{
eventdriver
}{
analysis
}{
area
}{
Architecture
}
}
\caption
{
#1
}
\caption
{
Extension of the diagram from figure
\ref
{
fig:driverdiagram
}
,
showing the position of areas in the architecture. An area delegate
events to a gesture detection component that trigger gestures. The area
then calls the handler that is bound to the gesture type by the
application.
}
\label
{
fig:areadiagram
}
\end{figure}
}
\
newcommand
{
\trackerdiagram
}
[1]
{
\
def\trackerdiagram
{
\begin{figure}
[h]
\center
\architecture
{
...
...
@@ -148,7 +156,8 @@
\group
{
eventdriver
}{
eventdriver
}{
tracker
}{
area
}{
Architecture
}
}
\caption
{
#1
}
\caption
{
Extension of the diagram from figure
\ref
{
fig:areadiagram
}
,
showing the position of gesture trackers in the architecture.
}
\label
{
fig:trackerdiagram
}
\end{figure}
}
...
...
@@ -330,6 +339,6 @@
\end{tikzpicture}
\caption
{
Daemon setup of an architecture implementation, serving
gestures to multiple applications at the same time.
}
\label
{
fig:
ex3
}
\label
{
fig:
daemon
}
\end{figure}
}
docs/report.bib
View file @
4b796592
...
...
@@ -171,3 +171,10 @@
year = "2001"
}
@misc{ZeroMQ,
author = "Corporation, iMatix",
howpublished = "\url{http://www.zeromq.org/}",
title = "{Zero MQ - The intelligent transport layer}",
year = "2007"
}
docs/report.tex
View file @
4b796592
This diff is collapsed.
Click to expand it.
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