Touch Navigation Views
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, inheritance, and read only. 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.
The Navigation View container is one of the most useful and versatile components in Sencha Touch 2. It allows you to easily create an interface where your user steps through a dynamic sequence of cards, while automatically maintaining a title bar and Back button for navigation.
This guide will show you how you can create and manipulate Navigation views within Sencha Architect to build a simple wizard-like interface. Launch a Sencha Touch project in Architect, set the URL Prefix, and save the project before following these instructions.
The completed project file for this tutorial can be found here
The most important thing to understand about Navigation View is that, unlike other card-layout components like Tab Panel, you almost never add multiple child cards into it initially. If you were to do so, the final card would be displayed by default.
Instead, you normally want to define the Navigation view with only one initial child card that displays first. Then, responding to certain user events, your app dynamically creates and pushes new child cards onto the view's navigation stack.
This means that you define each of the possible navigation cards as top-level components, independent from the Navigation view itself. Since they are created at the top level, they are defined as classes that can be instantiated individually.
It also means that you will need to use event handlers, write a small amount of JavaScript code to instantiate the cards, and push the cards onto the navigation stack. We will instantiate cards using their Xtype (also called userAlias in Architect), and will use the Navigation view Push method to add them to the navigation stack at the right time.
We'll start by defining each of the components
that will become cards in the navigation.
The first card will be called Step 1 and ask the user for a number.
The second card will be called Step 2 and ask for a second number.
The third card will be called Step 3
and let the user select a mathematical operator to perform a calculation.
To create the first card:
Step1Panel.step1 --
we will use this value later on when referring to the Step1 Panel component by its xtype.number1 and clear its label config.Next.forward to give it a forward-pointing look.The second card will be very similar to the first card; rather than repeating everything from scratch we can simply right-click the Step1Panel and select Duplicate to save some time. Select the resulting duplicated component, and:
Step2Panel.step2.Enter another number.number2.The third card is also similar to the previous two, so create a duplicate of Step2Panel, then:
Step3Panel.step3.Choose an operation.Calculate!confirm.operation so they will function as a single radio group.Add, and a value of add.Subtract and a value of subtract.Multiply and a value of multiply.Divide and a value of divide.true so it will be selected by default.Now that we've defined the cards, let's create the Navigation view that will display them.
MainNav.Step 1,
which will be displayed in the navigation view's title bar.Now that the application's view is created, let's add some behavior to it.
Implement the behavior of the app by creating a controller.
To add a controller to the project,
click the add button ("+") at the top-right of the project Inspector
and select Controller. Select the controller in the Inspector
and set its userClassName to MainNavController.
Next create a controller action to handle the Next button in the Step 1 card:
tap as the event name.onStep1SubmitTap.step1 button.
(This controlQuery is a
Component Query Selector,
which says to handle tap events for any button within the container with an xtype of step1.)Double-click the controller action in the Inspector and enter the following JavaScript code into the code editor:
button.up('navigationview').push({
xtype: 'step2',
title: 'Step 2'
});
This code says to find the navigationview ancestor of the button,
and to Push
a new Step2Panel card instance onto the end of the navigation stack,
automatically animating it into view.
We refer to the Step2Panel component class by its xtype
which we assigned earlier by setting the Step2Panel's userAlias.
We also give the new step2 instance a title of "Step 2"
which will be displayed in the titlebar when this card is visible.
The controller action for the Step 2 button should be nearly identical. Follow the same steps as for the Step 1 button action, but:
onStep2ButtonTap.step2 button.Change its handler code so it refers to Step 3 instead:
button.up('navigationview').push({
xtype: 'step3',
title: 'Step 3'
});
Follow the same steps to create a controller action for the Step 3 button, but:
onStep3ButtonTap.step3 button.For the handler code, double click the controller action in the Inspector and insert the following using the code editor:
var mainNav = button.up('navigationview'),
num1 = mainNav.child('step1').getValues().number1,
num2 = mainNav.child('step2').getValues().number2,
operation = mainNav.child('step3').getValues().operation,
result;
switch (operation) {
case 'add':
result = num1 + num2;
break;
case 'subtract':
result = num1 - num2;
break;
case 'multiply':
result = num1 * num2;
break;
case 'divide':
result = num1 / num2;
break;
}
Ext.Msg.alert('Your result is: ' + result);
In a nutshell, this code finds the forms for each step and asks for the values of their fields by name. It then performs the mathematical calculation by applying the chosen operator to the two entered numbers and displays the result in an alert popup.
The application is completely functional. Save and Preview the project to see it in action in your WebKit-based desktop browser or on your mobile device. Notice that as you progress through the steps, the Navigation View's title bar is automatically updated to display the title of the current card, and the Back button is automatically updated to allow you to go back to the previous step.
The Navigation view also supports some other useful options.
For example, go to Architect and select the Navigation view
and set its useTitleForBackButtonText config to true.
Save and preview again and notice
that the Back button now displays the title of the previous card
rather than the static Back label.
You can also control the title bar at the top of the Navigation view by selecting it in the Inspector, finding its Navigation Bar item in Config, and click the add button. You can then select and configure the Navigation bar child, add additional items into it, and so on.
Now you have an understanding of how to create and manipulate Sencha Touch 2 Navigation View containers using Sencha Architect. You will find this very useful when creating common sequential UI navigation structures in your Touch apps.
Architect | Terms of Use