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
f84b6adc
Commit
f84b6adc
authored
12 years ago
by
Taddeüs Kroes
Browse files
Options
Downloads
Patches
Plain Diff
Added reference to PyGTK and added daemon implementation to conclusions.
parent
6c3205c8
No related branches found
Branches containing commit
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
+6
-0
6 additions, 0 deletions
docs/report.bib
docs/report.tex
+9
-6
9 additions, 6 deletions
docs/report.tex
with
15 additions
and
6 deletions
docs/report.bib
+
6
−
0
View file @
f84b6adc
...
...
@@ -252,3 +252,9 @@
title
=
"{Hash map}"
}
@misc
{
PyGTK
,
author
=
"{The PyGTK Team}"
,
note
=
"\url{http://www.pygtk.org/}"
,
title
=
"{PyGTK}"
}
This diff is collapsed.
Click to expand it.
docs/report.tex
+
9
−
6
View file @
f84b6adc
...
...
@@ -821,9 +821,10 @@ the entire touch surface. The output of the application can be seen in figure
\label
{
sec:testapp
}
The second test application uses the GIMP toolkit (GTK+)
\cite
{
GTK
}
to create
its user interface. Since GTK+ defines a main event loop that is started in
order to use the interface, the architecture implementation runs in a separate
thread.
its user interface. The PyGTK library
\cite
{
PyGTK
}
is used to address GTK+
functions in the Python application. Since GTK+ defines a main event loop that
is started in order to use the interface, the architecture implementation runs
in a separate thread.
The application creates a main window, whose size and position are synchronized
with the root event area of the architecture. The synchronization is handled
...
...
@@ -997,9 +998,11 @@ use explicit detection. Also, the modularity of this design allows extension of
the set of supported gestures. Section
\ref
{
sec:testapp
}
demonstrates this
extendability.
% TODO: Daemon implementatie
% TODO: terugkomen op resultaten uit testimplementatie
A true generic architecture should provide a communication interface that
provides support for multiple programming languages. A daemon implementation as
described by section
\ref
{
sec:daemon
}
is an example of such in interface. With
this feature, the architecture can be used in combination with a wide range of
application frameworks.
\chapter
{
Suggestions for future work
}
\label
{
chapter:futurework
}
...
...
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