Our company has a working Ext JS 3.x application that we would eventually like to move to Ext JS 4.x. I've already done work to rewrite parts to work with 4.1, and now I'm looking at what it would take to move to 4.2. The biggest change for us is the use of Sencha Cmd as well as the way themes are now constructed. My initial concern is just getting something working in 4.2 with Sencha Cmd and I've run into something of a roadblock (possibly just mental).

Our application is currently launched via a JSP file. The file is structured loosely like this:

Code:
set up some JSP variables
get user session information
if session is valid

   emit HTML to load required Javscript/CSS files to run application

else

  emit HTML to load a Login 'app'
For login, we make use of a simple Ext JS Window and card view to deal with collecting login information and for displaying status. Once the session is valid, we reload our index.jsp and this time, since the session is valid, we would load the application code, not our login code.

Looking at the way apps are organized and build with Sencha Cmd, I'm not sure how to accomplish the same thing. The goal would be to be able to run a sencha app build and get the proper collection of all-classes.js which would be needed for either the login portion of the app or the main application. The idea being that I don't want to load the entire application just to support the login operation. I've got some ideas that I'm going to play around with, but I wonder if others are trying to do something similar and if so, how you have your code organized.

Thanks