Developing Mobile Applications with Force.com and Sencha Touch - Part 2 http://www.sencha.com/blog/developing-mobile-applications-with-forcecom-and-sencha-touch-part-2 In the first part of our series introducing you to the Sencha Touch mobile framework, we built the foundation for a simple mobile application hosted in a Visualforce page that displays lead data served from an Apex controller. We reviewed the basics of the Sencha class system and MVC data package by constructing model, view, controller and store components in Javascript. en-us don@forcementor.com Copyright 2012 2012-09-17T18:00:06+00:00 Comment by Don Robins There is an error in the article above - I did not clearly indicate that in the Store you MUST comment out or remove the line that sets the ‘data’ configuration to the Apex controller data binding: \\data: {!Leads}, This binding, which previously received the JSON from the Apex controller getter mtehod getLeads(), is replaced by an autoload process provided by the new proxy added to the model. There is an error in the article above - I did not clearly indicate that in the Store you MUST comment out or remove the line that sets the ‘data’ configuration to the Apex controller data binding:

\\data: {!Leads},

This binding, which previously received the JSON from the Apex controller getter mtehod getLeads(), is replaced by an autoload process provided by the new proxy added to the model.

]]> Mon, 15 Oct 2012 21:26 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32411#date:21:26 Comment by Don Robins Ken - if you were not using Safari as a browser, (perhaps you’re using Chrome or Mozilla,) the links to the Sencha libraries won’t work as they are not on a secure server. That would explain needing to put them in static resources. You should be able to paste the Apex final controller code, but will have to completely remove the data binding expression to “{!leads}” in the store.  Commenting it out won’t work. Once you replace the store with the new proxy and connect the new Apex controller, full CRUD should work; I’ve built from pasting the code which is why I’m confident.  However, the code was to be posted in a zipfile (rather than on Git) after Dreamforce, and I’ll find out where it is available.  Glad you find it of interest! What you may find is that once you get used to the patterns, you can build mobile apps incredibly fast against your Force.com org.  Please let us know if you build out projects, and how they work out.  Thanks! Ken - if you were not using Safari as a browser, (perhaps you’re using Chrome or Mozilla,) the links to the Sencha libraries won’t work as they are not on a secure server. That would explain needing to put them in static resources. You should be able to paste the Apex final controller code, but will have to completely remove the data binding expression to “{!leads}” in the store.  Commenting it out won’t work. Once you replace the store with the new proxy and connect the new Apex controller, full CRUD should work; I’ve built from pasting the code which is why I’m confident.  However, the code was to be posted in a zipfile (rather than on Git) after Dreamforce, and I’ll find out where it is available.  Glad you find it of interest! What you may find is that once you get used to the patterns, you can build mobile apps incredibly fast against your Force.com org.  Please let us know if you build out projects, and how they work out.  Thanks!

]]> Sat, 29 Sep 2012 00:53 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32343#date:00:53 Comment by Ken Brewer Very performant, and I like the way it integrates with Apex - although I ran into several issues getting the code from Part 1 and 2 to work.  I got a Salesforce error on the external references and had do download and add as resources - other problem the control code would not compile in part 2 because of a reference to getLeads - I added the function to the example to get it to run again, but gave up getting full CRUD.  If you could add a link to a working source in GIT or somewhere it would be greatly appreciated . Very performant, and I like the way it integrates with Apex - although I ran into several issues getting the code from Part 1 and 2 to work.  I got a Salesforce error on the external references and had do download and add as resources - other problem the control code would not compile in part 2 because of a reference to getLeads - I added the function to the example to get it to run again, but gave up getting full CRUD.  If you could add a link to a working source in GIT or somewhere it would be greatly appreciated .

]]> Sat, 29 Sep 2012 00:29 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32342#date:00:29 Comment by Don Robns Richard…The Sencha folk will likely advise to follow practices as per architect’s code generation. I have not looked closely at what you describe (yet), but the key is keeping your view and controller as decoupled as possible. Whatever works best to promote the practice of _not_ being too dependent upon anything from the view itself other than the action being fired. We want the controller to be responding to the action regardless of the view that emits it as there may be many. I followed this pattern also to be able to test that the buttons work without the controller even built yet which would be harder without the listeners. Perhaps someone else will chime in here and pick up the thread, you can also post the general question on the Sencha forums. So glad you found it all useful. Richard…The Sencha folk will likely advise to follow practices as per architect’s code generation. I have not looked closely at what you describe (yet), but the key is keeping your view and controller as decoupled as possible. Whatever works best to promote the practice of _not_ being too dependent upon anything from the view itself other than the action being fired. We want the controller to be responding to the action regardless of the view that emits it as there may be many. I followed this pattern also to be able to test that the buttons work without the controller even built yet which would be harder without the listeners. Perhaps someone else will chime in here and pick up the thread, you can also post the general question on the Sencha forums. So glad you found it all useful.

]]> Thu, 20 Sep 2012 13:54 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32254#date:13:54 Comment by Richard Shergold Don, thanks for this, this is really useful.  I have a question regarding listeners, controllers and events.  I like the way that you have (for example) a listener function in a view which uses fireEvent to fire an event in the Controller.  This make sense to me and I think makes the application easy to understand.  However, using Architect, its possible to use the ConvertToAction option which REMOVES the listener code from view completely and moves it up into the controller.  What is considered best practice - to have listeners down at the component level calling events in the Controller like you have done in the article or to do what “Convert To Action” does and remove the listener code?  Sorry if I haven’t worded this particularly well but I am very new to Sencha Touch.  Thanks again for the article. Don, thanks for this, this is really useful.  I have a question regarding listeners, controllers and events.  I like the way that you have (for example) a listener function in a view which uses fireEvent to fire an event in the Controller.  This make sense to me and I think makes the application easy to understand.  However, using Architect, its possible to use the ConvertToAction option which REMOVES the listener code from view completely and moves it up into the controller.  What is considered best practice - to have listeners down at the component level calling events in the Controller like you have done in the article or to do what “Convert To Action” does and remove the listener code?  Sorry if I haven’t worded this particularly well but I am very new to Sencha Touch.  Thanks again for the article.

]]> Thu, 20 Sep 2012 09:17 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32252#date:09:17 Comment by Jorge Ramon Thank you for the mention, Don. I’m happy that my tutorials helped you. Nice work! Jorge MiamiCoder.com Thank you for the mention, Don. I’m happy that my tutorials helped you. Nice work!

