Click to search on your search term.
Subscribe to Fig Leaf Tutorials


Need help with a project? Contact us at sales@figleaf.com.
From code reviews to project "jumpstarts" and full life-cycle development, we've got you covered!
Check out our case studies!
Follow us on Twitter!
Click here to join our Facebook group!

Ready to upgrade your skills? Try these instructor-led classes in Washington, DC:
Ext JS 6 Bootcamp
12/04/2017

Understanding the MVC file structure

Page of 168

MVC File StructureSencha Touch applications follow a unified directory structure that is the same for every app. The code for your application is placed into an 'app' folder, which in turn contains folders for your models, views, controllers and stores as depicted in the illustration.

At the top level there is a single file, index.html, which is the page your application will be hosted from. At the same level there is an 'app' directory, which contains directories for controllers, models, stores and views. The optional profile folder contains a set of classes that defines different types of physical devices. The resources folder is used as a container for CSS, images, and other media assets. Sencha Cmd copies the framework into the touch folder in order for you to isolate any framework changes or patches to your specific app. While you can add additional folders to this structure, it is strongly recommended that you keep this base file layout intact.

 

Page of 168
comments powered by Disqus