IT-G400 Series Android 6.0 Quick Start Guide This document is a Development Guide Book for IT-G400 application developers. Ver 1.
No part of this document may be produced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of CASIO Computer Co., Ltd. in Tokyo Japan. Information in this document is subject to change without advance notice. CASIO Computer Co., Ltd.
- Table of contents 1. 1.1 1.2 1.3 1.
1. Overview This document is a developement guide book writen for the IT-G400 application developers. 1.1 Notes of this development kit Notes for using this development kit are as follows. There is a dependency between the version of Android Studio and the version of the DeviceLibrary. For details, refer to "2.4 Required softwares (p.8)" in the Quick Start Guide (this document). Please contact your distributor to get the latest version of development Kit.
1.2 Version of this development kit The version number of this development kit consists of a combination of major version and minor version, as shown below. 1.02.1 Major version Minor version The major number represents the version of DeviceLibrary( i.e. DeviceLibrary.aarAAR). So, when a newer version of development kit is released, if it includes newer version of DeviceLibrary, its major version number is increased, and the minor version is returned to zero. If changes other than DeviceLibrary ( i.e.
1.3 Structure of the development kit The following figure shows the structure of this kit. QuickStartGuide.pdf /MANUAL QuickStartGuide.pdf SoftwareManual.pdf DeviceLibraryManual.pdf /SOFTWARE /BDK /CasioAndroidAddons /bin CASIOAndroidAddons0100010005.apk /manual CasioAndroidAdons.pdf /DeviceLibrary /javadoc index.html etc. /bin DeviceLibrary.aar /samples KeyLibrarySample.zip SymbolScan.zip RangeScan.zip InverseScan.zip CenteringWindowScan.zip TriggerScan.zip ImageCapture.
1.4 About manuals The following is a list of manuals provided with this development kit. Title Quick start guide Software manual DeviceLibrary manual CasioAndroidAddons manual KittingTool manual Contents This document Software specification of IT-G400 Describing the specifications of the device library Describing the specifications of the CasioAndroidAddons. Describing the specifications of the KittingTool.
2. Application development requirement 2.1 Needed programing knowledges IT-G400 application can be developped using the following language. • Java And, also the knowledge about the followings are needed. • • • • Android OS Android allication development Android Studio Networks, etc. 2.
2.3 Required system [ Windows ] Microsoft® Windows® 7/8/10 (32- or 64-bit) 3 GB RAM minimum, 8 GB RAM recommended; plus 1 GB for the Android Emulator 2 GB of available disk space minimum, 4 GB Recommended (500 MB for IDE + 1.5 GB for Android SDK and emulator system image) 1280 x 800 minimum screen resolution For accelerated emulator: Intel® processor with support for Intel® VT-x, Intel® EM64T (Intel® 64), and Execute Disable (XD) Bit functionality [ Mac ] Mac® OS X® 10.
2.4 Required softwares In order to develop IT-G400 application programs, it needs the development environment of Android. Development platform (Recommended) Development language Java Development platform (Recommended) Android Studio 2.2 or above Android SDK (API level 17 - 23) Google USB driver JDK7 or above Caution ! Using the old development kit with the new Android Studio may cause problems. Be sure to use the latest development kit when upgrading Android Studio version.
3. Installing the development environment Due to version upgrade of Android SDK, environment may not be installed by the following procedure. In that case, please refer to the procedure described on Google's website etc. and build the environment. 3.1 Installation steps of the development environment The followings are the basic steps to install the development environment. (1) Installing JDK Before installing Android Studio, JDK ( Java Development Kit ) has to be installed. Regarding JDK, refere “2.
3.2 Installing JDK Java SE JDK can be downloaded from the Java site. Visit the site and download the Java SE JDK package corresponding to your Windows platform. http://www.oracle.com/technetwork/java/javase/downloads/index.html The URL and contents of the Java site may differ from the contents described in this document due to the update of the site. When downloading the JDK, please access the Java site via the search engine etc. and follow the description of the site.
Execute the downloaded file with administrator privileges. Basically, it is not needed to change the value from default.
12
3.3 Installing Android Studio Android Studio can be downloaded from Android site of Google. http://developer.android.com/sdk/index.html Agree to the “Terms of Conditions”, then start downloading. Once executing the downloaded file, follow the instructions to proceed the installation.
During installation, you will be prompted to specify the installation destination by the dialog below. The "Android SDK Installation Location" on the figure below is also necessary when installing the USB driver, it's better to take a note. When the dialog shown below is displayed, installation of Android Studio is completed.
3.4 Downloading Android SDK and USB driver Launch Android Studio, and chose "SDK Manager" from Configure tab. Select “SDK Platform” tab, then check "Android 6.0 (API Level 23)". Then, select “SDK Tools” tab and check "Google USB Driver".
Once agree to the “License Agreement”, then press “OK” to start installation. The downloaded files are stored under "Android SDK Installation Location" that you noted in "3.3 Installing Android Studio (p.13) ". The USB driver is stored in "extras¥google¥usb_driver" under "Android SDK Installation Location".
3.5 Installing and Updating Device Library (AAR) This chapter explains how to register the device library and its help file to Android Studio project. 3.5.1 Preparations Device Library ( AAR ) and its help files ( Javadoc ) are needed to be registered to the each project via Android Studio. Therefore, the method described here is necessary every time when creating new project that uses the device library.
On the dialog shown below, select "Import .JAR/.AAR Package" and proceed with "Next". Press the of "File name" and select the DeviceLibrary (AAR) you copied beforehand. By the above, the registration of the device library to the project was completed. You can see that the AAR file name has been added to the Android Studio Project tree.
19
3.5.3 Dependency check of DeviceLibrary ( AAR ) The registration of the device library was completed with "3.5.2 Registering DeviceLibrary (p.17)". However, somehow the dependency relationship of the DeviceLibrary to the project is not set correctly in some cases. If the dependency is not set correctly, "3.5.4 Registering Help files ( Javadoc ) (p.23)" can not be done correctly, in that case follow the explanation in this section. First, select "Project Structure ..." from File menu. Project Structure...
Confirm that "DeviceLibrary" is displayed as shown below and tap "OK". By the above, "DeviceLibrary" has been added to the tab of "Dependencies".
22
3.5.4 Registering Help files ( Javadoc ) This section explains how to enable pop-up help (pops up help message when you move the cursor to the function name) of Device Library. First, associate Javadoc which is the help file of Device Libraries to Device Library registered to Android Studio. The Javadoc file can be placed anywhere as long as it can be referenced on the PC. It assumes that it is placed in the "docs/DeviceLibrary" folder here.
Select "Settings ..." from File menu of Android Studio. Settings Next, check a box of "Show quick documentation on mouse move". Show quick documentation on mouse move. Now, if you hover the mouse cursor over the function name, help of the function will be poped up.
3.5.5 Updating of DeviceLibrary （ AAR ） In order to update the device control library registered in the project of Android Studio (exchange to the new version), once you need to unregister (unassociate) them and register new one. This section explains how to unregister (unassociate) them from the project. (1) Unassociate Library ( AAR ) Open your project in Android Studio and select [File] -> [Project Structure ...]. Select "app" from "Modules" in the left frame and open the "Dependencies" tab.
A dialog to confirm deletion of DeviceLibrary appears, so tap [Yes]. By the above, Device Library was unregistered. Follow "3.5Installing and Updating Device Library(p.17)" to register the new Device Library.
3.6 How to use the DeviceLibrary ( AAR ) To use an AAR file, just like jar, it is needed to inport it in order to create class object. If a class that has not been imported is used, popup message as shown below is comes.
4. Application development and debug In order to develop / debug applications using IT-G400, the following preparation is necessary. (1) Enable USB debugging (ADB connection) of IT-G400. (2) Install IT-G400 USB driver to your PC. (3) Set PATH to the debug tools on your PC. These steps are described below. 4.1 Enabling USB debugging Since USB debugging is a function for developers, you first need to activate the Developer options by the following procedure.
Tap [Developer options] and enable "USB debugging" on the opened screen. 4.2 Installing USB driver Install the USB driver for connecting the IT-G400 and PC with the ADB (Android Debug Bridge) protocol. Files necessary for installation are downloaded as described in "3.4 Downloading Android SDK and USB driver (p.15)”. Connect the IT-G400 to a PC using a USB cable or a USB cradle. Then, open the Device Manager by [Control Panel] → [Hardware and Sound] → [Device Manager].
In the Device Manager, “Android” is displayed as an unknown device as shown below. By right-click the red frame (“Android”) in the above figure, displays its properties, and press [Update Driver]. When the dialog below is displayed, press "Let me pick from a list of drivers on my computer " at the bottom. In the driver list, with "Show all devices" is highlighted and press [Next].
When you click [Hard Disk…] in the displayed dialog, a dialog box for specifying the location of the driver opens, so click [Browse…] to open the file dialog box. In the file dialog box, search for “extras¥google¥usb_driver¥android_winusb.inf” under the “Android SDK Installation Location" that you took note in “3.4 Downloading Android SDK and USB driver (p.15)” and specify it. The following driver selection screen will appear. Select "Android Composite ADB Interface" and press [Next].
4.3 Settings for ADB （ Android Debug Bridge ) In order to use Android SDK tools such as adb from the command prompt, it is needed to add the path to Android SDK to the system environment variable. Add the following two paths. The "tools" folder under "Android SDK Installation Location" that you took note. The "platform-tools" folder under "Android SDK Installation Location". In the above example, the path to add is as follows.
