Quote Originally Posted by mankz View Post
Let's agree to disagree and let's repeat and summarize: this thread is not about how experienced developers should build their apps. It's about

1. Saving time (and frustration) for new users
1.5 Saving time for the Ext support team.
2. Making sure new users stay in the community and don't loose faith and switch to Kendo, AngularJS, jQuery or some other piece of cool tech due to the learning curve being too steep (which it will be if Cmd is a prerequisite).

Well worth a few bytes in my book (we have several such sanity checks in our scheduling components btw).

Code:
if (Ext.versions.extjs.isLessThan(MIN_EXT_VERSION)) {
        alert('The Ext JS version you are using needs to be updated to at least ' + MIN_EXT_VERSION);
    }
 if (!resourceStore) {
            Ext.Error.raise("You must specify a resourceStore config");
        }

        if (!this.eventStore) {
            Ext.Error.raise("You must specify an eventStore config");
        }
This is a popular misconception that you will not have to use a build system when you use another framework, but it doesn't work this way. You will most likely end up using some sort of loader such as RequiresJS that maintains module dependencies and you will most likely use some automation tool such as GruntJS.

Incidentally, I'm not sure why Sencha Cmd uses Java as opposed node.js (as in RequireJS). Also, they use the bootstrap.js file. This appears as if Ext JS has some sort of dependency on the popular Twitter Bootstrap library