this is for holding javascript data
Craig Ashley edited Our Prototype.tex
about 10 years ago
Commit id: cb9c574575de49fedffb7b4e18a861627aa945ca
deletions | additions
diff --git a/Our Prototype.tex b/Our Prototype.tex
index a0faf4f..6e217b6 100644
--- a/Our Prototype.tex
+++ b/Our Prototype.tex
...
\section{Prototype}
\subsection{Early Prototype}
The early prototype for the application made use of the Android SurfaceView, a View (classes for dealing with user interface and interaction) for drawing graphics onto the screen.
Two concurrent prototypes were created to test two different proposed implemetations.
\subsection{Canvas Prototype}
The
canvas prototype for the application made use of the Android SurfaceView, a View (classes for dealing with user interface and interaction) for drawing graphics onto the screen.
This prototype took in image files that were placed in the resources folder, and decoded them into Bitmap objects that could drawn onto the SurfaceView using the Canvas, which holds the drawing calls.
The Canvas was then used to draw the map background, and an arrow was drawn on top of that background.
A Thread was used to keep the graphics being drawn without it taking away processing from the user interface, so the application would not become unresponsive.
The Canvas was also used to draw a rectangle in the corner of the screen, where text would be displayed to display the score.
Problems were encountered
early on with this prototype, as
bonerbonerboner the limited amount of memory available for Android applications made it a problem to load a large map file. One of the alternative fixes would have been to use multiple image files and have them programatically stitched together inside the application itself. This proved to be a big problem and