Getting Started with Sencha Touch

关注

原创最新推荐文章于 2026-04-21 12:19:49 发布 214 阅读 AI 写同款· GEO 优化 ›

This document describes how to get started with Sencha Touch. It explains the basic steps for using Sencha Touch to create Web applications for touch-based devices. Additionally, it provides detailed steps for creating the GeoTweets example application, which is one of the example applications included in the Sencha Touch release package.

This document is written for Web developers who want to quickly get started using Sencha Touch to create Web applications for touch-based devices. It assumes you have downloaded the Sencha Touch libraries. have a properly installed and configured Web server, and are familiar with Web application development and concepts such as JavaScript, HTML, Cascading Style Sheets (CSS), Web servers, and so forth.

This document contains the following sections:

Introduction to Sencha Touch

Sencha Touch is a JavaScript framework for creating Web applications targeted to touch-based devices. With Sencha Touch, you can use the skills you already possess to create an elegant and consistent user experience with minimal effort. Sencha Touch makes use of technologies such as HTML and CSS to provide native-quality application experiences without needing plugins.

Using Sencha Touch: Main Steps

To use Sencha Touch to create JavaScript applications for touch-based devices, follow these main steps:

1. Upload the library files to the destination directory on your Web server.
2. Upload the application files (html, js, and css) and all referenced files to the destination directory on your Web server.
3. Point your browser to http://localhost:8080/myapp.html where:
  - localhost is the Web server host name or IP address
  - 8080 is the Web server port number
  - myapp.html is the name of the application HTML file
1. Open the HTML file.
2. Locate the code that specifies the Sencha Touch Library. For example:
```
	
	<script type="text/javascript" src="../../sencha-touch-debug.js"></script>
	
```
Replace sencha-touch-debug.js with sencha-touch.js. sencha-touch.js is optimized for production. It is compressed and does not contain documentation.
Save the HTML file.

Download the Sencha Touch Libraries.
Make sure your development environment is set up.
Make sure your development and production Web servers are properly installed and configured.
Know the name of the CSS file you want your application to use. You will need this file name when you create the application HTML file in the next step.

the default Sencha Touch cascading style sheet (CSS) file, sencha-touch.css.
the application's CSS file. For example, mycss.css.
the version of the Sencha Touch library you want the application to use.
Sencha recommends that you:
- use the debug version of the library, sencha-touch-debug.js, during application development and testing. The debug version helps you detect and troubleshoot errors, as well as to see exactly where in the library errors occur.
- change the HTML file to link to the production version of the library, sencha-touch.js, before you put your application into production. For more information see Update the Application for Production.
the application's JavaScript file, which you will create in the next step. For example, myapp.js.

In the editor of your choice, create the JavaScript file for your application. For an example of an application JavaScript file, see Creating the Application JavaScript File.
Save your file with the desired name and .js extension. For example, myapp.js. Link to this file in the HTML file you created in the previous step.

Set up your Environment Create the HTML File

In the editor of your choice, create the HTML file for your application. For an example of an application HTML file, see Detailed Steps: Creating the HTML File.

The application HTML file is where you specify links to:

Save the HTML file with a logical name such as myapp.html. After you have finished writing the application and have put it on your local Web server, you will point your browser to this file name on your local Web server in order to view and test your application.

Create the Application JavaScript File Test the Application

To test your application:

Update the Application for Production

When you are done testing your application, change the application's HTML file to point to the production version of the Sencha Touch library. To do so:

Put the Application into Production

When your application is ready for production, simply put a copy of the application's source files and any other files the application references on your production Web server.

Using Sencha Touch: Detailed Steps for Creating the GeoTweets Application

This section expands on the main steps described in the previous section by walking you step-by-step through the process of creating a Sencha Touch application. This complete source for the application, GeoTweets, can be found in the /examples/guide subdirectory in the Sencha Touch release package.

The GeoTweets application demonstrates how easy it is to use Sencha Touch to create a simple yet powerful application. The application:

uses Geolocation to find nearby tweets from Twitter.
shows the tweets in map and list views as cards which display on tabs.
uses a special animation effect when application users switch between the cards.

The following sections describe the application HTML and JavaScript files and break down creation of the application code into steps.

Creating the HTML File

The first step in creating a Sencha Touch application is to create an HTML file that links to Sencha Touch and application CSS files, the Sencha Touch library, and the application JavaScript file.

