{"id":488,"date":"2011-06-20T10:36:50","date_gmt":"2011-06-20T10:36:50","guid":{"rendered":"http:\/\/www.osd.net\/blog\/?p=488"},"modified":"2011-06-20T10:36:50","modified_gmt":"2011-06-20T10:36:50","slug":"creating-a-sencha-touch-mvc-application-from-scratch-part-2","status":"publish","type":"post","link":"https:\/\/www.osd.net\/blog\/mobile-development\/creating-a-sencha-touch-mvc-application-from-scratch-part-2\/","title":{"rendered":"Creating a Sencha Touch MVC application from scratch, part 2"},"content":{"rendered":"

As the title says we will continue to build our Sencha Touch MVC app<\/strong> we’ve started in part 1<\/a>. In this part we will create a controller<\/strong> and two views<\/strong> and learn how to use them.<\/p>\n

Let’s modify our current project structure by adding some folders:<\/p>\n

\"MvcTouch<\/a><\/p>\n

Creating a controller.<\/h2>\n

In app\/controllers<\/strong> create a file named HomeController.js<\/strong> and add the following content to it:<\/p>\n

\r\nExt.regController('Home', {\r\n\r\n\t\/\/ index action\r\n\tindex: function()\r\n\t{\r\n\t\tExt.Msg.alert('Test', "Home's index action was called!");\r\n\t},\r\n});\r\n<\/pre>\n
We create a controller<\/a> by registering within our application with the function Ext.regController <\/strong>with two parameters: the name <\/strong>of the controller and a configuration object. In the configuration object we will add our custom properties and functions\/actions<\/strong>.<\/p>\n
A controller action is a function that is called automatically based on a route<\/strong>. A route is an identifier for a controller\/action<\/strong> pair and looks like an url: home\/index<\/strong>, home\/contact<\/strong> etc.<\/p>\n
Note: <\/strong>when you add a custom property or a function to the controller you should always add a comma at the end of it to avoid any errors when you later add other properties or functions.<\/p>\n
Another note: <\/strong>you should always have the console of the browser opened to watch for errors.<\/p>\n
The default route (controller\/action pair)<\/h2>\n
Every Sencha Touch MVC application will have a default route loaded on startup. Before we start using routes in our application we need to define their structure.<\/p>\n
In app<\/strong> folder create a file named routes.js<\/strong> and add the following content:<\/p>\n
\r\nExt.Router.draw(function(map) {\r\n\tmap.connect(':controller\/:action');\r\n});\r\n<\/pre>\n
With the code above a route will be constructed by two parts: the controller and the action, separated by a forward slash. For more info about a route you could check the documentation<\/a>.<\/p>\n
Let’s set our default route in our application<\/strong>.<\/p>\n
Open app.js<\/strong> and set the defaultUrl<\/strong> property to point to Home\/index<\/strong> route like this:<\/p>\n
\r\nExt.regApplication({\r\n\tname: 'App',\r\n\tdefaultUrl: 'Home\/index',\r\n\tlaunch: function()\r\n\t{\r\n\t},\r\n});\r\n<\/pre>\n
Before testing our application we need to include the created files in the index.html<\/strong> file:<\/p>\n
\r\n\r\n<!-- Sencha Touch framework -->\r\n<link rel="stylesheet" type="text\/css" href="lib\/sencha-touch-1.1.0\/sencha-touch.css" \/>\r\n<script type="text\/javascript" src="lib\/sencha-touch-1.1.0\/sencha-touch.js"><\/script>\r\n\r\n<script type="text\/javascript" src="app\/app.js"><\/script>\r\n<script type="text\/javascript" src="app\/routes.js"><\/script>\r\n\r\n<!-- CONTROLLERS -->\r\n<script src="app\/controllers\/HomeController.js" type="text\/javascript"><\/script>\r\n\r\n<!-- VIEWS -->\r\n\r\n<\/pre>\n
Note: <\/strong>When you’ll start creating more controllers, views etc. there is a possibility that you’ll forget this step and wonder why things are not working as expected. So, don’t forget to include your files in index.html<\/strong>.<\/p>\n
Ready for testing! <\/strong><\/p>\n
Open index.html in a webkit based browser and you should see a message box.<\/a><\/p>\n
Creating views<\/h2>\n
Our views will be created by extending the Sencha Touch components and they will be responsible with the rendering of our data. With them we make our app look cool.<\/p>\n
Creating the main view: the Viewport<\/strong><\/p>\n
The first view we need to create when we start a new app will be the viewport<\/strong>. This is our main view in which we’ll render the other ones. You can think of it like a canvas. <\/strong><\/p>\n
in our app\/views<\/strong> folder create a file named Viewport.js <\/strong>and add the following content in it:<\/p>\n
\r\nApp.views.Viewport = Ext.extend(Ext.Panel, {\r\n\tfullscreen: true,\r\n\tlayout: 'card',\r\n\tcardSwitchAnimation: 'slide',\r\n\tdockedItems: [\r\n\t\t{\r\n\t\t\txtype: 'toolbar',\r\n\t\t\ttitle: 'MvcTouch',\r\n\t\t},\r\n\t],\r\n});\r\n<\/pre>\n
What’s in a view?<\/strong><\/p>\n
We create our view in App.views<\/strong> namespace created for us automatically by the application registration.<\/p>\n
Our views will be subclasses of an existing component\/class. We create them using the function Ext.extend<\/strong> by passing two parameters to it: the superclass (the component we want to extend) and an object in which we’ll add properties and functions.<\/p>\n
For our viewport we’ve choosed\u00a0 to extend the Panel<\/a> class and setting some properties: the fullscreen<\/strong> property\u00a0to true<\/strong> in order to take all the available space;\u00a0the layout<\/strong>  <\/strong>property to ‘card’<\/strong> so that only one child component will be visible at a time; <\/strong>the cardSwitchAnimation<\/strong> to ‘slide’<\/strong> will handle how the child components will be showed on screen.<\/p>\n
About the final property, dockedItems<\/strong>, Sencha Touch says: “A component or series of components to be added as docked items to this panel. The docked items can be docked to either the top, right, left or bottom of a panel. This is typically used for things like toolbars or tab bars<\/em>“.<\/p>\n
If you don’t know what is an\u00a0xtype<\/strong> you should read this<\/a>.<\/p>\n
Now we need to instantiate the viewport in our launch function of our app:<\/p>\n
\r\nlaunch: function()\r\n{\r\n\tthis.viewport = new App.views.Viewport();\r\n},\r\n<\/pre>\n
We assign our viewport instance to a property in our app so that we can access it later in our controller this way: this.application.viewport<\/strong>.<\/p>\n
Before testing what we have so far, we need to include the viewport file in our index.html, under the views comment:<\/p>\n
\r\n<!-- VIEWS -->\r\n<script type="text\/javascript" src="app\/views\/Viewport.js"><\/script>\r\n<\/pre>\n
Now you can test!<\/strong> You should have something that looks like this:<\/p>\n
\"MvcTouch<\/a><\/p>\n
Creating a controller specific view.
\n<\/strong><\/p>\n
For the views used by a specific controller we will create a new folder, named as the controller (lowercase), in app\/views<\/strong> to add them. So, create a folder named home <\/strong>in app\/views and in that create a file named HomeIndexView.js<\/strong>. Include this file in index.html<\/p>\n
\r\n<!-- VIEWS -->\r\n<script type="text\/javascript" src="app\/views\/Viewport.js"><\/script>\r\n<script type="text\/javascript" src="app\/views\/home\/HomeIndexView.js"><\/script>\r\n<\/pre>\n
and add the following content in it:<\/p>\n
\r\nApp.views.HomeIndex = Ext.extend(Ext.Panel, {\r\n\thtml: "<h3>A Lover's Complaint<\/h3>" +\r\n\t\t"<h4>a poem by<\/h4>" +\r\n\t\t"<h3>William Shakespeare<\/h3>" +\r\n\t\t"<p>From off a hill whose concave womb reworded<\/br>" +\r\n\t\t"A plaintful story from a sist'ring vale,<\/br>" +\r\n\t\t"My spirits t'attend this double voice accorded,<\/br>" +\r\n\t\t"And down I laid to list the sad-tuned tale,<\/br>" +\r\n\t\t"Ere long espied a fickle maid full pale,<\/br>" +\r\n\t\t"Tearing of papers, breaking rings atwain,<\/br>" +\r\n\t\t"Storming her world with sorrow's wind and rain.<\/br>" +\r\n\t\t"Upon her head a platted hive of straw,<\/br>" +\r\n\t\t"Which fortified her visage from the sun,<\/br>" +\r\n\t\t"Whereon the thought might think sometime it saw<\/br>" +\r\n\t\t"The carcase of a beauty spent and done.<\/br>" +\r\n\t\t"Time had not scythed all that youth begun,<\/br>" +\r\n\t\t"Nor youth all quit, but spite of heaven's fell rage<\/br>" +\r\n\t\t"Some beauty peeped through lattice of seared age.<\/p>" +\r\n\r\n\t\t"<p>Oft did she heave her napkin to her eyne,<\/br>" +\r\n\t\t"Which on it had conceited characters,<\/br>" +\r\n\t\t"Laund'ring the silken figures in the brine<\/br>" +\r\n\t\t"That seasoned woe had pelleted in tears,<\/br>" +\r\n\t\t"And often reading what contents it bears;<\/br>" +\r\n\t\t"As often shrieking undistinguished woe<\/br>" +\r\n\t\t"In clamours of all size, both high and low.<\/p>",\r\n});\r\nExt.reg('HomeIndex', App.views.HomeIndex);\r\n<\/pre>\n
Our HomeIndexView<\/strong> makes use of the html property<\/strong>, where we’ve added some content to our view, and Ext.reg<\/strong> function to register an xtype for our class.<\/p>\n
Rendering a view from a controller<\/h2>\n
Open HomeController.js<\/strong> and alter the index action (function) like this:<\/p>\n
\r\n\/\/ index action\r\nindex: function()\r\n{\r\n\tif ( ! this.indexView)\r\n\t{\r\n\t\tthis.indexView = this.render({\r\n\t\t\txtype: 'HomeIndex',\r\n\t\t});\r\n\t}\r\n\r\n\tthis.application.viewport.setActiveItem(this.indexView);\r\n},\r\n<\/pre>\n
First we test if the view class wasn’t already created. If it wasn’t created we create an instance of it with the controller’s render <\/strong>function and assign it to a variable. We pass to the render function an object with our registered xtype as a property.<\/p>\n
After we have a view instance, we pass it as a parameter to the setActiveItem<\/strong> function of our viewport. This function will add the view into the viewport as a child.<\/p>\n
Refresh your browser and you’ll see how the index view shows up on the screen with a nice slide animation from the right to the left (remember the cardSwitchAnimation<\/strong> property we’ve set in our viewport).<\/p>\n
\"MvcTouch<\/a><\/p>\n
Your app should look like the image above. We’ve added some html tags to our content but it’s still looking like plain text. To fix this we need to set the styleHtmlContent<\/strong> property of the view to true. Also, as you can see, our content is cut off and we have no option to scroll down. In order to enable scrolling we need to set the scroll <\/strong>property to vertical <\/strong>for that. Let’s do that.<\/p>\n
\r\nscroll: 'vertical',\r\nstyleHtmlContent: true,\r\nstyle: 'background: #d8e2ef',\r\n<\/pre>\n
\"MvcTouch<\/a><\/p>\n
We also add a style property to add some CSS rules to our view to observe the slide animation better. Now the text should look nicer on a blue background and when you will press and hold the mouse in the view and move up and down you’ll be able to scroll.<\/p>\n
That’s it for part 2!<\/strong><\/p>\n
In part 3 we will see how to add more views and how to navigate through them. We’ll also add some buttons to our toolbar.<\/p>\n
You can download the current phase of the project from here<\/a>.<\/p>\n
If you have questions, suggestions or improvements don\u2019t hesitate to use the form below.<\/p>\n
\t
\n\t \t\n\t\t
\n\t\t\t
\n\t\t\t\t\n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t<\/form>\n\t\t\t
If you liked this post 
 you can buy me a beer<\/strong><\/p>\n\t\t<\/div>\n\t<\/div><\/div>","protected":false},"excerpt":{"rendered":"
As the title says we will continue to build our Sencha Touch MVC app we’ve started in part 1. In this part we will create a controller and two views and learn how to use them. Let’s modify our current project structure by adding some folders: Creating a controller. In app\/controllers create a file named …<\/p>\n
Read more<\/a><\/div>\n
\n        <\/div><\/div>","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[88],"tags":[92,93,90,89,94],"_links":{"self":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts\/488"}],"collection":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/comments?post=488"}],"version-history":[{"count":55,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts\/488\/revisions"}],"predecessor-version":[{"id":559,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts\/488\/revisions\/559"}],"wp:attachment":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/media?parent=488"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/categories?post=488"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/tags?post=488"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}