As it seems there is no out-of-the-box way in Sencha ExtJS to provide a configuration based on the build environment (development, testing or production) to your application. Since you need at least different urls for your proxys, it makes sense to have a mechanism in place that would generate the respective configuration for you. This is our solution for the problem.
Cache is a great thing, but sometimes it causes problems. For example deploying the latest web app but users still having cached JS, CSS files and more cached in their browser. This is not a bad thing in a lot of cases, but consider, you did an API change and the cached JS is still accessing the old API.
Google Chrome 43, which was released in mid-May, has introduced several problems for applications using the ExtJS 4.x or the Sencha Touch 2.x frameworks. For example, the 'painted' event is no longer fired, list components cannot be scrolled, submenu items disappear, and the loadmask no longer plays the spinning animation. This is mainly caused by the removal of the formerly deprecated 'overflowchanged' event. As a reaction, Sencha has offered three overrides, which need to be required in app.js. The overrides can be found here.
Since it is not really documented how to build a release .apk package with SenchaCmd and Cordova I`d like to share the current workflow I use. First of all we build the native package via SenchaCmd. This results in a production build of the Sencha Touch application wrapped in a debug build of Cordova:
Long ago I started to globally .gitignore all the things. Recently I ran into a few issues with setting up Sencha projects via SenchaCmd. In my global .gitignore file I have a setting to ignore the vendor folder which perfectly makes sense in a Composer setup. As a side-effect this means that in a Sencha project the folder resources/themes/vendor/ will not be added to the repo. The work-a-round to avoid this is easy and simple. Add the following line to your global .gitignore file:
Am Donnerstag den 19.02.2015 trifft sich zum ersten Mal die HeidelbergJS Usergroup ab 19 Uhr im Technologiepark Heidelberg. Ich bin als Sprecher dabei und werde in meinem Vortrag "ExtJS 5 MVVM - WTF? FTW!" auf das neue Programmiermodell von ExtJS mit MVVM und Two-Way-Databinding eingehen und demonstrieren wie einfach damit zu arbeiten ist.