MMIR2 4 Getting started
This chapter describes the system and software requirements for developing multimodal mobile interaction applications using MMIR-framework for Android operating system.
- Windows XP, Vista, or Windows 7
- Mac OS
For development based on the MMIR Starter Kit application
-
Download and install Eclipse (3.4+)
(e.g. the Classic, or EE Developer edition)
-
Download and install Android SDK (2.2+)
-
Download and install ADT Plugin
-
Download the MMIG-StarterKit.zip
You should also ensure that you have created at least one Android virtual device (AVD): in Eclipse select the Java perspective and open from the menu Window → Android Virtual Device Manager; for detailed instructions on how to create a new AVD in Eclipse, we refer to the online instructions. You will need an AVD to run your project in the Android emulator. You should have the Android tools/ and Android platform-tool/ folders listed in your system path. Both these folders can be found inside your Android installation directory.
Use Window → Android SDK Manager for installing the SDK of the Android version you are targeting with your application; at least one SDK has to be installed (we recommend to use at least ver. 2.2+).
While using Eclipse as development environment is not strictly required, we recommend it. The following gives some hints for setting up Eclipse in order to ease development of MMIR based applications.
First, you should download and install the Android SDK; you should note the directory where the SDK is installed into, as you may need this information later. Next, install the ADT Plugins (e.g. in Eclipse, using the update site); see also chapter Requirements (p. 31), above.
Hint: If your Eclipse environment brings an HTML editor (e.g. as the EE Developer edition does) [⊗] you can setup Eclipse to use this editor for eHTML files. eHTML is the template format used by the framework, similar to JSP (Java Server Pages) or ASP (Active Server Pages) templates.
For setting the HTML editor as default editor: Preferences → General → Editors → File Associations, then in File types, add an entry for *.ehtml and set the HTML editor as its default.
Figure 6: Eclipse Preferences dialog for associating file extensions with content types.
For using the syntax highlight of the HTML editor: in Preferences → General → Content Types select Text → HTML, then in Text → File Associations add an entry *.ehtml.
Figure 7: *.ehtml file without (left) and with (right) syntax highlighting for content type HTML in Eclipse.
For debugging purposes, you may want to configure Eclipse to have access to the Android source code. For Android 4.x you can use the SDK Manager, e.g. in Eclipse in the Java perspective, open Window → Android SDK Manager, expand the entry for the corresponding Android 4.x version and select Sources for Android SDK for installing the source. When prompted with No sources attached... for Android code (e.g. during debugging), select the [Android SDK directory]/sources/[version] subdirectory for the version currently used in your project from the Android SDK installation directory, e.g. /android-sdk/sources/android-16.
For some of the older Android versions [⊥], the plugin from http://code.google.com/p/adt-addons/ → Android Sources can be used to integrate source code support. You can use the update site http://adt-addons.googlecode.com/svn/trunk/source/com.android.ide.eclipse.source.update/ for installing the Android Sources plugin.
[⊗]
Eclipse Classic does not bring an editor for HTML by default; you can install an editor manually e.g.
using your Eclipse’s update page Install New Software...: select the entry with
[version name] - http://download.eclipse.org/releases/[version_name], there expand the entry
Web, XML and Java EE development and select Web Page Editor.
[⊥] Note, that currently no source code is available for Android ver. 3.x.