Jorge
MiamiCoder.com

]]> Wed, 19 Sep 2012 01:57 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32235#date:01:57 Comment by Kazuhiro Kotsutsumi I translated it into Japanese. http://www.xenophy.com/javascript/3577 Provision: Japan Sencha User Group http://www.meetup.com/Japan-Sencha-User-Group/about/ I translated it into Japanese.

http://www.xenophy.com/javascript/3577

Provision: Japan Sencha User Group
http://www.meetup.com/Japan-Sencha-User-Group/about/

]]> Wed, 19 Sep 2012 01:35 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32234#date:01:35 Comment by Don Robins Sorry for messy code formatting; the indentation of comments should show lined up with the associated logic. Please take care when you copy the code to properly indent the comments and code blocks together for maximum readability. Sorry for messy code formatting; the indentation of comments should show lined up with the associated logic. Please take care when you copy the code to properly indent the comments and code blocks together for maximum readability.

]]> Tue, 18 Sep 2012 01:42 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32232#date:01:42 Comment by Kazuhiro Kotsutsumi ... which I do my best and translate Extremely long. ... which I do my best and translate
Extremely long.

]]> Mon, 17 Sep 2012 18:34 GMT http://www.sencha.com/blog//developing-mobile-applications-with-force.com-and-sencha-touch-part-2#id:32229#date:18:34