I am using Sencha Cmd to compile my ExtJS project.
I wanted to add a third-party package to my project. For Sencha Cmd to build this, one has to add the package in app.json:
"requires": [
"charts",
"font-awesome",
"font-ext",
"bryntum-scheduler",
"bryntum-scheduler-theme-base",
"bryntum-scheduler-theme-triton"
],
This somehow works, but not completely.
Cmd builds a production version correctly, so the compiled version is working.
However, even after multiple runs of sencha app build production, the application's bootstrap.json does not contain the paths of the package content, and the uncompiled version fails to load because of missing dependencies from that package.
Why is that, where does Sencha Cmd take the contents of bootstrap.json file from, and/or how can I see what happens?
you have to run these cammands in your cmd.whenever i change something in bootstrap.json it didnt work at first place.But after running these cammands it works
sencha app watch
sencha app refresh
Related
I think using skip.slice=1 when running
sencha app build
should still generate a .css file on the build/production folder but that is not the case with CMD 6.1.1.76
Am I missing something ?
I want to skip slicing images as I won't be supporting old browsers but obviously I still want to generate the proper css file.
I've tried it on a clean workspace and it generates CSS in a production build. Have you installed the Compass extension for Sencha Cmd? I've had some problems when I left this deselected on installation.
Since compass no longer works with the latest version of Sencha Touch, I looked for a way to compile my sass and I found sencha ant sass does the trick. But I found that executing the command each time I changed my sass was a bit annoying so I found sencha app watch that watches for ANY changes inside the application, whether it is sass or source code, and build the whole thing.
Is there a way to sencha app watch only sass code ?
EDIT:
Using Compass 1.0.1 (Polaris) Sencha Cmd v5.0.3.324 SenchaTouch 2.4.0
I had the same problem. Run your command with:
sencha ant sass -watch
It will monitor the sass files for changes and compile them on the fly just same as compass native command.
So I am trying to set up another ExtJS (4.2.1) dev workstation I've got Ruby 1.9.3, Sencha Cmd 4.0.4.84 installed and latest Java VM too.
The build won't work on this one though, I'm getting:
[INF] executing compass using system installed ruby runtime
Errno::ENOENT on line ["38"] of C: No such file or directory - C:/devtfs/CustomerPortal/CustomerPortal.UI/Content/Customer_Portal_UI/build/temp/production/Customer_Portal_UI/slicer-temp/.sass-cache/82daaa66b7a4761963814fd25131bf0f81370ec9/Customer_Portal_UI-example.scssc
82daaa66b7a4761963814fd25131bf0f81370ec9 folder does exist, but it's empty.
I've tried
sencha ant clean
sencha app refresh
sencha app build --clean
No go. Ever seen this issue ?
Thanks!
EDIT: Hmm, even after this error, the application seems to be running fine on the Sencha web server, but the index.html file is the last thing that's not created in build/production.
We have an app that was not initially created with Sencha Cmd.
While we will eventually restructure the app to adhere to the structure that works best with Sencha Cmd, for now we just need to know the steps to deploy the app to production in our case.
1) For example, I've heard we need to minify the code by building with Sencha Cmd. Can we do that even if our app was not initially created using Sencha Cmd?
2) I've also heard that we can use Sencha Cmd to ensure that the minified file only contains the classes that are actually used by our application (even reducing the number of ExtJS core classes included). Is that true and if so, can we do that even if our app was not initially created using Sencha Cmd?
3) Anything else to deploy our app to production, especially considering our app was not initially created using Sencha Cmd?
Thanks much in advance!
1) We can deploy & compile our application , even if we have not created the project using sencha CMD. We have to follow the standard application structure given in their tutorial/docs
2)Yes by compiling our js files using sencha compiler/sencha cmd minifies our code to a single file say xyz.js file, so in webapps folder only one file is needed not all other js files containing src code also the import statement in some parent jsp files need to be updated accordingly, instead importing "app.js" . By this process the performance is upgraded as only required/used components are complied.
Note : While compiling our src files,If any component say button,grid etc in any file is used without mentioning its xtype in 'requires[]' field in that particular view file then errors are thrown which are very difficult to track, So make sure all requires[] are updated.
I'm currently toying around with Sencha Touch 2.2.1 and am trying to get it to run offline using an HTML5 cache.manifest. Anyone know how to get this to work? I can only find old guides from the last version which no longer seem to work. After some fiddling I have my manifest as follows:
CACHE MANIFEST
index.html
app.js
touch/microloader/development.js
But this seems to throw errors in the development.js script when it attempts to send fetch the app.json file. Are there some Sencha settings I have to adjust for offline mode? Thank you for your help.
After some hunting around it seems this feature is present in Sencha Touch 2.0 but still a bit incomplete. To get it to work, do as follows:
You must have the Sencha command line installed (which you probably
already have since it's required to make a Sencha project in the
first place).
Navigate to your project's parent directory in command line
Use the sencha app build production command to "compile" your project into a single file
Navigate to your production directory in YourApp/build/YourApp/production
Chane the extension of cache.appcache to cache.manifest
Edit the index.html file's html tag so that manifest="cache.manifest"
Ensure your server is configured to serve .manifest files correctly
Now your production code should have a working cache manifest. Note you only need to change the extension so that the app works on iOS, it seems to work in browser (or at least Chrome where I tested this) with the .appcache extension.
Compiling to production appears to be the only way to generate a cache manifest file but you can use this same file in a testing build if you don't want all the code minified for debugging. Of course you'll have to copy your manifest over and ensure it's referenced in your testing build's html tag.
All in all Sencha clearly needs to update their documentation here but I'm glad I found this out. I only tested this with a super basic, static, two page application. Hoping it scales decently.
Instead of changing manually your production package, you should change in app.json lines after 'appCache'. Here is what will be generated by Sencha CMD and will work just fine after running sencha app build production.
You can see a live example here https://github.com/flrent/ConfMate/blob/master/app.json#L79