The GeoTweets application HTML file is index.html and its contents are as follows:

 <!DOCTYPE html>
 <html>
 <head>
     <meta charset="utf-8">
     <title>GeoTweets</title>

	 <!-- Sencha Touch CSS -->
	 <link rel="stylesheet" href="../../resources/css/sencha-touch.css" type="text/css">

	 <!-- Custom CSS -->
	 <link rel="stylesheet" href="css/guide.css" type="text/css">

	 <!-- Google Maps JS -->
	 <script type="text/javascript" src="http://maps.google.com/maps/api/js?sensor=true"></script>

	 <!-- Sencha Touch JS -->
	 <script type="text/javascript" src="../../sencha-touch-debug.js"></script>

	 <!-- Application JS -->
	 <script type="text/javascript" src="src/index.js"></script>


 </head>
 <body></body>
 </html>

The HTML file for the GeoTweets application links to five files:

The default CSS style sheet for Sencha Touch (sencha-touch.css).
The custom application CSS (guide.css).

This document does not describe the CSS file in detail because its properties are straight-forward and should be self-explanatory. Additionally, this document assumes you are familiar with Web application concepts such as CSS.

The Google Maps library ( http://maps.google.com/maps/api/js?sensor=true). The Sencha Touch library (during development and testing, use the debug version of the Sencha Touch library, sencha-touch-debug.js).

The debug version of the library is not compressed and it contains documentation. This can be helpful if an error occurs, as it allows you to see exactly where in the library the error occurred. Normally, in production, you would use sencha-touch.js, which is the version of the library that is optimized for production.

The application JavaScript file ( index.js).

NOTE: Notice that the <body> tag in the HTML file is empty. This is because Sencha Touch automatically generates the page content via JavaScript.

Creating the Application JavaScript File

Once you have created the HTML file, you are ready to create the application JavaScript file. This section shows the entire contents of the application JavaScript file and breaks down the creation of the application code into steps.

The GeoTweets application JavaScript file is index.js and its contents are as follows:

Ext.setup({
    tabletStartupScreen: 'tablet_startup.png',
    phoneStartupScreen: 'phone_startup.png',
    icon: 'icon.png',
    glossOnIcon: false,
    onReady: function() {
        var timeline = new Ext.Component({
            title: 'Timeline',
            cls: 'timeline',
            scroll: 'vertical',
            tpl: [
                '<tpl for=".">',
                    '<div class="tweet">',
                            '<div class="avatar"><img src="{profile_image_url}" /></div>',
                            '<div class="tweet-content">',
                                '<h2>{from_user}</h2>',
                                '<p>{text}</p>',
                            '</div>',
                    '</div>',
                '</tpl>'
            ]
        });

        var map = new Ext.Map({
            title: 'Map',
            getLocation: true,
            mapOptions: {
                zoom: 12
            }
        });

        var panel = new Ext.TabPanel({
            fullscreen: true,
            cardSwitchAnimation: 'slide',
            items: [map, timeline]
        });

        var refresh = function() {
            var coords = map.geo.coords;

            Ext.util.JSONP.request({
                url: 'http://search.twitter.com/search.json',
                callbackKey: 'callback',
                params: {
                    geocode: coords.latitude + ',' + coords.longitude + ',' + '5mi',
                    rpp: 30
                },
                callback: function(data) {
                    data = data.results;

                    // Update the tweets in timeline
                    timeline.update(data);

                    // Add points to the map
                    for (var i = 0, ln = data.length; i < ln; i++) {
                        var tweet = data[i];

                        // If the tweet is geo-tagged, use that to display marker
                        if (tweet.geo && tweet.geo.coordinates) {
                            var position = new google.maps.LatLng(tweet.geo.coordinates[0], tweet.geo.coordinates[1]);
                            addMarker(tweet, position);
                        }
                    }
                }
            });
        };

        // These are all Google Maps APIs
        var addMarker = function(tweet, position) {
            var marker = new google.maps.Marker({
                map: map.map,
                position: position
            });
        };

        map.geo.on('update', refresh);

        var tabBar = panel.getTabBar();
        tabBar.addDocked({
            xtype: 'button',
            ui: 'mask',
            iconCls: 'refresh',
            dock: 'right',
            stretch: false,
            align: 'center',
            handler: refresh
        });

    }
});

The JavaScript code in the GeoTweets application file defines:

the application cards, timeline and map. The timeline card is defined as an Ext.Component and it displays tweets in a list. The map card is an Ext.Map component and it displays the locations of the tweeters on a map.
a TabPanel component, called panel which contains two tabs: Timeline (which displays the timeline card) and Map (which displays the map card) within an animated transition for switching between the cards.
refresh and addMarker functions. The refresh function updates the data from Twitter. The addMarker function determines the geographic locations of the tweeters to display on the map card.
a custom refresh button.

Note: In this application, components are created with the following syntax:

    var objectName = new Ext.ComponentName({
        objectDefinition
    });

where:

objectName is the name of the variable used to reference the object.
ComponentName is the name of the object's class.
objectDefinition defines the object's properties and behavior.

The following sections walk you through the steps for creating the application script.

Beginning the Application Script File

In the editor of your choice, begin writing the application script. The first lines of JavaScript code for the application file (index.js) are as follows:

Ext.setup({
    tabletStartupScreen: 'tablet_startup.png',
    phoneStartupScreen: 'phone_startup.png',
    icon: 'icon.png',
    glossOnIcon: false,
    onReady: function() {

The Ext.setup method sets up a page for use on a touch-enabled device. It allows you to set various start up properties and behaviors for your application. For detailed information on the Sencha Touch API, including this method, see the Sencha Touch API Documentation.

The GeoTweets application code specifies the following start up properties:

tabletStartupScreen Property. Specifies the name of the icon file to use as the application's start up screen on tablet devices.
phoneStartupScreen Property. Specifies the name of the icon file to use as the application's start up screen on phone devices.
icon Property. Specifies the name of the application's default icon file, icon.png.
glossOnIcon Property. Specifies whether you want the gloss effect to be applied to the default icon. In this case, the value is set to false indicating not to add gloss to the default icon.
onReady Method. Specifies the function to run when the browser's Document Object Model (DOM) is ready after the application HTML file has loaded.
- The timeline card to display tweets in a list
- The map card to display tweets on a map
- The panel Ext.TabPanel container component
- A refresh function for updating the tweet data in the cards
- An addMarker function for displaying the geographic locations of the tweeters
- A refresh button on the tab bar that uses the refresh function to get the latest data from Twitter and redisplay it in the cards
- Defines three properties that control the appearance of the card:
  - title Property. Specifies the label Timeline to appear on the tab for this component.
  - cls Property. Specifies the CSS class, which you can use to style elements on the timeline.
  - scroll Property. Specifies the direction in which this Ext.Component is scrollable. In this case, it is set to 'vertical', making the card vertically scrollable. For other possible values, see the Sencha Touch API Documentation.
- Defines a template for displaying the tweets. Sencha Touch uses templates to dynamically render information in components.
- title Property. Specifies that the label Map appears on the tab for this component.
- getLocation Property. Uses the Geolocation utility to automatically get the application user's location and set it as the center of the map.
- fullscreen Option. Specifies that this component will take up the full width and height of the screen, and automatically renders the component to the page.
- cardSwitchAnimation Property. Specifies the slide special effect animation to use when switching between cards.
- items Property. Specifies the previously-defined component objects (cards) to add to this container.
- a url option. This option specifies the URL to which you want to make an external call using JSONp. The corresponding code is:
```
url: 'http://search.twitter.com/search.json',
```
- the callbackKey. This function runs when data is returned.
- params (parameters). These parameters are passed directly into the request and run a basic search for nearby tweets. The corresponding code is:
```
	params: {
	          geocode: coords.latitude + ',' + coords.longitude + ',' + '5mi',
          rpp: 30
    
```
  - the geocode parameter, which gets tweeter locations within a five mile radius of the application user.
  - the rpp parameter, which specifies the number of tweets (30 in this case) to return per page of data.
The specific parameters used to run a basic search for nearby tweets are:

ui Property. Controls the appearance of the UI.
iconCls Property. Specifies the CSS class for the button.
dock Property. Controls the horizontal (left to right) position of a docked object. In this example, it is set to 'right', which positions the button horizontally on the right side of the tab bar.
stretch Property. Defines whether a docked object maintains a fixed height or whether its height stretches as the tab bar's height changes when it is resized. In this example, the property is set to false, which specifies that the docked button maintains a fixed height regardless of whether the tab bar is resized.
align Property. Controls the vertical (top to bottom) position of a docked object. In this example, the property is set to 'center', which centers the object vertically on the tab bar.

Within the function in the onReady method, you define the rest of the application code, as explained in the following sections. The rest of the application code consists of:

Defining the Timeline Card

The timeline card displays tweets in a list view. It is created as an Ext.Component, which is a generic shell for data and other components or widgets.

The JavaScript for the timeline card Ext.Component is as follows:

    var timeline = new Ext.Component({
        title: 'Timeline',  // Name that appears on this tab
        cls: 'timeline',    // The CSS class. Lets you style elements on the timeline.
        scroll: 'vertical', // Make it vertically scrollable
        tpl: [              // Set up a template to display tweet data
          '<tpl for=".">',
            '<div class="tweet">',
              '<div class="avatar"><img src="{profile_image_url}" /></div>', // Tweeter's picture
              '<div class="tweet-content">',
                '<h2>{from_user}</h2>',       // Tweeter's name
                '<p>{text}</p>',              // Tweeter's message
              '</div>',
            '</div>',
        '</tpl>'
       ]
    });

The timeline card Ext.Component:

This template updates the timeline card component with data from Twitter. The template tags, profile_image_url, from_user, and text are enclosed in curly braces ({}) and match the JSON format in which Twitter data is stored. The Ext.util.JSONP.request method retrieves the data.

In the application CSS file, guide.css, you can set and change the way the classes defined in the template code appear on device screens.

The following figure shows a typical timeline card that the application might display:

Defining the Map Card

The map card displays a map of the nearby tweets.

The JavaScript for the map card, which is an Ext.Map component, is as follows:

    var map = new Ext.Map({
        title: 'Map',        // Name that appears on this tab
        getLocation: true,   // Gets user's current location
        mapOptions: {        // Used in rendering map
          zoom: 12
        }
    });

Ext.Map creates a Google Map component by wrapping a Google Map in an Ext.Component. As with other Ext components, the Ext.Map component defines properties that control the appearance of the card:

Ext.Map also specifies mapOptions which are used in rendering the map. The mapOptions you set as part of an Ext.Map component are passed directly to the Google Map object. For more information on these options and the Google Maps API, see the Google Maps API Documentation.

In this example, the zoom option, which specifies the initial map zoom level, is set to 12.

The following image shows the map card:

Defining the Tab Panel Component

Ext.TabPanel is a container component that holds the objects that the application displays. In this case, the TabPanel component contains the two previously-defined components timeline and map, automatically adds tabs with the specified titles (Timeline and Map) above the cards (components), and provides the logic for switching between the cards.

The Ext.TabPanel application code is as follows:

    var panel = new Ext.TabPanel({
        fullscreen: true,            // The panel will take up the full rather than partial screen
        cardAnimation: 'slide',       // Special effect for switching between cards
        items: [map, timeline]       // Components (cards) that the tabs correspond with
    });

The TabPanel card component defines three properties that control the appearance of the tab panel:

The following image shows the effect of switching between the cards in the application:

There are additional transition effects you can use for changing cards, such as flip, wipe, cube, pop and so forth. For more information, see the API documentation for the Ext.anims class.

Getting Data from Twitter

The refresh function is called when the application starts up and again whenever the refresh button (which you define in a later section) in the application is tapped. The function makes an external request to gather data from Twitter. It also calls an addMarker function that gets the geographic data for adding markers that show tweeter locations on the map.

The corresponding code from the application file is as follows:

    var refresh = function() {                           // Define the refresh function

      var coords = map.geo.coords;                       // Define a coords variable from the maps geolocation
      Ext.util.JSONP.request({                           // Make an external call using JSONP
        url: 'http://search.twitter.com/search.json',    // to this URL
        callbackKey: 'callback',                         // Set the required Twitter callback parameter
        params: {
          geocode: coords.latitude + ',' + coords.longitude + ',' + '5mi', // Get lat, long, and radius
          rpp: 30                                        // Number of tweets per page
        },
      callback: function(data) {                         // Provide structure to hold data from Twitter callback
        data = data.results;                             // Hold Twitter info in variable called data
        timeline.update(data.results);                   // Update the tweets in timeline

        for (var i = 0, ln = data.length; i < ln; i++) { // Loop to add points to the map
          var tweet = data[i];                           // Get data for a single tweet

          if (tweet.geo && tweet.geo.coordinates) {      // If the tweet is geo-tagged, use that to display marker
            var position = new google.maps.LatLng(tweet.geo.coordinates[0], tweet.geo.coordinates[1]);  // Get coords
            addMarker(tweet, position);                  // Call addMarker function with new data
          }
        }
      }
    });
  };

The Ext.util.JSONP.request provides an easy way to make a JSON call to Twitter. To it, you pass:

Note The geocode and rpp parameters are specific to the Twitter Search API.

The callback function receives the data from Twitter and stores it in the data variable. It first updates the timeline card with a list of the tweets. Recall that the template defined in the timeline card component looks for {profile_image_url}, {from_user}, and {text}, all of which are defined in the results.

The application code for the callback function is as follows:

callback: function(data) {
        data = data.results;
        timeline.update(data.results);

The following is an example of the raw data that comes back from Twitter:

{"results":
[{"profile_image_url":""http://a1.twimg.com/profile_images/704555348/boat3_normal.jpg...
"from_user":"jonathanjulian",...
"text":"@agnellvj have a look at the most intense #extjs book to be published do far!",
...

The for loop goes through the Twitter data one tweet at a time and checks for geographic tagging. If a tweet is geo-tagged, then the latitude and longitude coordinates are stored in the position variable and passed to the addMarker function, which adds the tweet to the map.

The corresponding code is as follows:

 for (var i = 0, ln = data.length; i < ln; i++) {
           var tweet = data[i];

           if (tweet.geo && tweet.geo.coordinates) {
             var position = new google.maps.LatLng(tweet.geo.coordinates[0], tweet.geo.coordinates[1]);
            addMarker(tweet, position);

Adding Tweet Markers to the Map

The addMarker function adds tweets to the map based on location. The logic in this function deals almost entirely with the Google Maps API and is not specific to Sencha Touch.

The corresponding code from the application file is as follows:

   var addMarker = function(tweet, position) {        // Define addMarker function
            var marker = new google.maps.Marker({          // Define variable to hold marker data
            map: map.map,
            position: position,
        });
    }

Adding a Refresh Event

The refresh function runs each time the Geolocation utility within the map is updated. Because you set getLocation: true on the Map component, refresh runs immediately after the page has loaded and has retrieved the application user's location.

The corresponding code, which specifies when refresh runs is as follows:

    map.geo.on('update', refresh);

Note: The Twitter API often serves cached data and refreshes periodically, which means that new tweets may not always display each time a user taps the refresh button.

Adding a Custom Refresh Button to the Tab Bar

To add the custom refresh button to the Tab Bar, first retrieve the TabBar portion of the TabPanel with the following code:

    var tabBar = panel.getTabBar();

The following image shows the Tab Bar.

This section describes a technique for creating a custom refresh button as a docked item on the GeoTweets application tab bar.

To add a button to the TabBar, create a component by passing an object directly to the addDocked function. By using an xtype property in this object, you can create the new button on the fly, inline with the code. This functionality is found throughout the library. Any place where you would typically insert a component or widget, you can also use a flat object with the configuration properties and an xtype property. While using this technique is a fast way to generate interfaces, it can also be less maintainable.

    tabBar.addDocked({
        xtype: 'button',          // Specifies an instance of the button class
        ui: 'mask',              // Appearance, for example, "light", "dark", etc.
        iconCls: 'refresh',       // CSS class for the button
        dock: 'right',            // Puts the new button at the right of the tab bar
        stretch: false,           // Prevents the button from stretching to full height of tab bar
        align: 'center',          // Centers the button vertically within the tab bar
        handler: refresh          // Refreshes the current card when users tap
    });

There are several properties that control the layout of docked objects. The GeoTweets application uses the following properties:

Additionally, the handler function is called when an application user taps the button. In this application, we specify that the refresh function is called when the button is tapped.

The following image shows the button you defined:

Testing the Application

Once you have finished writing and have saved the application JavaScript file you are ready to test it. To do so, follow the directions in Test the Application.

Updating the Application for Production

When you are done testing your application, follow the directions in Update the Application for Production to change from the debug to the production version of the Sencha Touch library.

Putting the Application into Production

When you are ready to release your application for general use, follow the directions in Put the Application into Production.

Summary and Further Reading

As you can see, creating JavaScript Web applications with Sencha Touch is quick and simple! The Sencha Touch release package includes many other examples you can browse and learn from.

For further information on the topics covered in this document, see:

This file last updated July 26, 2010.

收录于