3. #WIN
-Danny Winokur, Adobe’s vice president and general manager of interactive development
http://bits.blogs.nytimes.com/2011/11/09/adobe-to-kill-mobile-flash-focus-on-html5/
4. What is Sencha Touch
• Thefirst and best mobile-
centric HTML 5 framework
• Providesthe foundation to
develop kick ass cross
platform mobile Web apps
• Built
on the best Web
Standards
• 2.0 is killing it!
5. New to Sencha Touch 2.0
• Improved Class system (from Ext JS 4.0)
• Faster layouts
• Faster startup speed
• Smoother scrolling
• Updated rendering process
6. New to Sencha Touch 2.0
• DataView can render components
• Way better documentation
• High quality examples
• Updated MVC
7. A peek under the hood
• Full Component lifecycle
• Well designed class inheritance model
• Observable event model
• Components and elements
• Elaborate Container model
• Configureable layout managers
8. Robust class system
• Simple class registration
Ext.Base
• Automatic Name Spacing
Mixin Mixin
• Class dependency system
• Dynamic class loading MyClass
22. The SenchaCon app
• Leverages Local Storage
• Uses app cache (offline storage)
• Implements ComponentQuery
• Not a single component with a static id!
24. The SenchaCon app
• Highly
optimized custom
components
• Reusability
kept in mind
throughout code base
• Code developed with
minification in mind
• Minified with Sencha SDK Tools
2.0
25. Breaking the ice
• Develop individual views & models in their own
sandbox
• Views should work independently
• One HTML file per view for testing
• Test fired events via Webkit console
• Allowed for us to divide and conquer
26. Pass #1
• Initial development done in Sencha touch 1.0
• Used MVC
• Router
• History
• Best practices for extending components
• Paved the way for the Sencha Touch 2.0 migration
35. Sencha Touch 2.0 migration
• Change the namespace to match the new MVC pattern
• Views
• Models
• Controllers
• Utilities
36. Quick MVC thoughts
• Controller is at the center
Controller
• Controllersubscribes to events
from the view
• Controller updates the model
View Model
• Model drives the view
37. Quick MVC thoughts
App
Controller
• Application extends Controller!
• Controllers can talk to the
application via events or direct Controller
methods calls
View Model
39. The class architecture
Data
Util
Manager App
Schedule Sessions Session Speakers Speaker
Viewport NavBar
Panel List Detail List Detail
Schedule Sessions Session Speakers Speaker
Viewport NavBar Session Speaker
Panel List Detail List Detail