Cordova Device Features with Touch
Many classes have shortcut names used when creating (instantiating) a class with a
configuration object. The shortcut name is referred to as an alias (or xtype if the
class extends Ext.Component). The alias/xtype is listed next to the class name of
applicable classes for quick reference.
Framework classes or their members may be specified as private or protected. Else,
the class / member is public. Public, protected, and private are access
descriptors used to convey how and when the class or class member should be used.
Public classes and class members are available for use by any other class or application code and may be relied upon as a stable and persistent within major product versions. Public classes and members may safely be extended via a subclass.
Protected class members are stable public members intended to be used by the
owning class or its subclasses. Protected members may safely be extended via a subclass.
Private classes and class members are used internally by the framework and are not intended to be used by application developers. Private classes and members may change or be omitted from the framework at any time without notice and should not be relied upon in application logic.
static label next to the
method name. *See Static below.Below is an example class member that we can disect to show the syntax of a class member (the lookupComponent method as viewed from the Ext.button.Button class in this case).
Let's look at each part of the member row:
lookupComponent in this example)( item ) in this example)Ext.Component in this case). This may be omitted for methods that do not
return anything other than undefined or may display as multiple possible values
separated by a forward slash / signifying that what is returned may depend on the
results of the method call (i.e. a method may return a Component if a get method calls is
successful or false if unsuccessful which would be displayed as
Ext.Component/Boolean).PROTECTED in
this example - see the Flags section below)Ext.container.Container in this example). The source
class will be displayed as a blue link if the member originates from the current class
and gray if it is inherited from an ancestor or mixed-in class.view source in the example)item : Object in the example).undefined a "Returns" section
will note the type of class or object returned and a description (Ext.Component in the
example)Available since 3.4.0 - not pictured in
the example) just after the member descriptionDefaults to: false)The API documentation uses a number of flags to further commnicate the class member's function and intent. The label may be represented by a text label, an abbreviation, or an icon.
classInstance.method1().method2().etc();false is returned from
an event handler- Indicates a framework class
- A singleton framework class. *See the singleton flag for more information
- A component-type framework class (any class within the Ext JS framework that extends Ext.Component)
- Indicates that the class, member, or guide is new in the currently viewed version
- Indicates a class member of type config
- Indicates a class member of type property
- Indicates a class member of type
method
- Indicates a class member of type event
- Indicates a class member of type
theme variable
- Indicates a class member of type
theme mixin
- Indicates that the class, member, or guide is new in the currently viewed version
Just below the class name on an API doc page is a row of buttons corresponding to the types of members owned by the current class. Each button shows a count of members by type (this count is updated as filters are applied). Clicking the button will navigate you to that member section. Hovering over the member-type button will reveal a popup menu of all members of that type for quick navigation.
Getting and setter methods that correlate to a class config option will show up in the methods section as well as in the configs section of both the API doc and the member-type menus just beneath the config they work with. The getter and setter method documentation will be found in the config row for easy reference.
Your page history is kept in localstorage and displayed (using the available real estate) just below the top title bar. By default, the only search results shown are the pages matching the product / version you're currently viewing. You can expand what is displayed by clicking on the button on the right-hand side of the history bar and choosing the "All" radio option. This will show all recent pages in the history bar for all products / versions.
Within the history config menu you will also see a listing of your recent page visits. The results are filtered by the "Current Product / Version" and "All" radio options. Clicking on the button will clear the history bar as well as the history kept in local storage.
If "All" is selected in the history config menu the checkbox option for "Show product details in the history bar" will be enabled. When checked, the product/version for each historic page will show alongside the page name in the history bar. Hovering the cursor over the page names in the history bar will also show the product/version as a tooltip.
Both API docs and guides can be searched for using the search field at the top of the page.
On API doc pages there is also a filter input field that filters the member rows using the filter string. In addition to filtering by string you can filter the class members by access level and inheritance. This is done using the checkboxes at the top of the page.
The checkbox at the bottom of the API class navigation tree filters the class list to include or exclude private classes.
Clicking on an empty search field will show your last 10 searches for quick navigation.
Each API doc page (with the exception of Javascript primitives pages) has a menu view of metadata relating to that class. This metadata view will have one or more of the following:
Ext.button.Button class has an alternate class name of Ext.Button). Alternate class
names are commonly maintained for backward compatibility.Runnable examples (Fiddles) are expanded on a page by default. You can collapse and expand example code blocks individually using the arrow on the top-left of the code block. You can also toggle the collapse state of all examples using the toggle button on the top-right of the page. The toggle-all state will be remembered between page loads.
Class members are collapsed on a page by default. You can expand and collapse members using the arrow icon on the left of the member row or globally using the expand / collapse all toggle button top-right.
Viewing the docs on narrower screens or browsers will result in a view optimized for a smaller form factor. The primary differences between the desktop and "mobile" view are:
The class source can be viewed by clicking on the class name at the top of an API doc page. The source for class members can be viewed by clicking on the "view source" link on the right-hand side of the member row.
In this guide, we will walk through the process of creating a simple native Sencha Touch application that can access an Android device's photo library and camera. Within the application, you may:
The resulting image will then appear in the application's main panel.
Note: This guide only applies to Androids using Cordova.
The following tools must be installed before proceeding:
Open your CLI and generate a starter application with Sencha Cmd by issuing the following:
sencha -sdk /path/to/sdk generate app touchCamera /target/app/directory
Note: Please utilize 'touchCamera' as your application name or be prepared to modify the provided code as needed.
Using your editor of choice, replace the contents of the "app/view/Main.js" file in your application's view directory. Your new code should look like this:
Ext.define('touchCamera.view.Main', {
extend: 'Ext.Panel',
xtype: 'main',
requires: [
'Ext.Button',
'Ext.Img'
],
config: {
layout: {
type:"vbox",
pack:"center",
align:"center"
},
items: [{
xtype: 'titlebar',
docked: 'top',
title: 'Native API Examples'
}, {
xtype: "image",
src: "http://placehold.it/200x200",
width: '100%',
height: '100%'
}, {
xtype: 'toolbar',
docked: 'bottom',
items: [{
xtype: "button",
text: "Photo Library",
handler: function(btn) {
var panel = btn.up('panel');
panel.getPhoto(navigator.camera.PictureSourceType.PHOTOLIBRARY);
}
}, {
xtype: "button",
text: "Take Photo",
handler: function(btn) {
var panel = btn.up('panel');
panel.getPhoto(navigator.camera.PictureSourceType.CAMERA);
}
}]
}]
},
getPhoto: function(source) {
var me = this;
navigator.camera.getPicture(me.success, me.failure, {
quality: 50,
destinationType: navigator.camera.DestinationType.FILE_URI,
sourceType: source
});
},
success: function(image_uri) {
var img = Ext.ComponentQuery.query("image")[0];
img.setSrc(image_uri);
},
failure: function(message) {
alert("Failed" + message);
}
});
The next step is to create a Cordova project in the application folder. Cordova can access the native Android APIs so that the application can interact with the device photo library and camera.
Change to the directory in which the application was generated by ‘sencha generate app’.
cd /target/app/directory
Create a Cordova project in your application directory.
sencha cordova init
You should now see that a Cordova directory has been created in your application's directory. The default configuration files created for the project will be need to be updated as per the device APIs your application needs to access. You must also include the device permissions needed for your application to function properly.
This process also updates the app.json file in your application to include a "builds" configuration block. This
block needs to be updated to reflect the build type your application is creating.
Edit app.json file and update the "builds" block to look like the following example.
Note: In the case below, we are specifying a new build target of ‘android’ that will use the Cordova packager and run on an android platform:
"builds": {
"web": {"default": true},
"android": { // This can be any build target name you desire (eg myApp, apple, etc)
"packager": "cordova", // Specify that we are using cordova to package the app
"cordova" : { // configuration for cordova build
"config": {
"id": "com.domain.touchCamera", // namespace of application (required)
"name": "touchCamera", // app name which appears under the icon on device
"platforms": "android" // add platform(s) here
}
}
}
},
CD into the "cordova" directory
cd cordova
Each API that is used in the application requires its corresponding plugin is added to the project. In this example, the camera is used. To add the camera plugin, issue the following command in the "cordova" directory :
cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-camera.git
Verify that the plugin has been added to the "cordova" project:
cordova plugin list
//org.apache.cordova.camera 0.3.4-dev "Camera"
Next, let's tell Cordova that the application will be using the camera plugin by adding the following information to
the config.xml file:
<feature name="Camera">
<param name="android-package" value="org.apache.cordova.camera.CameraLauncher" />
</feature>
Add write permissions to the AndroidManifest.xml file found in "cordova/platforms/android" so the camera can save
pictures to the device. The following line will need to be added to the file directly after line regarding
android.permission.INTERNET.
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
Once the configuration files have been updated with the appropriate permissions and feature information, change back to the primary application directory and build the application:
cd ..
sencha app build android
A successful build will result in the creation of an Android Package (APK) found here:
cordova/platforms/android/ant-build
You can verify its existence with the following command:
find . name -name *.apk
//./cordova/platforms/android/ant-build/touchCamera-debug-unaligned.apk
//./cordova/platforms/android/ant-build/touchCamera-debug.apk
Prior to installation, please make sure that the:
Next, ensure that the development computer can see the attached Android device by issuing the following command:
adb devices
//* daemon not running. starting it now on port 5037 *
//* daemon started successfully *
//List of devices attached
//015d262e99100202 device
The above output shows one Android device connected to a computer.
Note: Your device number will be different than the one found above.
If you do not see a device listed, please check your connection, device permissions, and debugging status. Installing the Application
Move the package to the Android device by issuing the following command:
$ adb install -r cordova/platforms/android/ant-build/touchCamera-debug.apk
//1284 KB/s (2446896 bytes in 1.860s)
//pkg: /data/local/tmp/touchCamera-debug.apk
//Success
If the previous adb install command executed successfully, the Touch application will appear in the apps section of
the Android device. The standard Cordova icon will appear and the name under the icon will be touchCamera. Tap the
icon to launch the Touch application.
The application will have two buttons at the bottom of the screen. The first opens the photo library and second launches the camera.
Touch either button to see the app in action. After returning from either the photo library or camera, the selected picture will appear in the image block in the middle of the application.
Sencha Touch 2.4 | Terms of Use