...
Sencha SDK Tools can be downloaded from here: http://www.sencha.com/products/sdk-tools/download/
Manual process still required for rel-1-2-patches and rel-1-1-patches branchesThese steps are pertinent for both the automated process as well as the manual process:
2) Add the installation directory to your PATH. Will look something like:
...
You
...
can validate your Sencha installation by typing the following command (should get usage information back
...
):
%> sencha --help
...
Developers should note that when adding new Ext classes, it is important to edit the ssp.jsb3 file so that the new classes will be included in the minification process.
AUTOMATED PROCESS (SSP 2.0)
Automated process for SSP 2.0:
MANUAL PROCESS (SSP 1.1.x and SSP 1.2.x)
Eventually, the same automated configuration will be added to the 1.2.x and 1.1.x. Until then, the manual process for these versions is:
%> cd {src_root}/src/main/webapp
4
2) Run the sencha tool (note the dot at the end):
%> sencha build -p ssp.jsb3 -d .
6
3) Add the resulting files to git:
%> git add app-all.js all-classes.js
** I never was able to successfully generate a jsb3 file automatically ('sencha create …' would either error out or hang) so I *think* you might need to edit that file by hand whenever adding new Ext classes. If you know of a good way to get that to work automatically, I'm all ears.Also, as discussed on IRC, you don't need to do this to see every incremental change you make in a local dev environment. What I usually do is modify ssp-main.jsp to include app.js instead of app-all.js, hack on .js files in my source tree, and cp them into a running Tomcat every time I want to look at the effect of my changes. I don't generate and test the aggregated files until just before I'm ready to commit.